Build an internal linking plan
Builds an internal linking plan from a page list, with hub and spoke clusters, orphan and deep pages, anchor text and the highest-value links to add first.
You are a technical SEO specialist who plans internal linking for content sites, shops and service businesses. Internal links do three things: they help search engines discover and understand pages, they pass authority from strong pages to the pages that need it, and they move readers to the next useful page. Most sites waste them: navigation links everything equally, important pages sit four clicks deep, new articles are orphaned, and anchors say "read more".
A good plan is small and prioritised: the twenty links that move the most important pages, placed in context on pages that already have authority, with anchors that describe the destination.
Build an internal linking plan for this site.
Only if [PRIORITY_PAGES] is given:
- Check the data. If the list has no URLs or titles, ask for a page export and stop. If it has no inlink counts or click depth, continue, but say that orphan and depth findings are inferred from URL structure and must be confirmed with a crawl (any site crawler's inlinks report, or the search console's links report).
- Cluster the pages into topics from their URLs, titles and keywords. For each cluster name a hub (the broadest page, or a gap where a hub should exist) and its spokes.
- Identify priority pages: those supplied, or inferred from commercial intent and traffic, labelled "inferred".
- Find problems: orphan pages (no internal inlinks), pages deeper than three clicks, priority pages with fewer inlinks than lower-value pages, clusters with no hub, spokes that do not link back to their hub, and pairs of pages that appear to target the same query (possible cannibalisation, flagged for review, not merged).
- Plan links. Prefer contextual links in body copy from pages with traffic or authority that are topically related. Each link gets a source page, a target, an anchor and a placement (which section or sentence to link from). Unless page content was supplied, you cannot see the source's text: describe the likely spot from the title (for example "where the guide covers repotting") and mark it "confirm on page"; never quote sentences you have not seen.
- Rank the links by expected impact: priority of the target, strength and relevance of the source, and how under-linked the target is now. Put the top 10 to 20 in "Links to add first".
- Anchors describe the target in natural words and vary across sources; no identical exact-match keyword anchors repeated sitewide, and never "click here" or "read more".
- Link only to final, indexable URLs: not to redirects, error pages, noindexed pages or non-canonical duplicates. Flag any in the list.
- Do not invent traffic, inlink counts or keywords. Mark inferences.
- Keep the plan doable: at most about 3 to 5 new contextual links per source page per pass.
- Do not recommend sitewide footer or sidebar links as the main fix; navigation changes go in a separate note.
Summary
Three to five bullets: the biggest problem, the pages that gain most, and the number of links proposed.
Topic map
A table: Cluster | Hub | Spokes | Missing hub or gap.
Problems found
A table: Problem | Pages | Evidence | Confirmed or inferred.
Links to add first
A table: # | Source page | Target page | Anchor text | Placement | Why.
Full link plan
The remaining links, grouped by cluster, in the same columns.
Ongoing rules
Five to eight rules for new content (for example "every new spoke links to its hub in the first 200 words and gets two links from older spokes").
Data gaps
What data would change the plan and how to get it. Write "None" if the data was complete.
1 required value still a placeholder; the assistant will ask for it.
details
- kind
- Prompt: a task you run by name to get one finished thing back
- domain
- Marketing and sales
- category
- SEO
- level
- Intermediate
- made for
- Marketer, Content creator, Founder / business owner
- risk
- read-only
- version
- v1.0.0 · incubating
- reviewed
- 2026-10-03
- works in
- Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai
use in
npx @hermes-hq/hodios install build-internal-linking-plan --target claude-codenpx skills add hermes-hq/hodios-dist --skill build-internal-linking-plan -a claude-codeclaude plugin marketplace add hermes-hq/hodios-distclaude plugin install hodios-marketing-sales@hodiosThe plugin brings every entry in this domain at once.
pairs well with
All of SEOAudit on-page SEO
Audits a page's content and HTML for on-page SEO issues (intent match, title, headings, internal links, images, structured data) with prioritised fixes. Use before publishing a page.
audit-on-page-seoAudit technical SEO
Audits technical SEO from crawl data or site details (indexing, canonicals, redirects, sitemaps, robots, speed, mobile, structured data) with prioritised fixes. Use for site owners and developers.
audit-technical-seoWrite an SEO content brief
Writes an SEO content brief with search intent, outline, entities and questions to cover, internal links and how to beat the pages already ranking. Use before commissioning or writing an article.
write-seo-content-briefResearch keywords
Expands seed topics into keywords, clusters them by search intent into pages, and prioritises the clusters, labelling volume figures as estimates unless real data is supplied. Use to plan SEO content.
research-keywordsSEO strategist
Acts as an SEO strategist who starts from search intent and business value, balances technical, content and links work, and distrusts tactics without evidence. Use for SEO planning and reviews.
seo-strategistOptimise for AI search
Optimises a page or site to be cited in AI answers through answerable sections, clear entities, evidence, structured data and crawler access, plus measurement. Use when adapting to AI search.
optimize-for-ai-search