S.
  • Services
  • For you
  • Solutions
  • Work
  • About
  • Know-how
  • Blog
Start a project
EN/PL/RU
  • Services01
  • For you02
  • Solutions03
  • Work04
  • About05
  • Know-how06
  • Blog07
Start a project
EN/PL/RU
Vlad Sedenko
Independent web product developer
EU / Poland / Warsaw
Products
  • NextWooNext.js storefront for WooCommerce
© 2026. All rights reserved
Services
  • Product Discovery
  • UX/UI Design
  • MVP Development
  • SaaS Development
  • Website Redesign
  • Web Application Security
  • Conversion Optimization
  • API Integrations & Business Automation
  • Product Support
Explore
  • Services
  • For you
  • Work
  • Solutions
  • About
  • Blog
  • Know-how
  • Contact
Start a project
  • vlad@sedenko.net
  • LinkedIn
  • Privacy/Cookies
Know-how/Next.js SEO Checklist: The Complete Guide for App Router (2026)

Part 15 of 22

Internal linking and site architecture

Internal linking strategy for Next.js sites: topic clusters, descriptive anchors, crawl depth, orphan pages and generating related-content blocks from your data.

2026-07-15
Internal linking and site architecture

All topics in this guide

A practical, section-by-section SEO checklist for Next.js: rendering strategy, Metadata API, hreflang, structured data, Core Web Vitals, and optimization for AI answer engines.

Internal links are the cheapest SEO lever you fully control. They decide how authority flows through your site, which pages search engines consider important, and whether a crawler (or an AI engine) can even find your content. Most sites get them wrong not by breaking rules but by never deciding anything: links accumulate instead of being designed.

Architecture: hubs and clusters

Structure content as topic clusters: a hub page owning a broad topic, spoke pages covering each subtopic, linked both ways. This guide is itself an example — a hub linking 22 topics, every topic linking back and sideways.

Why it works:

  • Search engines infer topical authority from tightly interlinked clusters — twenty connected pages about Next.js SEO outrank twenty scattered posts.
  • Authority from external links to any one page flows through the cluster.
  • AI engines follow the same trails when deciding whether you're a source or a one-off mention.

The practical rule: every important page within 3 clicks of the homepage. Deeper pages get crawled less, ranked lower, and refreshed more rarely.

Anchors carry meaning

Anchor text tells the crawler what the target page is about — it's the closest thing to voting for your own keywords:

  • ❌ "Learn more here" — wasted signal.
  • ✅ "how ISR revalidation keeps pages fresh" — the target now has a relevance vote for its topic.

Vary anchors naturally; identical exact-match anchors from every page look mechanical. And never nofollow internal links — you'd be telling Google not to trust your own site.

Orphans and dead weight

An orphan page — reachable from nowhere — effectively doesn't exist: no crawl priority, no authority, often no indexing. Orphans accumulate silently: landing pages from old campaigns, posts whose category was removed, pages only reachable from a decommissioned menu.

Audit quarterly: crawl your site (Screaming Frog or a script over your own sitemap), diff the URL set against pages receiving internal links, and either link or retire the orphans. In Next.js, the fix is structural — generate link blocks from the same data that generates pages:

// related topics from the registry — pages can't become orphans,
// because every page is linked from its siblings by construction
const related = topics.filter((t) => t.cluster === current.cluster);

Where links live matters

  • In-body contextual links carry the most weight — a link inside a relevant paragraph beats ten footer links.
  • Breadcrumbs (UI + BreadcrumbList schema) give every deep page a crawlable path to its hub.
  • Related-content blocks at the end of articles keep both crawlers and readers moving; generate them from data, don't curate by hand — hand-curated blocks rot.
  • Site-wide footer links are fine for navigation but are heavily discounted as ranking signals; don't stuff keywords there.

Checklist:

  • Content organized in hub-and-spoke clusters with two-way links
  • Every indexable page reachable within 3 clicks of the homepage
  • Descriptive anchors everywhere; no "click here", no nofollow on internal links
  • Quarterly orphan audit; related blocks generated from data, not curated
  • Breadcrumbs with schema on all deep pages
← PreviousImage SEO: turning pictures into trafficNext →Search intent: pages that match what people actually type

01—22

All topics in this guide

  1. 01Rendering strategy: what does the crawler actually see?→
  2. 02Metadata API: titles, descriptions and the template pattern→
  3. 03Canonical URLs and hreflang: one page, one address→
  4. 04Open Graph and dynamic OG images→
  5. 05sitemap.ts and robots.ts: file conventions instead of hand-written XML→
  6. 06Structured data: JSON-LD that earns rich results→
  7. 07Images, fonts and scripts: the classic performance trio→
  8. 08Core Web Vitals: the three numbers Google measures→
  9. 09Redirects, 404s and status codes→
  10. 10Caching and content freshness→
  11. 11AEO/GEO: getting cited by ChatGPT, Perplexity and Google AI Overviews→
  12. 12Monitoring: SEO is a loop, not a launch task→
  13. 13Trust and E-E-A-T: making your site believable→
  14. 14Image SEO: turning pictures into traffic→
  15. 15Internal linking and site architecture•
  16. 16Search intent: pages that match what people actually type→
  17. 17Programmatic SEO in Next.js: pages at scale without the spam→
  18. 18SEO migration: replatforming to Next.js without losing traffic→
  19. 19Pagination and faceted navigation without index bloat→
  20. 20Accessibility and SEO: one job, two rewards→
  21. 21Content decay: refresh, consolidate or prune→
  22. 22Off-page for developers: earning links without buying them→

Want this handled for you?

I audit and fix technical SEO on Next.js sites — indexing, performance, hreflang and AI visibility.

Technical SEO service