MCPInstall

fix-linking

Design or audit internal link structure for a website. Use when the user asks about internal linking, link architecture, orphan pages, PageRank flow, anchor text, site structure, silo architecture, or why pages aren't ranking despite good content. For external link building, see build-links.

Installs
2K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/calm-north/seojuice-skills --skill fix-linking
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads fix-linking automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Fix Linking

Design and audit internal link structures using hub-and-spoke topology, PageRank flow logic, and anchor text budgets.

Why Internal Links Matter

Internal links do two things: (1) pass PageRank between pages, and (2) signal topical relevance via anchor text. A page with zero incoming internal links is an orphan — invisible to authority flow regardless of content quality.

Architecture Model Selection

Before auditing links, choose the right architecture model for the site:

ModelBest ForSite SizeKey Characteristic
Hub-and-Spoke (Topic Cluster)Content marketing, SaaS, publishers50-500 pagesBidirectional links between pillar and cluster articles
Silo StructureE-commerce, directories, large enterprises100+ categoriesVertical-only links within topic silos
Flat ArchitectureSmall sites, portfolios, startups<100 pagesAll pages within 2-3 clicks, cross-linked freely
PyramidNews sites, large blogs, corporate500+ pagesTop-down hierarchy, authority concentrates at top
Mesh/MatrixKnowledge bases, wikis, help centersAnyFree-form linking between any related pages

Key Metrics by Architecture

MetricHub-and-SpokeSiloFlatPyramidMesh
Target click depth≤3≤4≤2≤4≤3
Internal links per page5-103-78-153-58-15
Cross-section linksManyFewN/ASomeMany
Authority distributionDistributed to hubsTop of siloEvenTop-heavyEven

Expected ROI from Architecture Changes

ChangeTypical ImpactTimeline
Fix orphan pages+15-30% traffic to those pages2-4 weeks
Build first topic cluster+10-25% traffic to cluster pages4-8 weeks
Reduce click depth by 1 level+5-15% crawl efficiency2-6 weeks
Anchor text optimization+5-10% ranking improvement4-12 weeks
Full architecture migration+20-50% overall organic traffic3-6 months

Recommended for most sites: Hub-and-Spoke as the primary model, with silo-style isolation between unrelated topic areas.

Phase 1: Map the Current Structure

Before designing links, understand what exists:

  1. Hub pages. Pages that aggregate links and distribute authority — homepage, category pages, pillar articles. List them.
  2. Orphan pages. No incoming internal links from crawlable pages. They receive zero PageRank from the internal graph.
  3. Link depth. How many clicks from the homepage does each important page require? Depth 4+ pages are effectively buried.
  4. Anchor text. Repeated identical anchors are fine. Generic anchors ("click here", "read more") waste relevance signal.

Ask the user for their page list or sitemap, or work with what they describe.

Phase 2: Hub-and-Spoke Design

Hub Pages (pillar/category)

  • Linked from homepage or main navigation
  • Link out to all supporting pages in their cluster
  • Serve as authority redistribution nodes

Spoke Pages (supporting/cluster articles)

  • Receive at least 2-3 internal links from hub and sibling spokes
  • Always link back to their hub page
  • Link to 2-4 sibling spokes where contextually relevant
  • Never link to competing pages (same keyword intent)

Cross-Cluster Links

  • Only when there is genuine topical relevance
  • Use to signal E-E-A-T connections (e.g., case study → methodology page)
  • Limit to 1-2 per page to avoid diluting cluster coherence

Phase 3: Anchor Text Budget

For internal links, each page should receive anchor text in this distribution:

Anchor TypeTarget ShareExample
Exact match20-30%"content decay detection"
Partial match30-40%"detecting when content decays"
Related/semantic20-30%"pages losing traffic"
Branded5-10%"our decay detection feature"
Generic0-5%"learn more"

Diversity improves relevance coverage for semantic search.

Phase 4: Orphan Page Resolution

For each orphan page, apply this decision tree:

  1. Worth ranking? If no (thin, superseded), redirect to the closest relevant page. Stop.
  2. Which cluster? Find the nearest hub page.
  3. Which 2-3 existing pages would readers logically arrive from? These are injection points.
  4. What anchor text fits naturally? Match the orphan page's target keyword.
  5. Does the hub page need a content update to include a contextual reference?

