I want to walk you through exactly how I build a topic cluster for an independent hotel, because it is the single highest-leverage content thing I do, and almost nobody at the boutique level is doing it on purpose. Most hotel sites are a pile of disconnected pages: a rooms page, a “things to do” page somebody wrote in 2019, a blog with three posts about a Christmas event that already happened. Google and the AI answer engines look at that and see a brochure, not an authority. A topic cluster fixes that. Done right, it is the structure that makes both classic search and tools like ChatGPT and Google’s AI Overviews treat your property as the expert on a thing people actually search for.
Let me show you the real reasoning, not the LinkedIn version.
What a topic cluster actually is (the 90-second version)
A topic cluster is one pillar page that covers a broad guest intent fairly completely, surrounded by several spoke pages that each go deep on one narrow slice of that intent. Every spoke links up to the pillar. The pillar links down to every spoke. They reference each other where it makes sense. That internal web of links, all pointing at one tightly-related set of pages, is what tells a search engine: this site has real depth here, not one thin page.
Here is why I care about it in 2026 specifically. The old game was “rank one page for one keyword.” The new game is that AI answer engines synthesize an answer from sources that cover a question thoroughly and consistently across multiple pages. When ChatGPT or an AI Overview is assembling “where should I stay near [your area] if I want a quiet, walkable trip,” it is far more likely to pull from a site that has a coherent, cross-linked set of pages on exactly that than from a site with one orphaned blog post. Topical depth is the signal. A cluster manufactures that depth on purpose.
Search engines reward the page. Answer engines reward the source. A topic cluster is the only structure that feeds both at once, because it makes one page rankable and the whole site quotable.
Step 1: Pick one guest intent, not one keyword
This is where most hotels go wrong, so I am slow here. I do not start with a keyword. I start with a guest intent — a real thing a specific guest is trying to figure out before they book.
For a boutique property, my favorite intents are the ones the OTAs are bad at answering. Booking.com can show a price and a photo, but it cannot genuinely help someone plan “a romantic weekend within walking distance of good restaurants” or “a dog-friendly stay near the trails.” Those planning intents are wide open, and they are exactly what people now type into AI tools in full sentences.
So let’s say I run a small inn and I pick the intent: “a relaxed dog-friendly weekend in our town.” That is broad enough to be a pillar and specific enough to own. I would never try to rank for the head term “dog friendly hotel” against the chains — I would lose. But “a dog-friendly weekend in [specific town],” covered properly, is mine to take.
A quick gut-check on volume so we are being honest: the broad AI-search terms people throw around are big — “aeo” does around 27,100 US searches a month, “ai seo” about 8,100, “generative engine optimization” about 5,400, and even “hotel seo” only about 590. Your guest-intent clusters will be far smaller in raw volume than those. That is fine. A cluster that pulls 40 highly-relevant planners a month who are deciding where to sleep is worth more than 4,000 drive-by visitors who will never book.
Step 2: Draft the pillar as the “complete answer”
The pillar page is the one I want to rank and the one I want AI to quote. Its job is to answer the whole intent at a useful-but-not-exhaustive depth, then hand off the details to the spokes.
For my dog-friendly weekend pillar, the outline looks like:
- A short, honest intro (why this town is genuinely good for dogs, not marketing fluff)
- Where to stay (my property, framed as the obvious base — but not a hard sell)
- A sample two-day itinerary
- Dog-friendly restaurants and cafes nearby
- Trails, parks, and off-leash areas
- Practical stuff: vet on call, dog-sitting, weather, what to pack
- An FAQ block answering the literal questions people ask
I write the pillar to be genuinely complete on the summary level. Each of those sections is a candidate spoke — a place where I can say “here’s the gist” on the pillar, then link to a full article. That is the hand-off, and it is what makes the cluster feel deep instead of bloated.
One detail people miss: I make the pillar’s headings match how people phrase questions out loud, because that is how they query AI. “What are the best dog-friendly restaurants near [town]?” beats a cute heading like “Paws & Plates.” Clever headings are invisible to answer engines.
Step 3: Choose spokes that each own one question
Now I break the intent into the narrow questions a real planner asks, and each becomes a spoke. The test for a good spoke: could it be the complete answer to one specific search? If yes, it is a spoke. If it is just a paragraph, it stays on the pillar.
Here is the cluster I would actually build:
| Page | Type | The one question it answers |
|---|---|---|
| A relaxed dog-friendly weekend in [town] | Pillar | Where do I stay and what do I do with my dog here? |
| The 12 most dog-friendly restaurants near [town] | Spoke | Where can we eat with the dog? |
| Our favorite dog walks and off-leash parks | Spoke | Where can the dog actually run? |
| What to pack for a weekend away with your dog | Spoke | How do I prepare for the trip? |
| Rainy-day plans for dog owners in [town] | Spoke | What if the weather turns? |
| Our pet policy, fees, and dog amenities (real talk) | Spoke | Will this specific hotel take my dog, and at what cost? |
Notice that last spoke. It is half guest-service, half conversion. It is also the page that quietly does the most booking work, because it answers the exact friction question — “will they take my dog and how much” — that sends people back to an OTA to check. Answering it clearly on my own site is part of how I claw back direct bookings instead of leaking them. If you want the math on why those direct bookings matter so much, I broke it down in the real cost of OTA commissions — when you are handing over roughly 15 to 25 percent on every OTA reservation, owning these planning pages is not a vanity project, it is margin.
Step 4: Wire the internal links like you mean it
This is the part that does the heavy lifting and the part everyone phones in. A cluster is only a cluster because of the links. Loose pages with no links are just pages.
My rules:
- Every spoke links up to the pillar with descriptive anchor text — “plan your whole dog-friendly weekend” — not “click here.” The anchor tells the engine what the pillar is about.
- The pillar links down to every spoke from the relevant section. The restaurants section links to the restaurants spoke, and so on.
- Spokes cross-link where it is natural. The “what to pack” spoke links to the “dog walks” spoke, because someone planning a hike needs both. I do not force it; forced links read as spam to both humans and machines.
- I keep the cluster mostly self-contained. A topic cluster works partly because the link equity stays concentrated. If every page also links to forty unrelated pages, the signal dilutes.
The links are the architecture. Without them you have a pile of bricks. With them you have a building, and Google can finally tell what the building is for.
If you are nervous about internal linking and site structure generally — which orphan pages exist, what is linking to what — that is a foundational SEO problem, and it is exactly the kind of thing I work through in hotel SEO services. A messy link graph quietly caps everything else you do.
Step 5: Make every page quotable for AI
Once the structure exists, I optimize each page so an answer engine can lift a clean passage out of it. This is the AEO/GEO layer, and it is mechanical:
- Lead with the answer. The first two sentences under each heading should state the answer plainly, then elaborate. AI tools grab the top of a section.
- Use specifics, not adjectives. “Three off-leash parks within a ten-minute drive” is quotable. “Plenty of green space” is not.
- Match real questions. I mine the actual phrasing from AI chats and “People Also Ask,” then use those as my subheadings and FAQ entries.
- Add structured data. FAQ and article schema where it fits, so the meaning is machine-readable, not just human-readable.
If your hotel does not show up at all when you ask ChatGPT for a recommendation in your area, that is the symptom this whole layer treats — I wrote about diagnosing it in is your hotel invisible to ChatGPT. The cluster is the supply side: you cannot get cited for depth you have not published. The detailed mechanics of getting pulled into AI answers is its own discipline, which is what my AI visibility, AEO and GEO work is built around.
Step 6: Publish in an order that compounds
I do not dump all six pages on the same day. I publish the pillar first, even in a leaner form, so the spokes have something to link up to. Then I ship one spoke a week, linking it into the pillar as I go, and updating the pillar’s relevant section to point down at the fresh spoke. By the time the cluster is complete, the internal links are already mature and the pillar has had a few weeks to get discovered and indexed.
A realistic timeline so we keep expectations honest: a brand-new cluster on a small hotel site usually takes three to six months to gain real traction in search, longer if you are chasing competitive terms. There is no guaranteed ranking — anyone who promises you a number-one spot is selling something. What I can say is that this structure stacks the odds correctly, and clusters compound: the spokes you publish now keep feeding the pillar’s authority long after you wrote them.
A few things I have learned the hard way
One intent per cluster. The moment I notice a cluster drifting — dog-friendly weekends bleeding into general “things to do” — I split it. Two muddy clusters always lose to two clean ones.
Refresh the pillar, retire dead spokes. A cluster is a living thing. When a restaurant closes or a trail reroutes, I fix the spoke. Stale specifics destroy the trust that made the page quotable in the first place.
Tie clusters to booking. Every cluster should have at least one spoke that does conversion work and a clear path to your booking engine. Topical authority that never points at a “check availability” button is a hobby, not a strategy. If your direct-booking flow leaks once people land, that is a separate fix — see book-direct conversion work — but the cluster is what gets the right person there in the first place.
That is the whole method: one intent, one pillar, a handful of spokes that each own a real question, wired together with intentional links and written so both Google and the AI engines can quote you. It is not glamorous. It is a spreadsheet, an outline, and the discipline to publish on a schedule. But it is the closest thing I know to building durable authority for an independent hotel — the kind that keeps pulling in planners and slowly improves your OTA mix instead of renting visibility you lose the day you stop paying.
If you want, I will map your first cluster with you — pick the one guest intent your property is genuinely best at, sketch the pillar and spokes, and hand you the outline. Grab a free intro call and we will draw it on the whiteboard together.