# What Travel Agent Readiness asks of a hotel's website

Published by AuraScope on 5 November 2026. Last updated 5 November 2026.

Canonical page: https://research.aurascope.co/research/what-travel-agent-readiness-asks

Travel Agent Readiness is a lodging profile of the AgentReady standard. It says what a hotel website needs so that an AI agent can find it, read it and book through it, and why each requirement is there.

## Overview

AI agents visit hotel websites on a traveller's behalf to answer questions about a stay, compare properties and, increasingly, book. Travel Agent Readiness is a lodging profile of the AgentReady standard. It says what a hotel website needs so that an agent can find it, read it and book through it.

The requirements follow the order in which an agent meets a property. Each has a stable identifier, a level, and a category that says who fixes it.

| Stage | Question it answers |
| --- | --- |
| Find | Can an agent reach and discover the property's pages? |
| Read | Can it extract the stay facts from what came back? |
| Book | Can it turn an answer into a reservation? |

Table 1. The three stages, in the order an agent meets a property.

Each stage depends on the one before it. An agent cannot read a page it cannot reach, and will not book a stay it cannot read about.

1 · How to read a requirement

## Levels, categories and conformance

### Levels

| Level | What it means |
| --- | --- |
| MUST | Reserved for the few conditions whose absence stops an agent outright, or whose failure looks like success. |
| SHOULD | A practice that shapes where an agent goes and what it builds its answer from. |
| MAY | A reasoned practice or an emerging convention a property can adopt early. |
| Deferred | Kept under its identifier but not assessed, until the step it concerns can be observed. |

Table 2. The four levels a requirement can carry.

### Categories

| Category | What satisfying it changes |
| --- | --- |
| Technical | How the site is served, addressed or described to machines. |
| Content | What the property says and where it says it, as a human reads it. |

Table 3. The two categories, which say who fixes a requirement.

### Conformance

A property conforms as **Visible** when it satisfies every applicable MUST in Find and Read. Every MUST is technical, so a well-built site may already be Visible. The content requirements are what make a Visible site useful to an agent, and the property can close those gaps itself. **Bookable** waits until a Book requirement is in force at MUST.

The agent-readiness score counts every requirement in force except the four on agent interfaces, `FIND-08`, `READ-11`, `BOOK-03` and `BOOK-04`, which do not yet earn points. Deferred requirements are not assessed.

2 · Terms

## The words the requirements use

| Term | Meaning |
| --- | --- |
| Stay fact | What a traveller needs to choose, verify or arrive for a stay: check-in and check-out, cancellation and deposit, occupancy and children, pets, parking, accessibility, inclusions, address, arrival and contact. A facts page is a first-party page that states them. |
| Booking entry | The URL at which a booking begins and which accepts the traveller's dates and guests. |
| Booking surface | Every page and endpoint from the booking entry to payment, wherever it is hosted. |
| Fetch-only agent | An agent that retrieves HTML without running JavaScript. Most agent fetch tools behave this way. |
| Visible text | The text of a page after its script, style, noscript and template elements are removed. A fact that lives only in a script payload is not visible text. |
| Agent interface | A machine-readable way for an agent to read or act without using the web pages, such as MCP tools, an OpenAPI description or agent skills. An operation is read-only when it declares that it changes nothing. |

3 · Find

## Be reachable and citable

An agent can cite only pages it can discover and fetch. A property that cannot be reached is described by someone else's copy, because an agent usually also holds a third party's description of it.

| ID | Level | Category | What it asks | Why it is there |
| --- | --- | --- | --- | --- |
| FIND-01 | MUST | Technical | Keep public content open to agents and crawlers, in `robots.txt` and at the network layer, on the site and its booking surface. | A blocked page is absent from the indexes agents query, and a datacentre challenge stops the agent's own fetcher. |
| FIND-02 | SHOULD | Content | Publish stay facts on canonical first-party pages, not only inside the booking engine, a PDF or an image. | Agents cite pages. A fact that lives only in an engine or an image cannot be cited. |
| FIND-03 | SHOULD | Technical | List room and policy pages in a sitemap referenced from `robots.txt`. | A crawler finds every page that matters without guessing. |
| FIND-04 | SHOULD | Content | State each stay fact and identity detail the same way across pages, structured data and the booking surface, from one canonical origin. | An agent that reads two check-in times has to pick one, and it may pick wrong. |
| FIND-05 | SHOULD | Technical | Serve a plain-text `robots.txt` that states a policy for AI crawlers, in a group that names them or a wildcard group that applies to them. | A missing or malformed file leaves a crawler guessing what the property intends. |
| FIND-06 | SHOULD | Technical | Leave search and AI answers open in any Content-Signal line in `robots.txt` that covers pages with stay facts. | A closed signal removes the facts from the answers travellers get. |
| FIND-07 | SHOULD | Technical | Keep the homepage and every page with stay facts free of `noindex` and `nosnippet`. | The search engines agents query can then index and quote the page. |
| FIND-08 | MAY | Technical | Advertise an agent interface through a well-known discovery document. | An agent can find the interface without being told about it. |

