Design Your Site as a Connected Graph, No Dead Ends

A visitor lands on your themes page, likes what they see, and wants to know what templates use those themes. They look around. There is no link. The only way to get to templates is to scroll back up to the top navigation and start over, as if they had never been on the themes page at all. They followed their instinct, the instinct said "show me the related thing," and your site had no path to offer. So they do what people do when a site strands them: they leave. Not because the templates page was missing, but because the bridge between where they were and where they wanted to go did not exist. A dead end is its own kind of empty state, and the good ones drive action rather than letting the user fall off the edge of the experience.

This is the most common failure in website information architecture, and it is invisible to the team that built the site, because the team navigates by the top nav and never feels the dead end. A website is not a stack of independent pages connected only by a menu. The good ones are a connected graph, where a visitor can travel from any intent to the right page by following links inside the content, by association, without ever bouncing back to the navigation to restart. That connective tissue is the product as much as any individual page, and most sites are missing it.

The hub-and-spoke backbone

The structural foundation of a connected site is the hub-and-spoke model, which is the standard approach for a reason. You build one primary page for a broad topic, the hub, and support it with narrower pages, the spokes, organized around that central page. The hub gives a topic area one canonical home, and every detailed page underneath it is a one-click child of that home. This gives the site a clear structure where related pages reinforce each other and the whole cluster is easy to follow.

But hub-and-spoke is not just the hub linking down to its spokes. The linking has to flow in every direction. The hub links to the spokes, the spokes link back up to the hub, and related spokes cross-link to each other where their intent overlaps. A visitor on a detail page can go up to the overview, sideways to a sibling, or onward to a related topic, all from within the content, because the links are there. A site where the hub links down but nothing links back up or across is a one-way structure that strands users at the leaves, which is exactly the themes-page problem.

Contextual links carry the most weight, for users and for search

Here is the part teams underuse most: the strongest links are the ones inside the body of the content, not the ones in the chrome. Contextual internal links, placed naturally within the prose where they extend the reader's train of thought, carry the most relevance and, just as importantly, get far higher engagement than links sitting in a sidebar, footer, or recommendation widget. The reason is human. A link inside a sentence the reader is already reading rides on their existing momentum, and you can keep that momentum from ever stalling by making page navigations feel instant with speculation rules that prefetch the destination before the click. A link in a sidebar asks them to break their attention, look away from what they were doing, and evaluate a separate navigation element. Most people will not.

So when your content names a feature, a product, a category, or a concept that has its own page, link it right there, in the prose, where the reader's mind already reached for it. That inline link is the one they will actually follow, because it answered a question they were forming in the moment. A guideline that keeps this healthy is a handful of contextual links per page, with descriptive anchor text that says where the link goes, rather than a wall of links or repeated exact-match anchors. The goal is that wherever a reader's interest naturally points, a link is waiting to take them there.

The two failure modes to hunt down

Auditing a site for connectivity comes down to finding and fixing two specific problems.

• Stranded mentions. A page names something that has its own page, but renders it as dead text instead of a link. The reader hits a wall where their instinct expected a path. Every time your get-started page says "templates" or "themes" without linking them, you have created a stranded mention, a place where the user wanted to go deeper and you offered nothing.
• Orphan pages. A page that exists but receives no internal links from any other page. Because both users and search crawlers discover pages by following links, an orphan is effectively invisible during normal navigation and rarely ranks well even when its content is good. A page reachable only by knowing its URL is a page almost nobody reaches.

The fix for both is the same instinct applied page by page: when content names a subject with its own home, link it, and make sure every published page is reachable from at least one related page's content, not just from the navigation. A page no other page links to is a page you might as well not have published.

The persona test that proves it works

The way to know your site is actually connected, rather than just well-intentioned, is to trace real user journeys through it following only the links in the content, ignoring the top nav entirely. Pick your real personas. The buyer who wants to go from features to examples to pricing to signing up, where a pricing page that makes the right plan feel obvious is the page their journey has to land on cleanly. The designer comparing themes and templates and how editing works. The developer trying to find the API docs, then the page that generates a token, then the configuration guide, then the deploy instructions, where each step has to link to the next or the least-privilege token-scoping story strands halfway through, and where shipping an MCP server that survives real agent traffic is the kind of destination the docs cannot leave orphaned. For each persona, start where they would land and try to reach their goal using only in-content links.

Every point where they can only proceed by reaching for the top nav, or cannot proceed at all, is a strand to fix. The developer's path is a canonical test, because it almost always breaks: the API reference, the token-generation step, and the deploy guide each need to link to the next, or the story falls apart and the developer gives up halfway through a flow that should have flowed. If a persona can complete their journey by instinct, following links that live in the content, the site is connected. If they keep hitting the nav, it is a stack of islands wearing a menu.

Why this is the product, not decoration

It is tempting to treat internal linking as an afterthought or a search optimization tactic, something you sprinkle in at the end. That framing misses what it actually does. The connective tissue is what lets a visitor travel through your site the way they think, by association, moving from interest to interest without friction, which is exactly how a great site feels effortless to use. A site can have a beautiful page for everything and still fail this test, because beauty per page does not create paths between pages. The paths are a separate thing you have to build deliberately.

This is one of the things we obsess over when we build websites: mapping the page graph before building, linking every concept to its home as the content gets written, and running the persona traces before calling the information architecture done, so visitors travel by instinct rather than being forced back to the menu at every turn. It is the structural sibling of the small-scale care that produces micro-interactions that feel alive: both are about the product feeling considered at every touch rather than only on the pages someone remembered to polish. The same thinking shapes how we structure our own process and the way pages connect across everything we ship, because a site that strands its users at the leaves is a site leaking the very visitors it worked to attract.

The test is simple enough to run on your own site today. Pick a page, find every mention of something that has its own page, and check whether it is a link. Then pick a persona and try to complete their journey using only what is in the content. Wherever you reach for the nav, you found a strand. Fix the strands, and your site stops being a collection of stranded islands and becomes what the good ones are: a connected graph a visitor can travel by following their own instincts, never hitting a dead end, never having to start over.