Structure & Authority
Topical Authority and Internal Linking: Build Hubs and Paths That Earn Visibility
Visibility grows when your site explains a topic clearly and links pages in a predictable way. This guide shows how to plan clusters, design hubs and spokes, write anchors, use breadcrumbs and schema, handle duplicates, and measure impact with Search Console and GA4.
Definitions
The degree to which your site covers a subject with depth and clarity. Practically, it looks like well structured hubs, coherent spokes, and links that help readers navigate the topic without guessing.
A set of related pages aligned to one theme. A cluster usually includes a hub, definitions, how to guides, comparisons, use cases, and a solution or pricing destination.
A crawlable anchor that connects pages on your site. The words you choose in that anchor tell both readers and systems what to expect.
Why topical authority matters
People skim before they read deeply, so your structure has to do more work than your prose. Nielsen Norman Group’s usability studies show users often read a small share of words, which is why hubs, tables, and clear anchors outperform walls of text. See NN/g on the F-pattern and on how much users read.
Mobile leads global web usage, which compresses attention and punishes clunky navigation. StatCounter’s live dashboard tracks the split between mobile and desktop. Review the mobile vs desktop share to calibrate your design choices.
Quality and eligibility rules still apply. Google’s Search Essentials and the helpful content guidance explain the baseline. Your cluster strategy should satisfy those rules while making pages easier to quote and easier to navigate.
How systems read your site
Links and anchors
Links convey relationships. Systems rely on crawlable anchors to discover and understand pages. Avoid click handlers without URLs. See Google’s note on crawlable links.
Structure and hierarchy
Short, predictable paths help. The SEO Starter Guide shows examples of clean hierarchies and breadcrumb use. Review the site hierarchy section in Google’s SEO Starter Guide.
Experience signals
Fast, stable pages tend to perform better. Keep an eye on Core Web Vitals targets at web.dev and design clusters that remain performant as you add links and media.
Design a cluster
Start with a theme that maps to a job to be done and a revenue path. Choose a hub and five to nine spokes with clear roles. Keep the cluster small enough to ship in one quarter and broad enough to answer the obvious follow ups.
Example layout
- Hub: comprehensive guide that defines the topic and links out.
- Definitions: short pages that answer what and why.
- How to: step based guides with a small table and a checklist.
- Comparisons: head to head and alternatives pages.
- Use cases: role or industry focused pages.
- Solution: product or service page with one primary CTA.
Internal link blueprint
- Spokes link to the hub at top and bottom.
- Each spoke links to two siblings that a reader would need next.
- Every spoke has one BOFU destination with a clear CTA.
Sample architecture
| Layer | Purpose | Slug | Links out |
|---|---|---|---|
| Hub | Defines the theme and orients readers | /analytics/ | All spokes + solution |
| Definition | Answer what and why in 120 words | /analytics/what-is-product-analytics/ | Hub + how to |
| How to | Actionable steps and a checklist | /analytics/how-to-build-dashboards/ | Hub + template + solution |
| Comparison | Shortlist vendors with decision table | /analytics/tool-a-vs-tool-b/ | Hub + solution |
| Use case | Role based outcomes and proof | /analytics/for-revenue-teams/ | Hub + case study + solution |
| Solution | Outcome led product page | /solutions/product-analytics/ | Pricing + demo |
Write a great hub
The opening
- One sentence definition plus an answer block.
- Three bullets that summarize the steps or subtopics.
- A compact FAQ to mirror common questions.
Link layout
- Use descriptive anchors that match spoke H2s.
- Group links by intent: learn, compare, implement.
- Add a small visual index if the cluster is large.
Proof and CTA
- Short proof block with one case study or metric.
- One primary next step for evaluators.
- Secondary path to a template or checklist.
Anchors and link copy
Anchor text is small but powerful. It sets expectations for humans and clarifies relationships for systems. Be specific and keep style consistent across the cluster.
Good anchor patterns
- onboarding checklist instead of this post.
- compare analytics tools instead of click here.
- migration guide from tool A instead of learn more.
Implementation tips
- Use real anchors with href. Avoid JS only links. See Google’s note on crawlable links.
- Place links where readers decide, not just at the end.
- Limit repetitive anchors in the same paragraph.
URLs, breadcrumbs, and navigation
URL design
- Keep slugs short and descriptive. Avoid date folders.
- Use one home per concept. Consolidate near duplicates.
- Prefer lowercase and hyphens. Do not encode intent into parameters if a static path fits.
Breadcrumbs
Breadcrumbs help users and systems understand hierarchy. Mark them up with structured data. See Google’s Breadcrumb guide.
<script type="application/ld+json">
{
"@context":"https://schema.org",
"@type":"BreadcrumbList",
"itemListElement":[
{"@type":"ListItem","position":1,"name":"Analytics","item":"https://example.com/analytics/"},
{"@type":"ListItem","position":2,"name":"What is product analytics","item":"https://example.com/analytics/what-is-product-analytics/"}
]
}
</script>Navigation
- Global nav stays shallow. Do not list every spoke.
- Use hub landing pages to organize deeper exploration.
- Cross link related hubs with small, descriptive menus.
Duplicates, canonicals, and pagination
Duplicates and variants
- Pick a canonical URL for each concept. Use <link rel=”canonical”> for minor variants. Review Google’s canonicalization notes in the duplicate URL guidance.
- Merge near duplicates. 301 the weaker URL and repoint internal links.
- Keep parameters for tracking out of indexable URLs.
Pagination and indexes
- Use logical, crawlable pagination for long indexes.
- Ensure each page is useful on its own. Add contextual links.
- Link the index to key spokes and the hub with descriptive anchors.
Structured data choices
Article
Use on guides, hubs, and most educational pages. Keep markup aligned with visible content and follow Google’s structured data policies.
FAQ and HowTo
FAQ for compact questions and answers. HowTo for clear steps with required elements. See the docs for FAQPage and HowTo.
BreadcrumbList
Use across clusters to reflect hierarchy and improve clarity. Validate with the Rich Results Test.
External citations and E-E-A-T signals
Authoritativeness grows when you cite reputable sources and show experience. Link to primary research, official documentation, and recognized institutions. Examples you can rely on: Statista for market data, Nielsen Norman Group for usability, and Google’s official Search Essentials.
Measurement and diagnostics
Coverage
- Queries per page for the cluster in the Search Console Performance report.
- Index status and enhancement eligibility in Page indexing.
- Ratio of orphan pages to total pages. Reduce orphans by linking from hubs and siblings.
Movement
- Average position and CTR for hub and top spokes.
- Clicks from hub to spoke and spoke to solution in GA4. See GA4 help on events.
- Scroll depth to the link index and FAQ interactions.
Outcome
- Assisted conversions for the cluster using GA4 attribution.
- Opportunities that touched a hub or spoke inside your lookback window.
- Time to publish and refresh cadence for cluster pages.
Quick diagnostics table
| Symptom | Likely cause | Fix |
|---|---|---|
| Hub ranks but spokes do not | Weak internal links and anchors | Link from hub sections with specific anchors that match H2s |
| Spokes rank but do not convert | No BOFU path | Add one solution page link per spoke with a clear CTA |
| High impressions, low CTR | Title and meta mismatch | Align title and meta with the answer block and intent |
| Pages fall in and out of index | Thin duplication or weak linking | Consolidate duplicates and strengthen links from hub and nav |
30 60 90 rollout
Days 1 to 30
- Pick one theme. Define a hub and five to seven spokes.
- Draft the hub outline and link index. Confirm anchors.
- Publish the hub and two spokes with Article and Breadcrumb schema. Validate in the Rich Results Test.
Days 31 to 60
- Publish two more spokes and one comparison page.
- Add compact FAQs and small tables to each page.
- Instrument GA4 events for hub to spoke and spoke to solution clicks.
Days 61 to 90
- Publish the solution page for the theme with one primary CTA.
- Review queries per page, CTR, and assisted conversions. Prune or consolidate weak pages.
- Document anchors, schema, and refresh dates for the cluster.
FAQ
How many spokes per hub
Five to nine is a practical range. Enough to show depth without overwhelming readers. Expand only after the first set moves the metrics you care about.
Do we need structured data on every spoke
Use Article on most educational pages. Add FAQ where you include clear question and answer blocks. Use BreadcrumbList across the cluster. Keep markup aligned with visible content and validate regularly.
What if two topics overlap
Pick a primary home and differentiate the angle in the opening paragraph. If confusion persists, merge pages and redirect the weaker URL.
Are external links risky
No. Linking to reputable sources improves clarity and trust. Qualify paid or promotional links with the right attributes per Google’s guidance.
