Anchor Distribution & Graph Linker

Overview

Design, audit, and optimize internal linking hierarchies, anchor text distribution, and topic cluster equity.

Verification & Test Notes

[!NOTE] Tested & Reviewed on 2026-10-10 for runtime environment TypeScript 5, Astro View Transitions.

Audited across 44,000+ internal links. Eliminates orphan pages and ensures bidirectional pillar-cluster authority flow.

Installation & Setup

Option 1: Direct Skill Download

1. Download Anchor Distribution & Graph Linker (internal-linking.zip).
2. Unpack the zip file into your workspace agent directory:
   • Antigravity IDE: .agents/skills/internal-linking/
   • Claude Code: ~/.claude/skills/internal-linking/ or .agents/skills/internal-linking/
   • Cursor: .cursor/rules/internal-linking/ or your project prompt definitions.

Option 2: CLI Activation

If using Antigravity or compatible agent runners:

# Load into active workspace
mkdir -p .agents/skills/internal-linking
curl -sL https://nadhebe.com/skills/internal-linking.zip -o /tmp/internal-linking.zip
unzip /tmp/internal-linking.zip -d .agents/skills/internal-linking/

Skill Instructions & Reference

Strategic Internal Linking & Link Equity Architecture

Activate this skill when planning, auditing, or optimizing internal link structures across Nadhebe’s technical content.

1. When to Activate This Skill

• When linking a newly written article to existing pillar and cluster guides.
• When selecting natural, descriptive anchor text that prevents keyword stuffing.
• When preventing orphan pages and optimizing search crawler pageRank distribution.
• When troubleshooting or configuring scripts/run-internal-linker.ts and scripts/verify-links.ts.

2. Link Hierarchy Rules in Nadhebe

Nadhebe follows a strict 4-way internal linking topology:

 ┌────────────────────────────────────────────────────────────────────────┐
 │                      INTERNAL LINKING TOPOLOGY                         │
 └───────────────────────────────────┬────────────────────────────────────┘
                                     │
           ┌─────────────────────────┼─────────────────────────┐
           ▼                         ▼                         ▼
┌──────────────────────┐  ┌──────────────────────┐  ┌──────────────────────┐
│  PILLAR → CLUSTER    │  │  CLUSTER → PILLAR    │  │  CLUSTER ↔ CLUSTER   │
├──────────────────────┤  ├──────────────────────┤  ├──────────────────────┤
│ • Authority push     │  │ • Equity consolidation│ • Semantic depth      │
│ • "Related Guides"   │  │ • Link in first 300w │  │ • Contextual mention │
│ • Broad to specific  │  │ • Mandatory link back│  │ • Complementary tech │
└──────────────────────┘  └──────────────────────┘  └──────────────────────┘

1. Pillar → Cluster (Downward Equity)

Pillar articles must link out to their child cluster posts within the body text or dedicated “Related Pricing Guides” / “Related Architectures” sections.

2. Cluster → Pillar (Upward Consolidation — Mandatory)

Every supporting cluster post MUST link back to its parent pillar guide within the opening 300 words. For example, in deepseek-api-pricing-guide.md:

“For high-volume developers, comparing token rates against our OpenAI API & ChatGPT Pricing Guide highlights key cost differences…“

3. Cluster ↔ Cluster (Cross-Cluster Semantic Links)

Articles sharing technical dependencies should link horizontally:

• A guide deploying vLLM links to RunPod GPU Pricing Explained
• A guide configuring Claude Code links to Cursor Pricing Guide

3. Anchor Text Best Practices

4. Automated Build Integration

Nadhebe utilizes an automated build-time pipeline:

• scripts/run-internal-linker.ts: Automatically injects contextual links for existing articles across compiled HTML files based on title keyword matching.
• scripts/verify-links.ts: Automatically tests every internal link during npm run build to ensure 0 broken links.

Always format markdown links with absolute project paths: [Link Text](/guides/slug-name) or [Link Text](/tutorials/slug-name) Never use relative paths like ../guides/slug.md in markdown content.