seo-internal-linking
Skill81 starsChanged 2 months agoMITView on GitHub
Audit and improve a site's internal-linking topology and semantic HTML — map pillar/cluster structure, count and grade contextual in-body links and anchor text, surface orphan pages and nav-heavy templates, and propose specific source→target link insertions. Module M10. Feeds the Search SEO score.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- DoddleHQ/doddle-seo-geo-skillstheir own version, first seen Oct 20, 2026
- Thibaultbm/claude-seo-geotheir own version, first seen Oct 13, 2026
- datacas/seo-agent-toolkittheir own version, first seen Oct 11, 2026
- Teapot-Agency/teapot-seo-skillstheir own version, first seen Apr 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Thibaultbm/claude-seo-geo★ 18same name
- datacas/seo-agent-toolkit★ 1same name
- DoddleHQ/doddle-seo-geo-skills★ 0same name
- Teapot-Agency/teapot-seo-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- auditSkill
- compareSkill
- fixSkill
- geoSkill
- scoreSkill
- seo-agent-readinessSkill
- seo-ai-crawlersSkill
- seo-ai-discoverySkill
- seo-core-web-vitalsSkill
- seo-crawlabilitySkill
- seo-crawl-renderSkill
- seo-ecommerceSkill
- seo-eeatSkill
- seo-entity-linkingSkill
- seo-fix-applySkill
- seo-freshnessSkill
- seo-geo-answerblocksSkill
- seo-geo-factdensitySkill
- seo-headings-structureSkill
- seo-images-mediaSkill
- seo-indexabilitySkill
- seo-internationalSkill
- seo-localSkill
- seo-meta-onpageSkill
- seo-mobileSkill
- seo-orchestratorSkill
- seo-platform-detectSkill
- seo-renderingSkill
- seo-schema-jsonldSkill
- seo-scoreSkill
- seo-sitemapsSkill
- seo-social-cardsSkill
- seo-vertical-detectSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Semantic HTML: check for <main>, <article>, <nav>, <header>, <footer>, one <h1>, and a logical heading order — semantic structure helps …
- Distinctive: line 27
Never invent target URLs, anchor wording, or topology you cannot observe in the snapshot/crawl — ask the user or leave a clearly-marked …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Portions Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) - see LICENSE for original authors · tododeia.com · id er-d03758e1 -->seo-internal-linking (M10)
Internal links distribute crawl priority and topical authority and tell search engines (and AI crawlers) how your pages relate. Reference: references/schema-tier1.md for the entity/@id linkage this topology should mirror; M6/seo-entity-linking owns external sameAs.
Inputs
Work from the PageSnapshot named in your dispatch envelope: read parsed from <run_dir>/pages/<slug>.json (anchors[] with region/internal/anchor, landmarks) and the crawl graph in <run_dir>/crawl.json (graph.edges, pages[].inlinks, templates[]); Grep pages/<slug>.html for verbatim evidence; site artifacts live in <run_dir>/site/{robots.json,sitemaps.json,discovery.json}. Deterministic findings already emitted by audit.mjs are listed in <run_dir>/findings.deterministic.json — do not re-emit those ids; add model-judged findings only. If invoked directly with a URL/path and no snapshot exists, first run node "${CLAUDE_PLUGIN_ROOT}/scripts/snapshot.mjs" <target> --out "${CLAUDE_PLUGIN_DATA}/runs" and use the printed snapshot path.
Audits
Working from the PageSnapshot (parsed_rendered when render.used is not none, else parsed):
- Pillar/cluster topology: classify each URL (pillar hub vs. cluster page) and confirm clusters link up to their pillar and the pillar links down to its cluster — gaps break the hub-and-spoke model.
- Contextual in-body links: count links inside
<main>/<article>prose (target ~3-5 descriptive in-content links per page); flag pages with zero in-body internal links. - Anchor-text descriptiveness: flag generic anchors ("click here", "read more", "learn more", bare URLs) and over-optimized exact-match repetition; anchors should describe the destination.
- Orphan pages: list URLs in the sitemap/crawl with no incoming internal links from other crawled pages.
- Nav-vs-in-content ratio: flag templates where boilerplate nav/footer links overwhelm contextual links, diluting per-page link signal.
- Semantic HTML: check for
<main>,<article>,<nav>,<header>,<footer>, one<h1>, and a logical heading order — semantic structure helps both parsers and accessibility.
Fixes
- PROPOSED (
fixable: proposed): concrete internal-link insertions — a specific source page, the target URL, the suggested anchor text, and the sentence/selector to attach it to — emitted as a unified diff forfix. These require per-item accept because auto-injecting body links can alter meaning, tone, or reading flow. - ADVISORY (
fixable: advisory): wrapping content in semantic tags (<main>/<article>/<nav>) and heading-order corrections — described, never written by the tool, since they touch template structure. - Never invent target URLs, anchor wording, or topology you cannot observe in the snapshot/crawl — ask the user or leave a clearly-marked TODO placeholder. (Severity for this module's findings: 3.)
Verification
- Per page:
node "${CLAUDE_PLUGIN_ROOT}/scripts/link-graph.mjs" --snapshot <pages/<slug>.json>(or--url <u>/--file <path> --base <origin>) returns that page's link profile (verification.method: link_graph):total_links,internal_unique,external_unique,in_content_target,generic_anchors,empty_anchors,dropped. It does not compute topology from one page. - Site topology: read
<run_dir>/crawl.json(graph.edges,pages[].inlinks,templates[]) — the crawl already built it.--crawl [--max 25] [--max-depth 3] [--no-robots] [--ua <preset>]runs a fresh shallow same-site crawl and adds acrawlblock withpotential_orphans(a crawled page with no inbound internal link from another crawled page; the start page is never one, and the script itself calls the list non-authoritative). Pillar/cluster judgement is model work on top of those edges, not a script output. - The full topology/orphan check needs a site-wide crawl tier. When that crawl data is unavailable, status is
needs_api— never a falsepass.
Findings
Emit findings per schema/finding.schema.json. Examples:
M10.contextual.too_few_inbody_links— fewer than ~3 contextual in-body links (statuswarn, severity 3,fixable: proposed, axissearch, confidencedirectional).M10.anchor.generic_text— anchor reads "click here"/"read more" (statuswarn, severity 3,fixable: proposed, axissearch, confidencedirectional).M10.orphan.no_incoming_links— page has no internal inlinks from the crawl (statusfail, severity 3,fixable: advisory, axissearch, confidenceestablished).M10.semantic.missing_main— no<main>/<article>landmark around primary content (statuswarn, severity 3,fixable: advisory, axissearch, confidencedirectional). Each finding:evidence.observedquotes the page (the anchor text, the link count, the offending element);verification.reproduceis the runnablelink-graph.mjscommand above;expected_impactis banded + confidence-tagged (no naked percentages).
Honesty
- A fixed "3-5 links per page" is a usability/structure heuristic, not a ranking law — treat the count as directional and never cap a score on it alone.
- Exact-match anchor stuffing and "more links = more authority" are myths: relevance and editorial context matter more than raw count, and excess can look manipulative. Recommend links only where they genuinely help the reader.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

