Nobody Needs Another “Hotels in Paris” Page

For a while I was building the obvious thing — big landing pages for "hotels in Paris," "hotels in London," the cities everyone types into a search box. Ten thousand sites already do that. I was about to become the ten-thousand-and-first, and lose.

Then I looked at what my site actually gets found for, and not a single city page was on the list. Every page pulling real search traffic was an event — a named band, a Test match, an eclipse. The cities were a mirage: most of that traffic was crawlers walking my own homepage links, not anyone looking to book a room.

That flipped the whole idea for me. The question was never which city — it's why the trip is happening. A festival. A fixture. Four minutes of totality over the Moroccan coast. Nobody books "a hotel in Reading"; they need somewhere to crawl back to after Florence + The Machine finish at Richfield Avenue.

So I rebuilt local-hotel.com to start from the event, not the place. Point it at something real and it finds the beds within walking distance: Reading Festival, the second Test at Lord's, the 2027 eclipse seen from Tangier. The whole events list works the same way — the specific stuff the big platforms never bothered to index properly.

The giants optimise for the words everyone searches, where they will always outspend me. I cannot win "hotels in Paris." But "hotels near Craven Cottage," or "where to stay for the Tangier eclipse" — those are queries with almost no competition, and they are exactly the ones my site already surfaces for. Same global supply as the giants, checked against their benchmark on every rate and never marked up above it; the difference is that my site understood the trip.

It's why the eclipse I wrote about chasing already has its own pages — Tangier, Cádiz, Málaga, Luxor, each with its own beds. I am not trying to be everywhere. I am trying to be the one place that already knew where the traveller was going.