Your Rooms Rank. Your Policies Do Not.

Search your hotel's name and the room pages appear, well-photographed, properly marked up, ranking as they should. Now ask an assistant whether your hotel allows dogs. It does not know, or it guesses, or it names a competitor whose page said so in one sentence.

That is the gap. The rooms are findable. The policies - the things travellers actually ask about - are not.

Why the rooms are fine

The booking engine vendor built them. Every hotel website in the last decade got room pages with photos, prices, availability, and structured data, because the vendor's product depends on them ranking. The property did not have to think about it.

Why the policies are not

Nobody built them. Parking, pets, cancellation, late arrival, breakfast, accessibility, shuttle - at most properties these live in one of four places, each invisible to an assistant:

A PDF. Not extractable as a passage, not marked up, often not crawled at all.

A paragraph on the contact page. Buried, unstructured, usually out of date.

A script-loaded accordion. The crawlers behind ChatGPT, Claude and Perplexity fetch HTML and do not execute JavaScript. An answer that appears on click does not exist to them.

Nowhere. A line saying contact us for details. The most common answer, and the one that guarantees a competitor gets named instead.

What travellers actually ask

Not about the room. The room is chosen from photos. The questions that go to an assistant are the ones that decide whether the stay works:

• Is parking free, and do I need to reserve it
• Are dogs allowed
• Can I check in at 11pm
• Is breakfast included, and what time does it end
• What happens if I cancel two days before
• Is there step-free access
• Is there a shuttle from the airport
• Are children free, and is there a cot

Every one of those is a policy. Every one is answerable in a sentence. And at most hotels, none of them is on a page an assistant can read.

The shape that works

One page, or one clearly separated section per policy. The question as the heading. The answer beneath it in one or two self-contained sentences, specific enough to quote:

Are dogs allowed? Dogs are welcome in ground-floor rooms for 20 per night. Guide dogs stay free in any room.

Plain HTML, not a PDF, not an accordion that loads on click. FAQ schema behind it, so a machine reads the pairs without interpreting prose. A visible date, kept honest.

Then the tedious part: check the same facts on the OTA listing and the map profile and make them match. An assistant cross-references, and a hotel whose sources disagree gets a hedge - check-in times vary - or gets skipped.

The connection to the front desk

The list above is the list of questions the desk answers most. The person who knows the current answers is a supervisor. The page you are building is the knowledge base a messaging assistant needs to answer those questions on WhatsApp.

So this is not a marketing task that operations should be consulted on. It is an operations task with a marketing benefit. The front desk already has the questions; writing the answers down once, in one place, serves the guest who messages, the assistant that answers them, and the assistant that decides whether to recommend the property.

The honest limit

A clear policy page does not make a hotel better than its competitors. It makes a hotel that deserves to be named actually get named, instead of being skipped because a competitor's page was easier to read. Reviews still describe the experience. Policies describe whether the stay is possible, and that is the gate the assistant checks first.

What to do

Find where your parking policy currently lives. If it is a PDF, a paragraph or a line saying to call, that is the first page to build. Then the other eleven. It is a day, and it is the day that closes the gap between ranking and being recommended.