Can an AI agent find a room at your hotel and reach your booking form?
Travellers now ask AI assistants for a hotel with free cancellation, parking or a sea view. Specoria checks whether those agents can read your property, your rooms and your cancellation terms, and sends a real agent through your booking flow up to the guest details form.
What an agent needs from a hotel site
- To reach the site at all: robots.txt and the security layer must let AI agents in.
- To read the property: name, address, stars and amenities in machine-readable form (schema.org Hotel or LodgingBusiness), not only in images or scripts.
- To compare rooms: room types and starting prices it can read without running JavaScript.
- To trust the booking: a cancellation policy it can find and quote.
- To act: a booking link or form it can find in the page itself (a plain link or form with dates), not only a script-driven button.
What the free test measures on a hotel site
The free test recognises a hotel or lodging site from its home page. Checks that only make sense for an online store (cart, guest checkout, product feed and so on) are marked “not applicable” and leave the score; the checks below are measured instead, from your home page.
Hotel checks
| Weight | |
|---|---|
| Hotel structured data (Hotel / LodgingBusiness) | 18 |
| Amenities in structured data | 8 |
| Rooms and prices readable | 15 |
| Cancellation policy discoverable | 12 |
| Booking entry point reachable | 20 |
Checks shared with every site type
| Weight | |
|---|---|
| Search and user agents allowed (robots.txt) | 8 |
| Is bot protection open to agents? | 8 |
| Homepage readable without JavaScript | 5 |
| Sitemap | 2 |
| Can the homepage be indexed? | 2 |
| Currency and language | 2 |
The weights add up to 100, so a hotel’s score sits on the same 0-100 scale as a store’s. None of the hotel checks is a critical blocker, because they are measured from the home page only. A check we couldn’t verify (for example because a page didn’t open) is shown as “couldn’t verify” and leaves the denominator; it never counts as zero.
Run the free test on your hotel site → How the free test works →
What the agent simulator does on a hotel site
- A pre-check recognises the hotel site and adapts the task: the agent chooses dates, the number of guests and a room, the way a guest would.
- It goes as far as the guest details form and reads which details the form asks for.
- It types nothing into the form and never sends it. No booking is made, no card or personal details are entered.
- If your booking opens in an engine on another domain, the agent doesn’t follow it there; the report marks that part as “not measured”.
Send the agents to your booking flow →
What we don’t claim
- We don’t read your channel manager, PMS or OTA listings; we only look at your public website.
- We don’t publish industry averages for hotels: we only show a figure once we have measured enough hotel sites ourselves, with the sample size and date.
- Nobody can guarantee that an AI assistant recommends your hotel; we measure whether it can read and use your site.
With a paid plan
- Monthly deep audit and agent simulation on your booking flow
- Tasks with ready code (for example Hotel and LodgingBusiness JSON-LD) and a “Check” button that re-measures
- AI visibility measurement for questions travellers ask
Questions from hotels
Our booking engine is on another domain. Can you still test it?
The free test and the simulator stay on the domain you enter. If the booking opens on another domain, that step is marked “not measured”; we don’t follow it and we don’t guess its result.
Will the agent make a booking?
No. It stops at the guest details form, types nothing into it and never submits it.
Do you need access to our systems?
No. We only read public pages. You add the fixes yourself, or with your web agency.