Architecture & Findability
Internal Linking & Topic Cluster Standard
Help people and crawlers find the next best page without guesswork. This standard defines hubs and clusters, shows how to write anchor text that adds meaning, explains breadcrumbs, and gives you copy-paste patterns for read-next links and audits. It follows guidance from Google Search Central, NN/g, and web.dev.
Objective and scope
Give every page a clear place in the site and a few confident links to the next step. Google calls internal links “important for your site visitors and for Google” and advises using descriptive anchor text, consistent navigation, and crawlable markup. See the Search Central docs on helpful content, site structure, crawlable links, and breadcrumbs.
References: helpful content, SEO starter guide, crawlable links, breadcrumbs. For readable link text and scanning behavior see NN/g link text.
Principles
One hub per topic
A hub page introduces the topic and routes to key subpages. Duplicate hubs split signals and confuse readers. Keep one canonical hub and consolidate variants.
Anchors carry meaning
Links should describe the destination. Avoid “click here.” Good anchors improve understanding and can help models infer relationships.
Paths stay stable
Use simple, crawlable links and avoid JS-only navigation. If structure changes, add a single 301 or 308 redirect and update internal links.
Accessibility matters. WCAG requires that link purpose be clear from the link or its context. See W3C’s guidance on link purpose.
Hubs and clusters
Build clusters that mirror how users research and decide. A typical cluster has a hub, 5 to 12 subpages, and connective “read-next” links between siblings.
Suggested cluster types
- Definition hub with glossary subpages
- Comparison hub with vendor pages and vs articles
- Use case hub with role or industry pages
- Implementation hub with setup, migration, security
Minimum linking rules
- Hub links to all subpages with descriptive anchors
- Every subpage links back to the hub in the first screenful
- Each subpage links to at least two siblings as next steps
- BOFU pages link to proof and pricing from the body copy
Hub scaffold
<section aria-label="Topic hub">
<h2>Content Operations Hub</h2>
<p>Plan, deliver, and measure content with shared standards and workflows.</p>
<ul>
<li><a href="/resources/content-brief-specification/">Content brief specification</a></li>
<li><a href="/resources/internal-linking-topic-clusters/">Internal linking standard</a></li>
<li><a href="/resources/image-media-optimization-standard/">Image and media optimization</a></li>
</ul>
</section>Anchor text policy
Write anchors that set expectations. Keep them short, specific, and tied to the destination heading.
| Rule | Good | Avoid | Notes |
|---|---|---|---|
| Describe the target | Compare analytics tools | Click here | Improves comprehension and clarity |
| Match page language | On-page SEO checklist | SEO stuff | Consistent naming helps scanning |
| Use natural variants | Product analytics vs web analytics | Exact-match spam | Variety reads better |
| Keep it short | 2 to 6 words | Long sentences | Short anchors scan better |
Google recommends descriptive anchors and clear navigation in the Starter Guide. NN/g documents how people scan links and headings.
Read-next patterns
Give readers a confident next step that fits their intent. Use normal anchors inside visible sections.
Inline read-next
<p>Once your structure is set, validate it with a quick internal links audit.
Read next: <a href="/resources/semantic-url-slug-governance/">Semantic URL and slug governance</a>.</p>End-of-page block
<aside aria-label="Read next" class="card">
<h3>Where to go next</h3>
<ul>
<li><a href="/resources/content-brief-specification/">Define briefs and acceptance criteria</a></li>
<li><a href="/resources/image-media-optimization-standard/">Optimize images and media</a></li>
</ul>
</aside>Keep these links crawlable. Avoid onclick handlers that hide the real destination from crawlers. Search Central recommends standard anchors for discoverability.
Special cases: pagination and faceted states
Pagination
- Use simple anchors for pages 1, 2, 3
- Make the first page the canonical
- Keep titles and headings consistent
Keep links crawlable. Do not rely on JS-only infinite scroll without fallback. See Google’s crawlable links guidance.
Faceted and filtered views
- Expose crawlable links for the most important states
- Use a clean canonical for the default view
- Avoid parameter combinations that create duplicates
Audit and maintenance
Run a quarterly review. Fix orphans, stale anchors, and redirect chains. Validate that hubs still route to the right set of subpages.
Minimum audit checks
- Every subpage has a link to its hub
- Every hub links to all subpages
- No “click here” anchors in body copy
- No links through redirect chains
Content hints
Scan for opportunities to add useful cross-links. NN/g shows that descriptive links and nearby headings improve scanning and task success.
Structured data
Validate breadcrumbs and Article markup when you change structure. Use Google’s Rich Results Test and monitor Search Console enhancements.
Simple crawl script idea
// pseudo: fetch pages, extract anchors, assert required links exist
// for each cluster: assert hub → all subs, each sub → hub, 2+ sibling linksMeasurement and KPIs
Measure how links change behavior and visibility. Use GA4 for engagement and conversions and Search Console for queries and click-through rate by folder.
Reader behavior
- Read-next click rate from article body
- Path flow: hub → subpage → BOFU
- Engaged sessions per user in a cluster
SEO signals
- Queries and CTR by cluster folder in Search Console
- Coverage and indexing for all cluster pages
- Rich results status for breadcrumbs
GA4 events example
gtag('event','anchor_click',{
anchor_text:'Semantic URL and slug governance',
location:'read_next',
cluster:'content-architecture'
});Mark key events as conversions when they represent progress. See GA4 events and conversions docs and the Search Console performance report.
Implementation checklist
- Choose hubs and write one-line purposes for each
- List required subpages per hub and map read-next links
- Add descriptive, short anchors inside the first screenful
- Implement breadcrumbs with visible HTML and JSON-LD
- Keep links crawlable and avoid JS-only navigation
- Run an orphan and redirect check, fix broken paths
- Track anchor clicks and hub flows in GA4
- Monitor folder performance and enhancements in Search Console
- Review quarterly and prune redundant pages
FAQ
How many internal links per page
There is no fixed number. Prioritize a handful of high value links near the top and a read-next block at the end. Focus on clarity and purpose.
Do exact-match anchors help
Use natural language that matches the destination heading. Repeating exact phrases everywhere reads poorly and adds little. Variety is fine when the meaning is clear.
Will site-wide nav links dilute signals
No. Navigation helps users and crawlers. Still give body links descriptive anchors so readers know why to click.
Should I nofollow internal links
Do not nofollow normal internal links. Use nofollow only for untrusted content or user-generated pages when appropriate. See Search Central guidance.