Fetches internal-linking-optimizer from aaron-he-zhu/seo-geo-claude-skills and configures it for Cursor.
3
Select Cursor when prompted
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4
Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/internal-linking-optimizer
Restart Cursor to activate internal-linking-optimizer. Access via /internal-linking-optimizer in your agent's command palette.
⚠
Security Notice
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.
This skill analyzes your site's internal link structure and provides recommendations to improve SEO through strategic internal linking. It helps distribute authority, establish topical relevance, and improve crawlability.
System role: Optimization layer skill. It turns weak pages, structures, and technical issues into prioritized repair work.
When This Must Trigger
Use this when the conversation involves any of these situations — even if the user does not use SEO terminology:
Use this whenever the task needs a diagnosis or repair plan that should feed directly into remediation work, not just a one-time opinion.
Improving site architecture for SEO
Distributing authority to important pages
Fixing orphan pages with no internal links
Creating topic cluster internal link strategies
Optimizing anchor text for SEO
Recovering pages that have lost rankings
Planning internal links for new content
What This Skill Does
Link Structure Analysis: Maps current internal linking patterns
Authority Flow Mapping: Shows how PageRank flows through site
Orphan Page Detection: Finds pages with no internal links
Anchor Text Optimization: Improves anchor text diversity
Topic Cluster Linking: Creates pillar-cluster link strategies
Link Opportunity Finding: Identifies where to add links
Navigation Optimization: Improves site-wide link elements
Quick Start
Start with one of these prompts. Finish with a short handoff summary using the repository format in Skill Contract.
Analyze Current Structure
Analyze internal linking structure for [domain/sitemap]
Find internal linking opportunities for [URL]
Create Linking Strategy
Create internal linking plan for topic cluster about [topic]
Suggest internal links for this new article: [content/URL]
Fix Issues
Find orphan pages on [domain]
Optimize anchor text across the site
Skill Contract
Expected output: a scored diagnosis, prioritized repair plan, and a short handoff summary ready for memory/audits/.
Reads: the current page or site state, symptoms, prior audits, and current priorities from CLAUDE.md and the shared State Model when available.
Writes: a user-facing audit or optimization plan plus a reusable summary that can be stored under memory/audits/.
Promotes: blocking defects, repeated weaknesses, and fix priorities to memory/open-loops.md and memory/decisions.md.
Next handoff: use the Next Best Skill below when the repair path is clear.
Data Sources
Note: All integrations are optional. This skill works without any API keys — users provide data manually when no tools are connected.
With ~~web crawler + ~~analytics connected:
Claude can automatically perform a full site crawl via ~~web crawler to map the complete link graph, fetch page performance metrics from ~~analytics to identify high-value pages, and analyze link flow throughout the site. This enables data-driven internal linking strategies.
With manual data only:
Ask the user to provide:
Sitemap URL or list of important pages
Key page URLs that need more internal links
Content categories or topic clusters
Any existing link structure documentation
Proceed with the analysis using provided data. Note in the output which findings are from automated crawl vs. manual review.
Instructions
When a user requests internal linking optimization:
## Orphan Page Analysis### DefinitionOrphan pages have no internal links pointing to them, making them
hard for users and search engines to discover.
### Orphan Pages Found: [X]| Page | Traffic | Priority | Recommended Action ||------|---------|----------|-------------------|| [URL 1] | [X]/mo | High | Link from [pages] || [URL 2] | [X]/mo | Medium | Add to navigation || [URL 3] | 0 | Low | Consider deleting/redirecting |### Fix Strategy**High Priority Orphans** (have traffic/rankings):
1. [URL] - Add links from: [relevant pages]
2. [URL] - Add links from: [relevant pages]
**Medium Priority Orphans** (potentially valuable):
1. [URL] - Add to category/tag page
2. [URL] - Link from related content
**Low Priority Orphans** (consider removing):
1. [URL] - Redirect to [better page]
2. [URL] - Delete or noindex
Analyze Anchor Text Distribution
CORE-EEAT alignment: Internal linking quality maps to R08 (Internal Link Graph) in the CORE-EEAT benchmark -- use descriptive anchors, ensure links support topical authority. See content-quality-auditor for full audit.
## Anchor Text Analysis### Current Anchor Text Patterns**Most Used Anchors**:
| Anchor Text | Count | Target Pages | Assessment ||-------------|-------|--------------|------------|| "click here"
✓
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
›Access to product documentation and roadmap tools (Jira, Notion, etc.)
›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Steps
1Install product management skill
2Start with user story generation for known feature
3Progress to competitive analysis: research 2-3 competitors
4Use for roadmap prioritization: apply RICE/ICE scoring
5Draft stakeholder communications and refine based on feedback
6Build template library for recurring PM tasks
7Share effective prompts with product team
Common Pitfalls
⚠Not validating competitive research—verify facts before sharing
⚠Accepting user stories without involving engineering team
⚠Over-relying on frameworks without qualitative judgment
⚠Not customizing outputs to company culture and communication style
⚠Skipping stakeholder validation of generated requirements
Best Practices
✓ Do
+Validate research and competitive analysis with real data
+Collaborate with engineering when generating technical requirements
+Customize frameworks and templates to your company context
+Use skill for first drafts, refine with stakeholder input
+Document successful prompt patterns for PM tasks
+Combine AI efficiency with human judgment and intuition
✗ Don't
−Don't publish competitive analysis without fact-checking
−Don't finalize user stories without engineering review
−Don't make prioritization decisions solely on AI scoring
−Don't skip customer validation of generated requirements
−Don't ignore company-specific context and culture
💡 Pro Tips
★Provide context: company goals, constraints, customer feedback
★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
★Use skill for 70% generation + 30% customization to company needs
When to Use This
✓ 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.
Learning Path
1Basic: user stories, feature specs, status updates
