Booking sites took the search results. The guide stayed worth quoting

Most agencies advise travel brands from the outside. We also run one of the oldest destination references on the web, so the problem the sector page describes is one we live with every week.

World Travel Guide has been published since 1982. Today it carries around 220 country guides plus city guides, and it is owned and operated by Occam Digital. That makes it useful in a way a client story cannot be. We can name it, you can open it, and you can ask an AI assistant a question about a country and see where the answer comes from.

What changed in how travellers find a guide?

Two things, and neither was in the guide's control.

First, the booking sites and aggregators took the generic destination searches. A query like the name of a city plus the word hotels returns pages with more budget behind them than any reference site will ever have. Fighting for those results would be a waste of money, and we say the same to hospitality clients.

Second, a growing share of practical travel questions are now asked of AI assistants rather than typed into a search box. What documents do I need, when is the rainy season, what is the currency, is the tap water safe. Those are exactly the questions a destination reference has always answered.

Why does a reference site have to be quotable rather than ranked?

Because an assistant does not send a visitor to page one. It lifts a passage and, at best, names the source.

When a traveller asks an assistant about entry requirements for a country, the assistant fetches pages, reads the plain HTML, and composes an answer from the sentences it can lift cleanly. A guide whose facts sit in ordinary text, under a clear heading, on an address that has not moved in years, is a good source. A guide whose facts load after a script runs, or sit inside an image, is not there at all.

Rankings still matter for the demand that clicks. Quotability decides whether the guide exists in the answer layer. We treat the two as separate tests and we check both.

What rules do we run the property on?

The same rules we ask clients to accept, applied first to ourselves.

- One permanent address per destination. A country guide URL does not change when the design does. - Facts in the first HTML response. Nothing important waits for a click, a tab or a script. - An honest robots file. The AI crawlers are admitted and named, not blocked by a default we forgot to check. - A server log we read. Client-side analytics cannot see a crawler, so the log is the only record of which assistants fetched which pages. - No doorway pages and no spun near-duplicates. One good page per question beats fifty thin ones competing with each other.

How do we know any of this works?

We do not publish a percentage, and we would not believe one from anyone else.

What we can show is a process and an open test. The server log tells us which AI crawlers fetched which guides in a given month, so the claim that assistants read the site is a matter of record, not of faith. The rest of the evidence is available to you directly: open a country guide, read it without JavaScript, then ask an assistant a practical question about that country and look at where the answer came from.

We would rather offer a test you can run than a number you have to take on trust. That is the standard we hold client work to, and it would be odd to lower it for our own property. Price bands for the equivalent client work sit on Pricing.

What does this mean for an operator?

You cannot outspend the booking sites, and you do not need to.

The booking sites answer the first question: where can I stay, and for how much. They cannot answer the second one, which is about your specific property, trip or service, because only you know the answer. Who the stay suits. What is included. What the first day looks like. How to book directly and what that changes. Publish those answers as plain sentences on your own domain, on addresses that will still work next year.

The sector page for travel and hospitality sets out what we change for an operator. The service that does most of the work is Search and AI Visibility. Where the site cannot yet be read by a crawler, the fix is Website Development first.

Key takeaways

- A reference site cannot win generic destination searches against booking sites. It can stay the source an assistant quotes on practical questions. - Permanent addresses, facts in plain HTML, an honest robots file and a server log you read are the whole method. None of it needs a new tool. - We run these rules on a property we own before asking a client to accept them, and we name the property so you can check. - No percentage is claimed. The test is open: read a guide without JavaScript, then ask an assistant and see where the answer comes from.

If the booking sites have taken your search results and you still want to be the operator an assistant recommends, start a conversation. We will say whether the pages can be quoted as they stand, or whether the site needs to be readable first.

World Travel Guide is owned and operated by Occam Digital. This case study describes our own property, not a client engagement, and it is general information about the work rather than a promise of identical results for any other site.