seo-aeo-internal-linking
Maps internal link opportunities between pages with anchor text, placement instructions, orphan page detection, and cannibalization checks. Activate when the user wants to build an internal linking strategy or find link opportunities.
Best use case
seo-aeo-internal-linking is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Maps internal link opportunities between pages with anchor text, placement instructions, orphan page detection, and cannibalization checks. Activate when the user wants to build an internal linking strategy or find link opportunities.
Teams using seo-aeo-internal-linking should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/seo-aeo-internal-linking/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How seo-aeo-internal-linking Compares
| Feature / Agent | seo-aeo-internal-linking | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Maps internal link opportunities between pages with anchor text, placement instructions, orphan page detection, and cannibalization checks. Activate when the user wants to build an internal linking strategy or find link opportunities.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SEO-AEO Internal Linking ## Overview Analyses a set of pages and produces a prioritised list of internal link opportunities with exact anchor text, a context sentence showing where each link should appear, orphan page detection, anchor text cannibalization warnings, and a link equity map showing how authority flows across the content. Part of the [SEO-AEO Engine](https://github.com/mrprewsh/seo-aeo-engine). ## When to Use This Skill - Use when building internal links between a new pillar page and its cluster articles - Use when auditing an existing site for orphan pages - Use after content-cluster generates a topic map - Use when you need anchor text suggestions with placement context ## How It Works ### Step 1: Detect Orphan Pages Flag any page with zero incoming internal links. These are invisible to search engines and must be linked immediately. ### Step 2: Build Semantic Overlap Matrix Match pages by primary keyword similarity and content summary to identify natural linking opportunities. ### Step 3: Assign Link Types Every suggestion gets one of four labels: - **Cluster → Pillar** — highest priority, consolidates authority upward - **Pillar → Cluster** — distributes authority downward - **Cluster → Cluster** — builds semantic depth - **Contextual Boost** — concentrates equity on a focus page ### Step 4: Write Context Sentences For every link opportunity, write the sentence the anchor text should appear in — naturally placed, not forced. ### Step 5: Check Anchor Text Flag any exact-match anchor used more than once for the same target page as a cannibalization risk. Never use generic anchors like "click here". ## Examples ### Example: Link Opportunity Output 🔴 High Priority — Link 1 Type: Cluster → Pillar Source: "How to Build a Budget That Actually Works" Target: "The Complete Guide to Automated Budgeting" Anchor: "automated budgeting guide" Context: "For a full breakdown of every method available, see our [automated budgeting guide]." Impact: Consolidates topical authority on pillar page. Orphan Alert: "PennyWise Pricing Page" has no incoming links. Fix: Add link from comparison table in Article 2. ## Best Practices - ✅ **Do:** Every cluster article must have at least one Cluster → Pillar link - ✅ **Do:** Write a context sentence for every suggestion — anchor text needs natural placement - ✅ **Do:** Fix orphan pages before adding any new links - ❌ **Don't:** Use the same exact-match anchor for the same target page more than once - ❌ **Don't:** Use "click here", "read more", or "learn more" as anchor text — ever - ❌ **Don't:** Add more than 100 outgoing internal links on any single page ## Common Pitfalls - **Problem:** All cluster articles link to the pillar but not to each other **Solution:** Add Cluster → Cluster links between semantically related articles to build depth. - **Problem:** Same anchor text used across multiple pages for the same target **Solution:** Use partial match and branded anchors for subsequent links after the first exact-match use. ## Related Skills - `@seo-aeo-content-cluster` — generates the cluster map this skill links together - `@seo-aeo-schema-generator` — uses link map output for BreadcrumbList schema ## Additional Resources - [SEO-AEO Engine Repository](https://github.com/mrprewsh/seo-aeo-engine) - [Full Internal Linking SKILL.md](https://github.com/mrprewsh/seo-aeo-engine/blob/main/.agent/skills/internal-linking/SKILL.md) ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related Skills
internal-comms-community
To write internal communications, use this skill for:
internal-comms-anthropic
To write internal communications, use this skill for:
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
ckm:ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.