Rebuilding Internal Linking at Site Scale With Claude Code

Rebuilding Internal Linking at Site Scale With Claude Code

AI & Agents
TripleDart
Workflow guide
Why per-post linking cannot repair an archive, and where the high-impact linking opportunities sit instead.
Organisation
TripleDart
Written By
TripleDart SEO team
PUBLISHED
August 5, 2026
Read
3
min

What it is.

This starts from 340 orphan pages on one archive, which is the kind of problem per-post linking cannot reach.

Across the B2B SaaS archives we rebuild, 40 to 50% of high-impact linking opportunities are orphan repairs, another 25 to 30% are topic cluster work, and the remaining 20 to 30% are anchor diversity corrections.

New-post link insertion accounts for under 5% of the lift we measure after a rebuild, which is the finding that redirects the effort.

What you get.

  • A four-part site audit: sitemap reconciliation, link graph, anchor distribution, cluster integrity
  • Where the opportunities sit, at 40 to 50% orphan repairs and 25 to 30% cluster repairs
  • Why template-level repairs beat per-page edits, with about 70% of breaks templatable
  • The anchor concentration threshold we flag, at 25% of inbound anchor text to one destination
  • Anchor fatigue on 10 to 15% of high-traffic destinations, and generic anchor waste on 25 to 35%
  • One archive rebuild walked through, and how the pipeline handles CMS limits

Read it at the source.

Opens on TripleDart. Free, and the figures on this page all come from it.
Read the guide

Frequently Asked Questions

Where is the lift concentrated?
Can I do this post by post?
Does internal linking still matter?
Can internal linking be automated?
Should you add links to new posts or repair the archive?
How much of one anchor is too much?
Strengths
  • Quantifies where the lift is, so effort goes to orphan and cluster work before anchor polish.
  • Gives a numeric threshold for anchor concentration, which makes the audit repeatable.
  • States that new-post linking is under 5% of the lift, against how most teams spend their time.
Limitations
  • Our own workflow, supporting a service we sell.
  • Percentages are drawn from our own client archives.
  • Template-level repairs need CMS access that some stacks will not give a marketing team.
Skip this if
  • Skip it if your archive already has an internal linking pass behind it.
Ideal for
  • SEO leads with a large archive
  • Content operations leads
  • GTM engineers

The plays behind the reading.

We build inbound GTM engines for B2B software teams, and these are the frameworks we build from. Bring us a pipeline target and we'll map the route.