A great set of pages with bad internal linking is a library with no index.

You can build a perfect topical map, write every page on it well, and still end up with a site that doesn’t rank — because the pages aren’t connected in a way that tells a search engine they belong together. Internal links are the connective tissue. They route both readers and crawlers through the site, they pass authority between pages, and they’re the signal that says “these forty pages are one body of work on one topic.” Get the architecture right and the cluster behaves like a cluster. Get it wrong and you’ve got a library where every book is on the floor.

Hub-and-spoke: pillar ↔ cluster, sibling ↔ sibling

The backbone of an authority site’s linking is hub-and-spoke. The pillar page (the hub) links down to every cluster page that sits under it. Every cluster page (a spoke) links back up to its pillar. And cluster pages link sideways to their siblings wherever the topics genuinely touch — “AC repair vs. replace” links to “AC repair cost” because a reader on one wants the other. That’s the shape: down from the hub, up from the spokes, across between spokes that are actually related.

What it isn’t: every page linking to every other page. That’s not a structure, it’s a mesh, and a mesh tells a search engine nothing about which pages are central. Links should follow the real relationships — the pillar is central, so it gets linked from all its spokes; two siblings on adjacent topics link to each other, but a sibling on an unrelated topic doesn’t. The link graph should be a readable map of how the topic decomposes, which is exactly what the cluster structure is in the first place. The links make the structure visible.

Anchor text done right

Anchor text — the clickable words in a link — tells the destination page (and the search engine) what that page is about. Done well, it’s descriptive and varied. Done badly, it’s the same exact-match keyword phrase stuffed into every link, which reads as manipulation and gets treated as such.

• Be descriptive. The anchor should tell the reader what they’ll get. “How many pages a site needs to rank” is a good anchor for that page. “Click here” tells the reader nothing and the search engine less.
• Vary it. The same destination page should be linked with different, natural phrasings across the site — sometimes the page’s topic, sometimes a question it answers, sometimes a phrase that fits the sentence it’s in. A page that’s linked twenty times with the identical anchor phrase looks engineered. A page linked twenty times with twenty natural variations looks like a page people genuinely reference.
• Don’t force the exact keyword. If the natural way to refer to a page in a sentence isn’t the keyword you’d love it to rank for, use the natural phrasing. Search engines have been discounting exact-match-anchor stuffing for over a decade. Write the anchor a careful editor would write.
• Let context do work. A link inside a paragraph about the topic carries more meaning than the same link in a bare list — the surrounding sentence tells the search engine what the link is about. Which is the whole argument for contextual links, below.

Link depth and orphans

Two rules, and they’re close to non-negotiable on an authority site.

First: every page reachable in three clicks or fewer from the homepage. Click depth is how far a page is from the front door. Pages buried five or six clicks deep get crawled less, get less authority flowing to them, and effectively don’t exist as far as ranking goes. A well-structured site keeps everything within three clicks — home to pillar to cluster page, at most. If something’s deeper than that, the structure is wrong, not the page.

Second: no orphans. An orphan page has zero internal links pointing to it — nothing on the site links in. Search engines find it only via the sitemap, if at all, and treat it as disconnected from everything. On a real cluster every page is linked from at least its pillar and ideally a sibling or two as well. Before an authority site ships, the orphan count should be zero — and it should be re-checked whenever pages are added, which is one of the things a care plan watches for. (The flip side — adding so many pages that the structure frays — is covered in whether more pages is always better: more pages only helps if every one of them is properly wired in.)

Breadcrumbs — UX and structured data at once

Breadcrumbs (Home › Topical authority › Internal link architecture) earn their place twice over. For the reader, they show where the page sits and give a one-click route back up the hierarchy. For search engines, when marked up with BreadcrumbList structured data, they declare the page’s place in the site’s structure — and that hierarchy often shows up in the search result itself instead of a raw URL. They’re a small piece of markup that reinforces the cluster structure on every single page. An authority site should have them everywhere, generated from the actual page hierarchy, not hand-typed.

Contextual links vs. navigational links — you need both

Contextual links live in the prose — inside a paragraph, where the surrounding text gives the link meaning. These carry the most weight, because the search engine reads the sentence around the link and understands what it’s pointing at and why. A contextual link is also the kind a reader is most likely to follow, because it appeared exactly where they wanted more.

Navigational links live in the furniture — the main nav, the footer, breadcrumb trails, “related” card grids, in-content link lists. These are consistent, predictable, and they’re how a reader who didn’t follow a contextual link still finds the rest of the cluster. They also guarantee coverage: the “related” grid at the bottom of every cluster page means no sibling is more than one click away even if the prose didn’t happen to mention it.

You need both because they do different jobs. Contextual links handle relevance and reader intent; navigational links handle coverage and consistency. A site that’s all prose links has gaps; a site that’s all nav links has no contextual relevance signal. The right architecture has dense contextual linking inside the content and a clean navigational layer around it.

Link because it helps the reader. Every link that survives that test is also the link a search engine wants to see. The two audiences agree more often than people think.

Doing it at scale without spam

On a 12-page site you can place every link by hand. On a 150-page authority site you can’t — and the temptation is to automate it crudely: every page links to every other page in the cluster, identical anchor text, a wall of links in the footer. That’s spam, and it works against you. Modern search engines are good at spotting link patterns that exist to manipulate rather than to help.

The way you scale it cleanly is to automate only the relationships that are genuinely true. A cluster page should programmatically link to its pillar — that relationship is always real. It should link to the FAQ pages under its topic — also real. It should link to its location siblings if it’s a location page — real. What you don’t do is generate links between pages whose only connection is “they’re both on the site.” The programmatic layer encodes the structure from the topical map; the structure is real, so the links are real. Anything beyond that — the cross-topic link that happens to make sense in a specific paragraph — stays a hand-placed contextual link, written by someone who read the page.

That’s also where programmatic SEO sits relative to this: it’s the right tool when the relationships are templatable (service × location, say), and the wrong tool when they aren’t. Used for the real relationships, it’s how you wire 150 pages correctly. Used to manufacture relevance, it’s how you get a manual action. The authority sites build does the structural linking programmatically and the contextual linking by hand, which is the only combination that scales and stays clean. If you want the thesis behind why this whole apparatus beats a prettier brochure site, the topical authority overview lays it out.