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.
What this skill does
# 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:
| Model | Best For | Site Size | Key Characteristic |
|-------|---------|---------|-------------------|
| Hub-and-Spoke (Topic Cluster) | Content marketing, SaaS, publishers | 50-500 pages | Bidirectional links between pillar and cluster articles |
| Silo Structure | E-commerce, directories, large enterprises | 100+ categories | Vertical-only links within topic silos |
| Flat Architecture | Small sites, portfolios, startups | <100 pages | All pages within 2-3 clicks, cross-linked freely |
| Pyramid | News sites, large blogs, corporate | 500+ pages | Top-down hierarchy, authority concentrates at top |
| Mesh/Matrix | Knowledge bases, wikis, help centers | Any | Free-form linking between any related pages |
### Key Metrics by Architecture
| Metric | Hub-and-Spoke | Silo | Flat | Pyramid | Mesh |
|--------|--------------|------|------|---------|------|
| Target click depth | ≤3 | ≤4 | ≤2 | ≤4 | ≤3 |
| Internal links per page | 5-10 | 3-7 | 8-15 | 3-5 | 8-15 |
| Cross-section links | Many | Few | N/A | Some | Many |
| Authority distribution | Distributed to hubs | Top of silo | Even | Top-heavy | Even |
### Expected ROI from Architecture Changes
| Change | Typical Impact | Timeline |
|--------|--------------|---------|
| Fix orphan pages | +15-30% traffic to those pages | 2-4 weeks |
| Build first topic cluster | +10-25% traffic to cluster pages | 4-8 weeks |
| Reduce click depth by 1 level | +5-15% crawl efficiency | 2-6 weeks |
| Anchor text optimization | +5-10% ranking improvement | 4-12 weeks |
| Full architecture migration | +20-50% overall organic traffic | 3-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 Type | Target Share | Example |
|---|---|---|
| Exact match | 20-30% | "content decay detection" |
| Partial match | 30-40% | "detecting when content decays" |
| Related/semantic | 20-30% | "pages losing traffic" |
| Branded | 5-10% | "our decay detection feature" |
| Generic | 0-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 Page | Target Page | Suggested Anchor Text | Where on Source Page | Priority |
|---|---|---|---|---|
| /blog/seo-guide | /tools/keyword-research | "keyword research tool" | Under "Research Phase" heading | high |
| ... | ... | ... | ... | ... |
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](https://seojuice.com/tools/internal-link-finder/)
> and [Anchor Text Diversity](https://seojuice.com/tools/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.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.