Phase 5: Link Injection Plan

Produce a concrete action plan:

Source PageTarget PageSuggested Anchor TextWhere on Source PagePriority
/blog/seo-guide/tools/keyword-research"keyword research tool"Under "Research Phase" headinghigh
...............

Priority = high if the target is a revenue-critical or high-intent page.

Output Format

Internal Link Audit: [domain]

Current State

  • Orphan pages: [count or list]
  • Average link depth for important pages: [value]
  • Hub pages identified: [list]
  • Anchor text diversity: [assessment]

Hub-and-Spoke Map For each cluster: Hub → [Spoke 1, Spoke 2, Spoke 3 ...]

Link Injection Plan [Table from Phase 5]

Anchor Text Fixes Pages where anchor text is entirely generic and needs replacement.

Recommendations

  1. Orphan pages that are revenue-critical — link them first
  2. Pages at depth 4+ that should be at depth 2 — add shortcuts via hub pages
  3. Clusters with weak internal connectivity — add sibling cross-links
  4. Pages with 0-1 incoming links that are important for conversions

Pro Tip: Try the free Internal Link Finder and Anchor Text Diversity tools at seojuice.com. SEOJuice MCP users can run /seojuice:site-health for instant orphan page detection, link depth distribution, and most-linked pages — the get_site_topology tool maps your entire internal link graph automatically.

FAQ

What does the fix-linking skill do?

Design or audit internal link structure for a website. Use when the user asks about internal linking, link architecture, orphan pages, PageRank flow, anchor text, site structure, silo architecture, or why pages aren't ranking despite good content. For external link building, see build-links.

How do I install fix-linking?

Run npx skills add https://github.com/calm-north/seojuice-skills --skill fix-linking in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/fix-linking/ (personal) or .claude/skills/fix-linking/ (project).

Which AI agents can use fix-linking?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is fix-linking safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains fix-linking?

It is published by calm-north in calm-north/seojuice-skills. It has 2,038 recorded installs.

More from calm-north/seojuice-skills

View all →

find-keywords

calm-north/seojuice-skills

Build a prioritized keyword list for a website, topic, or campaign. Use when the user asks about keyword research, finding keywords to target, building a keyword list, search demand, keyword difficulty, intent mapping, or which keywords to prioritize. For writing content around keywords, see brief. For grouping keywords into clusters, see build-clusters.

Docs & Writing7K installs

optimize-for-ai

calm-north/seojuice-skills

Optimize content for AI search engines — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews. Use when the user asks about AI SEO, AISO, getting cited by AI, appearing in AI answers, answer engine optimization, AEO, GEO, LLMO, AI Overviews, zero-click search, or how to appear in ChatGPT/Perplexity results. For traditional SEO, see diagnose-seo.

Marketing & SEO6.6K installs

build-links

calm-north/seojuice-skills

Design a link building campaign with prospect identification, asset creation, and outreach strategy. Use when the user asks about link building, backlinks, domain authority, how to get backlinks, outreach campaigns, digital PR, guest posting, or link acquisition. For internal linking, see fix-linking.

brief

calm-north/seojuice-skills

Produce an editor-ready content brief for a target keyword or topic. Use when the user asks for a content brief, writing guidelines, article outline, SEO brief, what to include in a blog post, or how to structure content for a keyword. For choosing which topics to write about, see find-keywords. For a full site-wide SEO audit, see audit.

Docs & Writing6.4K installs

audit

calm-north/seojuice-skills

Run a comprehensive SEO audit on a website covering technical health, on-page optimization, content quality, and backlink profile. Use when the user asks for an SEO audit, site review, SEO health check, "what's wrong with my SEO", website analysis, or a full diagnostic of their site's search performance. For speed-specific issues, see audit-speed. For technical crawl/index issues only, see diagnose-seo.

Security6.4K installs

rank-local

calm-north/seojuice-skills

Build a local SEO strategy covering Google Business Profile, local citations, reviews, and NAP consistency. Use when the user asks about local SEO, Google Business Profile, Google Maps ranking, local pack, NAP consistency, local citations, review strategy, or ranking for "[service] near me" searches.

Marketing & SEO2.5K installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.