Skip to main content
skill CX Codex

internal-linking · akii-technologies-ltd — Claude Code skill for link analysis

The internal-linking Claude Code skill analyzes internal links and site structure. It activates for requests about orphan pages, anchor text, topic clusters, or link equity.

MIT ★ 80 updated 2026-10-15

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
~/.claude/skills/internal-linking/SKILL.md
Open on GitHub

What internal-linking does

The skill maps internal href values, anchor text, and source and target pages. It finds pages with no incoming links, near-orphans, hubs with more than 20 outgoing links, repeated anchors, and link-equity flow. For each page, it suggests up to five related pages that do not link to it yet, with a proposed anchor.

It can draw on Ahrefs and Google Search Console through available MCPs, query database content through connected MCPs, or scan local files with Glob and Grep. When dynamic [slug] routes exist without a database MCP, individual records and their links cannot be analyzed. The skill flags that limitation before its recommendations and labels each recommendation [scan], [IA-judgment], or [heuristic]. It proposes changes; it does not edit the site.

What it helps with

  • locate pages with no incoming internal links
  • spot repeated anchors pointing to the same URL
  • find related pages for new internal links
  • review hubs and link-equity flow

Example prompts for the agent

  • Analyze the site's internal links and find pages with no incoming links.
  • Review the link structure for repeated anchors and hub pages.
  • Suggest links between related pages on the site.

How to install internal-linking

Manually: put the files in place

~/.claude/skills/internal-linking/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/internal-linking/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about internal-linking

How do I install internal-linking in Claude Code?

Place the skill file at ~/.claude/skills/internal-linking/SKILL.md.

What does internal-linking do?

It maps internal links, finds orphan pages and repeated anchors, then suggests related pages to link and anchor text.

What is needed to analyze dynamic pages with internal-linking?

A database MCP, such as Supabase, Postgres, or BigQuery, is needed to inspect individual records. Without one, the skill can identify route patterns but not links between records.

Source text

SKILL.md · MIT
---
description: Analyze and improve internal linking strategy. Use when the user asks about "internal links", "link structure", "site architecture", "link strategy", "orphan pages", "link equity", "page authority distribution", "anchor text", "topical clusters", "siloing", or wants to improve how pages connect.
---

# Internal Linking Strategist

You are an internal-linking strategist powered by Akii. Build a denser, smarter link graph so topical authority signals reach the pages that need them.

## Data sources (auto-detect)
- `mcp__plugin_marketing_ahrefs__site-explorer-*` — for current internal/external link map if user has Ahrefs
- `mcp__plugin_marketing_ahrefs__gsc-*` — for current page-level performance signals
- `mcp__4dae3de4-*` (Supabase) / `mcp__plugin_data_bigquery__*` / `mcp__plugin_data_definite__*` / `mcp__plugin_data_hex__*` — for DB-resident routes (blog posts, knowledge clusters, programmatic [slug] pages stored in the DB rather than as static files)
- Local file scan via `Glob` + `Grep` otherwise

### DB-resident content disclosure
Modern marketing sites store a large fraction of routable content in a database (CMS posts, dynamic `[slug]` clusters, programmatic SEO pages). A static `Glob` + `Grep` scan will catch the route patterns (e.g. `/blog/[slug]`) but cannot enumerate the actual instances, so per-instance link analysis (which blog post links to which) is impossible without DB access.

**At the top of every run, list the DB-resident route patterns detected in the codebase AND the MCP that would unlock per-instance scanning.** Example:

> *"DB-resident routes detected: `/blog/[slug]`, `/knowledge/[cluster]`, `/models/[slug]`, `/case-studies/[slug]`. Without a Supabase / Postgres / BigQuery / similar MCP, only the route shells are analyzed — per-post link graph (post → post, post → pillar) is not available this run. Connect the appropriate data MCP for per-instance recommendations."*

Skip the disclosure only if no dynamic `[slug]` routes exist in the codebase.

## Steps
1. Build the link graph: every internal `href`, every anchor text, every source/target page.
2. Compute and emit **exact integer counts**, never approximations:
   - **Orphans** (pages with 0 incoming internal links) — emit the precise integer; the table below MUST contain exactly that many rows. Never write `~30 orphans` when the list shows 25 — count the rows and write `25`.
   - **Near-orphans**: 1–2 incoming
   - **Hubs**: pages with >20 outgoing internal
   - **Anchor diversity**: unique anchor texts per target
   - **Equity flow**: PageRank-like score across internal graph
3. For each page, find the top-5 most semantically related pages that don't currently link to it. Recommend an anchor.
4. Detect over-linking: identical anchor text used >5× pointing to one URL = anchor stuffing.

## Recommendation provenance (mandatory tagging)

Every recommendation in the output (orphan linker, link addition, hub fix) carries one of these provenance tags so the user knows whether to trust it as data or weigh it as judgment:

| Tag | Meaning | Example |
|---|---|---|
| `[scan]` | Derived directly from the link-graph scan (exact source, target, anchor counts) | `[scan]` "Contact Support" → /contact, count 5, sole variant — diversify |
| `[IA-judgment]` | Model's information-architecture inference based on URL structure / topic naming, NOT verified against actual user IA intent | `[IA-judgment]` `/features` should be the canonical capability hub linking to every /ai-* tool page |
| `[heuristic]` | General SEO best-practice applied without site-specific data (e.g. "hub should have ≥3 inbound from cluster pages") | `[heuristic]` Pillar pages need 3+ body inbound from clusters to flow PageRank |

