Design and audit internal link structures using hub-and-spoke topology, PageRank flow, and anchor text optimization.
Works with
Supports five architecture models (hub-and-spoke, silo, flat, pyramid, mesh) with guidance on which fits different site sizes and content types
Includes orphan page detection, link depth analysis, and anchor text diversity assessment to identify ranking barriers
Provides concrete link injection plans with source pages, target pages, anchor text suggestions, and priorit
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfix-linkingExecute the skills CLI command in your project's root directory to begin installation:
Fetches fix-linking from calm-north/seojuice-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate fix-linking. Access via /fix-linking in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
5
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
5
stars
Design and audit internal link structures using hub-and-spoke topology, PageRank flow logic, and anchor text budgets.
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.
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 |
| 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 |
| 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.
Before designing links, understand what exists:
Ask the user for their page list or sitemap, or work with what they describe.
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.
For each orphan page, apply this decision tree:
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.
Current State
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.
Pro Tip: Try the free Internal Link Finder and Anchor Text Diversity tools at seojuice.com. SEOJuice MCP users can run
/seojuice:site-healthfor instant orphan page detection, link depth distribution, and most-linked pages — theget_site_topologytool maps your entire internal link graph automatically.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
fix-linking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend fix-linking for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added fix-linking from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
fix-linking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
fix-linking fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
fix-linking is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in fix-linking — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
fix-linking has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: fix-linking is focused, and the summary matches what you get after install.
Registry listing for fix-linking matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 35