Faragiri

Learn Topic clusters Site structure

An archery supplier had 34 pages about bows and no page about bows, then built one hub and pointed 34 links at it in the words a customer would use.

4Sections
4Min read
4Depth

A cluster is one hub, its supporting pages, and the links in both directions. Ampleforth Archery sells bows, arrows and club equipment and had 34 pages about recurve bows and no page about recurve bows: 34 answers to specific questions, and nothing a person could read to understand the subject.

The hub was written in March 2026, 1,400 words, and every one of the 34 was edited to link up to it. The hub went from nothing to position 7 in four months for the query it was written for, and eleven of the 34 moved up as well without being touched.

What a hub is

The hub is a page somebody would want to read, not an index. Ampleforth's hub explains how a recurve bow is put together, what draw weight means for somebody who has shot twice, and why a first bow is bought in a lower weight than anybody expects. A list of links to 34 pages would have been a menu with a heading.

Clusters

One hub, four branches, and what hangs off each

The hub explains the subject in order, while each branch groups the specific questions people ask next.

  • Choosing a first bow
    • Draw weight for a beginner
    • Bow length against draw length
    • What a starter kit should contain
  • Looking after it
    • String wax and when to use it
    • Storing limbs over winter
Recurve bows: the hub
  • Setting it up
    • Stringing a bow safely
    • Bracing height and how to measure it
    • Nocking point position
  • Shooting it
    • Anchor point
    • Why arrows fly left

Ten of the 34 supporting pages are drawn here. A theme archive listing 34 links has no prose and competes with the pages instead of introducing them.

An index page generated by a theme is not a hub, and this is the commonest substitute. The archive page listing every post tagged recurve existed all along, had no prose on it, and was competing with the 34 rather than describing them, which is the same failure as pages that dilute the ones that matter.

The links, and the words in them

Every supporting page links up to the hub using words a customer would use. Not the page title, and not one phrase repeated on every one of them: how a recurve bow is put together, choosing a first draw weight, and what to buy for a beginner all point at the same page and describe three true things about it.

Internal links

Upward anchors describe the hub in customer words, while sideways links point only to the next question.

  • Varied upward anchors
  • Knowing where to stop
  • Sideways next steps
  • Varied upward anchorsEach leaf uses a real customer phrase such as choosing a first draw weight rather than repeating one title.
  • Knowing where to stopStringing a bow answers stringing and links back to the hub for draw weight so it never grows into a second hub.
  • Sideways next stepsStringing links across to bracing height and string wax because a reader asks those two questions in that order.

Sideways links follow subject judgement rather than a tool report: what a person who just strung a bow needs to know next.

A supporting page answers one question and hands the rest back to the hub. The page on stringing a bow answers stringing and says nothing about draw weight; the link up is the sentence that lets it stop. That is what keeps a supporting page from growing into a second hub, which is how clusters collapse.

Sideways links go to the two pages somebody would actually read next. From stringing, that is bracing height and string wax, because a person who has just strung a bow has those two questions in that order. It is a judgement about archery rather than about search, and it is the part no tool can supply.

Where this stalls: the subject nobody has decided

A cluster is a decision about the subject before it is a decision about links. Ampleforth spent a fortnight arguing about whether recurve and barebow are one subject or two, and that argument had to be settled before a single link could be written, because the answer decides whether there is one hub or two.

Scope decision

Ampleforth had to settle whether recurve and barebow were one hub or two before a single link could point anywhere.

Subject decided firstSettle the boundary before editing pages.
Links added firstAmpleforth's earlier 2024 attempt.
Starting questionAre recurve and barebow one subject or two?Which existing page looks most important this week?
Link targetA dedicated hub explaining how bows workThe shop category page for buying equipment
Resulting mapDeliberate cluster with clear ownershipA record of guesswork from the week links were added
Query fitAnswers the broad informational queryPage about buying cannot answer the query

Skipping the two-week argument feels faster until every link points at a category page that cannot satisfy the reader.

The stall is that the argument feels like a waste of time next to the visible work of adding links, so the links get added first, to whichever page seems most important, and the structure that results is a record of what people thought in the week they did it. Ampleforth's earlier attempt in 2024 pointed everything at the shop category page, which is a page about buying rather than about bows and could never have answered the query.

What it looks like when it is working

The eleven supporting pages that moved without being edited are the evidence. Nothing about them changed except that they now sit under a page describing them and link up to it, and the description they collectively carry is now attached to something. The other 23 did not move, which is the ordinary result and not a failure.

Verification

Four signals that a built cluster is holding together

Once the hub exists and the leaves link up, two free tools show whether the structure matches the plan.

One query, one page, working together
  • Unaffected pages are normalEleven supporting pages climbed without edits; the other 23 stayed still, which is an ordinary result.
  • Nearly every leaf links upAhrefs Webmaster Tools reports internal links and crawl depth so you check the cluster as built.
  • Broad vs narrow queries splitSearch Console shows the hub holding the broad query while supporting pages keep narrow ones.
  • No rival second hubIf a supporting page starts collecting the hub query, two pages are competing for one search.

Anchor text decided one page at a time

Search Console replaced the keyword detail removed from analytics in 2011 and remains the check on whether a leaf is drifting into a rival hub.

Ahrefs Webmaster Tools crawls a site you have verified and reports internal links and crawl depth, which is the cluster as built rather than as intended. It is free for a verified site and it replaced paying for a full crawl of something you already own. The number to read is how many pages link to the hub, and it should be nearly all of them.

Search Console shows whether the hub is collecting the broad query while the supporting pages keep the narrow ones, free, replacing the keyword data Google removed from analytics in 2011. Where a supporting page starts collecting the hub's query, the cluster has developed a second hub and it is two of your pages competing for one query.

Which query each page owns before any of this is drawn is one query, one page, decided deliberately, and the anchor text carrying the whole arrangement is decided one page at a time at sending authority where you want it. The cluster itself is the working unit of how pages relate, which decides what a site is about.

Alongside this

Above this