The Complete Internal Linking Guide

Everything about internal and outbound links in one place, ordered the way you actually execute: understand the evidence, design the architecture, write the anchors, implement the code, then audit and test until it is provably working. Merges the research report (what the data proves) with the 2026 implementation blueprint (local service matrices, code, and benchmark tests).

The execution order this guide follows

Sections 1–4 are build work you do once per site (and revisit when you add a city, service, or topic). Sections 5–7 are the repeatable loop that keeps the linking system honest. If you only read one thing before a launch, read Testing & Verification — it tells you how to prove the setup is actually right.

The Evidence Base

Every rule in this guide is grounded in three tiers of evidence: Google's official documentation and statements, large-scale data studies and controlled split tests, and practitioner consensus (50 Reddit r/SEO threads, 441 comments sampled). Where sources disagree, both readings are shown. Correlational findings are labeled as such — the Zyppy study says explicitly that correlation is not proof. Controlled split tests (SearchPilot) are the strongest causal evidence available.

Core Linking Rules

The non-negotiables. Each is backed by Google documentation, data, or both. Do these in order when wiring up a site.

How many links is the right number?

Site Architecture

Good architecture makes linking automatic instead of a chore. Build the skeleton first, then let real data refine it.

Local service business architecture (the multi-location pattern)

For local service sites: every city service page links up to its regional hub and its parent service category, laterally to two sibling cities or services, and to its Google Business Profile landing page. National informational guides carry a contextual "Local Bridge" link down to the matching local money page.

Special cases

Anchor Text System

Anchor text is the strongest fully controllable signal in internal linking — the Zyppy data found anchor variety is the single strongest correlation with traffic. Two goals: describe the destination honestly, and vary the phrasing.

The ratio system

Which link "counts" when a page links to the same target twice

The first-link priority theory says Google credits the anchor text of the first link on a page to a given URL — usually the nav link ("Services"), potentially overriding your descriptive body anchor. This is practitioner analysis, not confirmed by Google. Two things are true regardless:

Link type weight table

Implementation & Code

Rules 6 and 7 live or die here. Plain language first, then the code for each stack.

The crawlability rules

Code patterns

1 · The crawlable anchor standard (HTML5)

<!-- ALWAYS: crawlable by Googlebot and AI crawlers -->
<a href="/locations/dallas/hvac-repair">Dallas HVAC Repair Services</a>

<!-- NEVER: JavaScript navigation is invisible to crawlers -->
<div onclick="window.location='/locations/dallas/hvac-repair'">Dallas HVAC</div>

2 · Next.js 14+ Server Component (sibling link block, server-rendered)

import Link from 'next/link';

interface LocationService { cityName: string; slug: string; }

export default async function LocalServiceMatrix(
  { currentCity, serviceSlug }: { currentCity: string; serviceSlug: string }
) {
  // Fetch sibling locations server-side during rendering — no client hooks
  const siblingCities: LocationService[] = await fetch(
    `https://api.yourdomain.com/locations?service=${serviceSlug}&exclude=${currentCity}`,
    { cache: 'force-cache' }
  ).then(res => res.json());

  return (
    <section>
      <h3>Other Nearby Service Areas</h3>
      <ul>
        {siblingCities.map(city => (
          <li key={city.slug}>
            <Link href={`/locations/${city.slug}/${serviceSlug}`}>
              {city.cityName} HVAC Repair
            </Link>
          </li>
        ))}
      </ul>
    </section>
  );
}

3 · Java Spring Boot / Thymeleaf (server-rendered link)

<a th:href="@{/locations/{city}/{service}(city=${location.citySlug}, service=${service.slug})}"
   th:text="${location.cityName + ' ' + service.name}">Dallas HVAC Repair</a>

Local link block anatomy (what to output per city service page)

Inside a contextual in-content section (for example "Serving Dallas–Fort Worth & Surrounding Communities") — never a footer dump:

<section class="service-area">
  <h3>Serving Dallas–Fort Worth & Surrounding Communities</h3>
  <p>Our <a href="/locations/dallas/">Dallas service center</a> handles every job in the
     metro, and our <a href="/services/hvac/">full HVAC services</a> team also covers
     <a href="/locations/fort-worth/hvac-repair/">Fort Worth HVAC repair</a> and
     <a href="/locations/arlington/hvac-repair/">Arlington AC repair</a>.
     See our <a href="https://maps.google.com/?cid=123">Google Business Profile</a>
     for reviews and hours.</p>
</section>

Every line does four jobs at once: parent hub link up, service category link up, two sibling links across, and the Google Business Profile alignment — all as descriptive anchors inside a real sentence.

Outbound Links & Rel Attributes

"Linking to other sites isn't something to be scared of; in fact, using external links can help establish trustworthiness (for example, citing your sources). Link out to external sites when it makes sense, and provide context to your readers about what they can expect." — Google Search Central

Rel attributes — quick reference

Multiple values are allowed (rel="ugc nofollow"). target="_blank" has zero SEO effect — pure user experience (pair with rel="noopener" for security).

Audit Workflow

The repeatable process, synthesized from Screaming Frog's official tutorial, Ahrefs' guide, and practitioner workflows. Run monthly on active sites, quarterly at minimum.

Orphan and crawl audit — what the output should look like

Orphan threshold: 0–2 incoming internal links. Deep page threshold: more than 3 clicks from the homepage. Every flagged row gets an explicit action.

Tools worth paying for

Testing & Verification

Two kinds of tests: setup tests that prove the linking system is built correctly, and impact tests that prove the links actually move rankings and traffic. Run the setup tests before any launch; run impact tests continuously.

Pre-launch setup checklist

Five benchmark tests (verify your tooling and process, not just the page)

Run these against your site, your audit script, or your AI assistant. Each exercises one behavior. If a run fails its pass criteria, the setup is not right yet.

Impact tests — proving the links actually work

Ongoing Maintenance

Linking is not a one-time build. This is the continuous loop.

Do-Not-Do Checklist

The complete never-list, merged from both source documents. If any item describes your site, fix it before adding anything new.

Myths & Debates

Sources & Learning

Video library

Merged from the Internal Linking & Outbound Links research report and the Interlinking SEO 2026 implementation blueprint. Correlational findings are labeled as such. Built for execution: rules → architecture → anchors → code → audit → test → maintain.