Most hotel websites contain at least one pair of pages that disagree with each other about something a guest needs to know. Not a tone mismatch or an outdated photograph, but a flat contradiction: the FAQ says one thing, the policy page says another, and both are live.
This isn’t a sign of a badly run hotel. It’s what happens to any website that has existed for more than about three years and has had more than one person writing for it.
How it happens
Nobody sits down and writes two conflicting answers on purpose. Contradictions accumulate.
A policy changes. Somebody updates the page where the policy obviously lives, and possibly the FAQ, and misses the two blog posts from 2021, the meta description, and the sentence in the footer of the rooms page. A facility closes and the booking pages are updated the same week, while the local area guide that mentions it in passing survives for another four years. A restaurant is renamed and the new name goes on the restaurant page, while every other page on the site, plus every listing on the internet, carries on using the old one.
Each of those individual omissions is entirely reasonable. The person making the change fixed the page they were asked to fix. The problem is that nobody’s job is the whole site, so nobody is looking at page 3 and page 41 at the same time.
Where they hide
The contradictions are rarely on the pages that get attention. They cluster in predictable places:
- FAQ pages, which are typically written once at launch and then left, while the rest of the site moves on around them
- Access statements and policy documents, often maintained separately by someone who isn’t in the marketing conversation
- Older blog posts, which nobody counts as part of the website but which search engines and AI systems certainly do
- Meta titles and descriptions, which are edited in a different system from the page they describe
- Navigation labels pointing at pages whose content has since changed underneath them
- Third-party listings, which sit outside your site entirely and disagree with all of the above
The FAQ page deserves particular attention, because it combines the two worst properties. It’s the page most likely to be out of date, and it’s the page most likely to be quoted verbatim by a search summary, because it’s written in exactly the question-and-answer form that gets extracted.
Why nobody notices
Three reasons, and they compound.
First, nobody reads their own website. Staff navigate to the page they need and leave. The last person to read the site end to end was probably the developer who built it.
Second, the people who could spot the error read straight past it. If you know the spa closes at eight, your eye slides over a sentence saying it closes at nine, because you’re reading for meaning rather than for accuracy. Knowing the correct answer makes you worse at catching the incorrect one, not better.
Third, guests do notice and mostly don’t tell you. Someone who finds two different answers about whether you accept dogs doesn’t email to point it out. They book somewhere that gives them one clear answer. The cost is real and completely invisible, because the enquiry you never received doesn’t appear in any report.
Why it costs more now than it used to
A guest reading your site follows one path through it. They see the parking answer once, on whichever page they happened to land on, and if it’s the wrong one they simply don’t know there was another.
A system generating an answer about your hotel doesn’t work that way. It sees the parking claim in all seven places it appears, finds them inconsistent, and has to resolve the conflict without being able to ring reception and ask.
It resolves it by weight of signal, and weight of signal favours whichever version has been around longest and repeated most. That is very often the outdated one, because the old fact has had years to propagate across directories, listings and other people’s blog posts, while the correct new fact exists in one place and was published last month. The internet is a lagging indicator of your hotel’s current state, and your own inconsistency is what lets the lag win.
So the practical effect is that a contradiction on your site doesn’t produce a random answer. It tends to produce the wrong one. It’s the same mechanism that makes entity consistency across your pages and listings matter so much, applied to facts rather than to names and addresses.
Audit by claim, not by page
Here’s the part that changes the outcome, and it’s a small shift with large consequences.
The instinct is to work through the site page by page, reading each one and checking it looks right. That process will never find a contradiction, because each page is internally consistent. The error only exists in the relationship between two pages you’re reading a fortnight apart.
Audit claims instead. Pick a claim, then find every place on the site it appears, and read those places together.
Start with the claims where being wrong costs a guest something real. Accessibility and step-free access. Pets. Parking. Lifts. Check-in and check-out times. Whether food is served, and when. Room occupancy limits. Anything involving a deposit or a cancellation.
For each one, search your own domain for every page mentioning it, including old blog posts and the FAQ, and line the answers up next to each other. Most audits of this kind turn up their first contradiction inside twenty minutes, which is usually the moment the exercise justifies itself.
Then fix at source. Decide which page is the canonical home for that claim, correct it there, and remove or update the claim everywhere else rather than duplicating the correct version into six more places. Duplicated facts are just future contradictions with a delay on them. Consistency is a large part of what makes content trustworthy enough to be cited in the first place.
The awkward part
Running this audit means finding out that your website has been telling guests something untrue, possibly for years. That’s uncomfortable, and it’s the reason these audits get postponed.
It’s worth doing anyway, because the contradiction is already there and already costing you. The only question is whether you find it or a guest does. Get in touch if you’d like us to run one properly.