Table 4. The eight Find requirements.

4 · Read

## Put the stay facts where agents read

After reaching a page, an agent has to extract the answer from what came back. Agents read the same pages human visitors do, so the pages themselves carry the answer.

| ID | Level | Category | What it asks | Why it is there |
| --- | --- | --- | --- | --- |
| READ-01 | MUST | Technical | Put stay facts in the visible text of the initial HTML, server-rendered or prerendered. | A fact injected after load, or present only in a script payload, never reaches a fetch-only agent. |
| READ-02 | MUST | Technical | Return accurate status codes on the site and its booking surface: `404` for a missing path, `429` with `Retry-After` when throttling, not a `200` for a missing page, or a silent challenge page. | A dishonest status makes a failure look like success. |
| READ-03 | SHOULD | Technical | Serve the homepage as raw HTML with real links to rooms, policies, location, contact and the booking entry. | A homepage whose only call to action is a script widget gives an agent nowhere to go. |
| READ-04 | SHOULD | Content | Answer every stay fact on a facts page, on a stable URL and in visible text. | An agent fills a silence from other sources, so "no pets" is worth stating. |
| READ-06 | SHOULD | Technical | Link discovery files and agent interfaces from content agents already visit, such as the footer or an HTTP `Link` header. | A file nobody links to is never found. |
| READ-07 | MAY | Technical | Ship an `llms.txt`: a lean, described index of facts pages, room pages and the booking entry. | Routes an agent to the right page in one fetch. |
| READ-08 | SHOULD | Technical | Carry lodging JSON-LD: a `Hotel` on the property page and a `HotelRoom` with an `Offer` on room pages, with the critical facts also in visible text. | Gives a machine one unambiguous value for a time or a policy. |
| READ-09 | SHOULD | Technical | Offer a markdown representation, by answering `Accept: text/markdown` or advertising a markdown mirror. | Markdown is the page with everything an agent cannot use stripped out. |
| READ-11 | MAY | Technical | Offer read-only agent access to stay facts and to live availability and rates, directly or through the vendor. | A web page cannot answer availability for a given date. |

Table 5. The nine Read requirements.

5 · Book

## Let agents book, not only read

To book, an agent needs either a booking-engine URL that accepts the traveller's intent and keeps it through to payment, or an agent interface whose operations can reserve. The stage applies to properties that sell rooms online. A property with no online booking earns no points in this stage, and those points do not move to Find or Read. No Book requirement is at MUST in this version.

| ID | Level | Category | What it asks | Why it is there |
| --- | --- | --- | --- | --- |
| BOOK-01 | SHOULD | Technical | Expose a booking entry URL that takes dates and guests as query parameters, with the parameter names documented where agents read. | An agent can construct the handoff instead of driving a form. |
| BOOK-02 | SHOULD | Technical | Make the dated booking entry reachable and readable by a fetch-only agent, with room types and a total price, taxes, fees and currency, in visible text. | The entry is where an answer becomes a reservation. An agent that cannot read it stops there. |
| BOOK-03 | MAY | Technical | Offer an agent interface through which an agent can hold, book, modify or cancel a stay, directly or through the vendor. | Lets an agent reserve without driving a browser. |
| BOOK-04 | MAY | Technical | Where an interface needs authentication, make it completable by an agent, for example OAuth 2.0 with discoverable metadata. | A login only a human can complete is an interface an agent cannot use. |
| BOOK-05 | Deferred | Technical | Publish a UCP business profile. | Returns when UCP onboarding for lodging opens. |

Table 6. The five Book requirements. Shaded rows are deferred.