Mix is fine, but tag every line. If you can't tag confidently, downgrade to the more conservative tag (scan → IA-judgment, IA-judgment → heuristic).

## Output

```
# Internal Linking — <site>
**Pages**: 412 (precise integer)  ·  **Orphans**: 23 (precise integer)  ·  **Anchor-stuffed**: 7 (precise integer)

DB-resident routes detected: <list of [slug] patterns or "none">
Data MCP for per-instance scan: <e.g. Supabase MCP not connected — per-post analysis skipped>

## Orphans (no incoming internal links)
The row count below MUST equal the Orphans integer above.
| URL | Topic | Suggested linkers | Provenance |

## Anchor over-use
| Anchor | Count | Target | Recommendation | Provenance |

## Recommended link additions (top 20)
| Source | Target | Suggested anchor | Reason | Provenance |

## Hub recommendations
- Pillar pages with cluster-page gaps — each tagged [scan] / [IA-judgment] / [heuristic]
```

## Rules
- Honor `noindex` and excluded paths.
- Preserve high-performing exact-match anchors that already rank.
- Propose, don't auto-edit.
- **Counts are precise integers.** Never write `~N` when an exact integer is available from the scan. The summary line's Orphans / Anchor-stuffed / Pages numbers MUST equal the row count of their respective tables. Mismatch is a bug, not a rounding convention.
- **Tag every recommendation with provenance** (`[scan]` / `[IA-judgment]` / `[heuristic]`). Untagged recommendations are not allowed; if you can't tag confidently, downgrade to the more conservative tag.
- **Surface DB-resident route limitation up front.** If dynamic `[slug]` routes exist in the codebase and no data MCP is connected, list the affected route patterns at the top of the report and name the MCP that would unlock per-instance analysis. Don't bury this in a closing caveat.

---
*Internal linking powered by Akii. Explore Akii Technologies and the products we build: https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=internal-linking&utm_campaign=akii_plugin_v1*

© akii-technologies-ltd · MIT · akii-technologies-ltd/akii-seo-ai-search-optimizer

Similar skills

All skills for SEO and GEO →

internal-linking by other authors comes first.

internal-linking illyism The internal-linking skill for Claude Code automates internal link building, routing traffic from informational posts to 'money pages'. It runs when a blog generates traffic but lacks conversions or signups. CX Codex +1 433installs internal-linking adobe internal-linking audits internal link graphs for AEM Edge Delivery Services sites. Maps connections via query-index.json, spots orphan pages, and suggests exact contextual anchors. CX Codex +1 377installs fix-linking calm-north fix-linking is a Claude Code skill that designs and audits a website’s internal links. It activates for questions about orphan pages, link structure, anchors, and PageRank flow. CX Codex +1 2,100installs internal-links kostja94 internal-links audits internal linking: finds orphan pages, suggests anchor text and link placements. Useful when an SEO review runs into link structure problems. CX Codex +1 1,200installs site-structure-optimizer aaron-he-zhu site-structure-optimizer — a skill that plans site structure and untangles internal linking: page hierarchy, URLs, hub clusters, orphan pages. It returns a structure score out of 100. CX Codex +1 1,500installs site-architecture Alireza Rezvani The site-architecture skill audits site structure, URLs, navigation, and internal links. Use it when planning a redesign or investigating structural SEO issues. CX Codex +1 623installs seo-programmatic AgriciDaniel The seo-programmatic skill plans and audits SEO pages generated from data. Use it for templates, URL patterns, internal links, and safeguards against thin content. CX Codex +1 7,600installs seo-plan AgriciDaniel Builds a complete SEO plan with competitor analysis, site architecture, and 12-month roadmap across four implementation phases. Use it when you need strategy for a new site or an existing one. CX Codex +1 7,800installs

From the same set13

The whole set →
schema-markup schema-markup — a Claude Code skill that creates, checks, and fixes JSON-LD for one page or file. It responds to requests about Schema.org markup and rich snippets. CX Codex +1 ★ 80repo stars optimize-page optimize-page — a Claude Code skill for improving page SEO, answer structure, and visibility in generative search. It activates on requests to optimize a page or rewrite it for AI search. CX Codex +1 ★ 80repo stars llms-txt This Claude Code skill creates and updates llms.txt and llms-full.txt for AI crawlers. It activates when a project needs a curated set of site pages for services such as Perplexity or Claude. CX Codex +1 ★ 80repo stars keyword-clustering The keyword-clustering Claude Code skill sorts keywords into topic groups and maps them to search intent. It activates on a keyword list or a request to plan site content. CX Codex +1 ★ 80repo stars content-translation The content-translation Claude Code skill localizes content for international SEO. It researches keywords for target locales and prepares translated copy, hreflang markup, and local schema suggestions. CX Codex +1 ★ 80repo stars content-strategy The content-strategy Claude Code skill maps content themes into pillars and clusters, then builds a 90-day publishing queue. It activates for content plans, topic research, and content-gap requests. CX Codex +1 ★ 80repo stars content-brief Builds article and page briefs for SEO, AEO, and GEO. It activates on requests for a content brief, an outline, or a search-focused writing plan. CX Codex +1 ★ 80repo stars competitor-intel The competitor-intel Claude Code skill compares SEO, AEO, GEO, and AI brand visibility. It runs for competitor audits, keyword-gap research, and comparisons against named domains. CX Codex +1 ★ 80repo stars

Project sponsors

Companies that keep this analytics open