internal-linking
Skill0 starsChanged 21 days agoMITView on GitHub
Use when planning, adding, auditing, or measuring contextual internal links, orphan recovery, hubs, or anchor rewrites.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- classroomio/classroomiotheir own version, first seen Nov 16, 2026
- 6t9xstar/one-step-seotheir own version, first seen Nov 8, 2026
- akii-technologies-ltd/akii-seo-ai-search-optimizertheir own version, first seen Nov 1, 2026
- afeezadebayo/technical-seo-skillstheir own version, first seen Oct 20, 2026
- risukisu/marketing-skillstheir own version, first seen Oct 13, 2026
- searchfit/searchfit-seotheir own version, first seen Sep 10, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- classroomio/classroomio★ 1.7ksame name
- akii-technologies-ltd/akii-seo-ai-search-optimizer★ 80same name
- searchfit/searchfit-seo★ 9same name
- risukisu/marketing-skills★ 6same name
- 6t9xstar/one-step-seo★ 5same name
- afeezadebayo/technical-seo-skills★ 2same name
- DarynaRodriguez/seo-skills★ 1same name
- younesbenallal/seo-skills★ 1same 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 repository4 other files it gives its agents.
- seo-auditSkill
- seo-opsSkill
- seo-quick-winsSkill
- verified-seo-article-writingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 15 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
15
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
- Distinctive: line 25
Search or analytics data when ranking donors or measuring results.
- Distinctive: line 34
Never change a published source to Draft to stage a link.
- Distinctive: line 36
Keep one planned body edge per source and target.
- Very specific: line 37
Use ordinary crawlable links.
- Distinctive: line 38
Verify the target returns a direct HTTP 200, is indexable, and has the intended canonical.
- Distinctive: line 41
Start with a bounded manual batch.
- Distinctive: line 42
Use evidence gathered after relevant canonical, redirect, or indexability fixes.
- Distinctive: line 43
Read back the saved content and publication status.
- Distinctive: line 72
Use concise descriptive anchors that fit the sentence.
- Distinctive: line 80
Read back the saved body and confirm the exact href, visible anchor, and page status.
- Distinctive: line 90
Add relevant links to established coverage, including a useful hub when one exists.
- Distinctive: line 91
Verify each target and keep the copy readable.
- Distinctive: line 93
Keep older-page edits within the same published-source safety rules.
- Distinctive: line 95
Use verified-seo-article-writing when the article also needs source and claim verification.
- Distinctive: line 103
If a repeated insertion rule performs poorly or introduces irrelevant links, stop expansion and review the pattern before changing more …
- Distinctive: line 114
Use distinct states: proposed, staged, published, verified, or blocked.
“Common” is measured: kept by at least 6 in 10 of the 8 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
Internal Linking
Build useful paths between pages, then prove that the intended links were saved. For a broad technical audit, start with seo-audit. For a recurring, lightweight opportunity harvest, use seo-quick-wins. Site hierarchy changes need a separate architecture plan.
Choose a mode
| Request | Mode |
| Find orphans, broken targets, or weak link coverage | Diagnose |
| Choose targets, donors, and placements | Plan |
| Add approved links or rewrite anchors | Implement |
| Check results after a linking change | Measure |
| Link a new article into the existing site | Editorial loop |
Required inputs
- Site and permitted URL scope.
- Fresh crawl or page export with published status, body links, canonicals, and indexability where available.
- Search or analytics data when ranking donors or measuring results.
- Target page priorities and any editorial restrictions.
- Permission scope: recommendations, draft edits, revisions, or approved live changes.
Missing data limits the result. Do not label a URL an orphan from a sitemap alone, or claim technical verification from a search snippet.
Guardrails
- New content stays Draft or Pending Review unless publication is authorized.
- Never change a published source to Draft to stage a link. Use a revision, staging copy, or authorized live edit.
- Count contextual body links separately from navigation, breadcrumbs, related-content modules, and footer links.
- Keep one planned body edge per source and target. Skip insertion if that body edge already exists, including a redirect or URL variant that resolves to the same canonical page.
- Use ordinary crawlable links. Do not add internal
nofollow,sponsored, orugcattributes without a documented reason. - Verify the target returns a direct HTTP 200, is indexable, and has the intended canonical. Prefer linking directly to the canonical URL. If evidence is unavailable, mark the edge unverified and do not apply it.
- Quote a real placement from the current source. If it has disappeared, find a genuinely equivalent passage or reject the row. Never invent a claim to justify a link.
- Traffic alone does not make a good hub. Exclude off-topic, thin, duplicate, or unhelpful targets even when they receive visits.
- Start with a bounded manual batch. Bulk insertion requires explicit scope, rollback, and a small checked sample before expansion.
- Use evidence gathered after relevant canonical, redirect, or indexability fixes. Old exports may describe a problem that no longer exists.
- Read back the saved content and publication status. A successful save response is not proof that the link exists.
Diagnose
- Define the crawl scope, capture date, and coverage limits. Combine crawl discovery with published URL inventories to find pages the crawl cannot reach.
- Repair broken body targets and unnecessary redirect hops before adding more links.
- Identify pages with no discovered inbound body links. Separate true discovery problems from pages that should remain excluded or unindexed.
- Find relevant targets with search demand, reader value, or a conversion role. Use query and page data rather than position alone.
- Find potential donors with topical relevance, useful traffic, external links, or strong existing internal coverage.
Report counts for published URLs, unique body edges, orphan candidates, verified target issues, and coverage gaps. If a full crawl is unavailable, label the diagnosis partial.
Plan
Choose the applicable play after hygiene:
- Authority to opportunity: relevant established donors link to useful pages that already show search visibility but need stronger internal discovery.
- Traffic to conversion: visited pages link to relevant conversion pages. Use observed conversion data when available; do not invent conversion rates.
- New to old and old to new: a new article links to established coverage, then older relevant pages are queued for links back to the new article.
Site search such as site:example.com "topic phrase" can discover candidates. It does not prove that a target is current, indexable, or relevant.
Rank edges by reader usefulness, target quality, strategic value, donor strength, and placement quality. Keep the first batch small enough to inspect every saved edit.
Return one row per unique edge:
| Source | Target | Play | Proposed anchor | Exact context quote | Placement | Evidence | Status |
Use concise descriptive anchors that fit the sentence. Avoid empty anchors, "click here", forced exact matches, and repeated target links. Spread links where they help the reader. A link count is not a quota.
Implement
- Fetch the current source and target. Confirm the correct page identity and editing permissions.
- Recheck target status, indexability, canonical, existing body links, and the quoted placement.
- Stage the smallest necessary change. Preserve surrounding claims and formatting.
- Save through the permitted draft, revision, or live workflow.
- Read back the saved body and confirm the exact href, visible anchor, and page status.
- For staged changes to published pages, confirm the live page remains unchanged. For authorized live changes, inspect the rendered page and follow the link.
- Record rejected edges with the reason. Stop the batch if saves alter unrelated content or publication status.
Suggestion plugins may help find candidates. Verify current capabilities against current docs and treat suggestions as leads, not evidence. Keep automatic insertion disabled unless the approved workflow explicitly includes it.
Editorial loop
For each new article:
- Add relevant links to established coverage, including a useful hub when one exists.
- Verify each target and keep the copy readable. Do not pad with weak links.
- Queue relevant older pages for inbound links after the new target is available and verified.
- Keep older-page edits within the same published-source safety rules.
Use verified-seo-article-writing when the article also needs source and claim verification.
Measure
Capture a baseline and agree on follow-up windows before implementation. Compare touched pages with similar untouched pages where possible.
Record unique body inlinks, search impressions, clicks, query mix, position, relevant conversions, and implementation quality. Note seasonality, content changes, releases, and search-result changes. A before-and-after movement alone does not establish causality.
If a repeated insertion rule performs poorly or introduces irrelevant links, stop expansion and review the pattern before changing more pages.
Output contract
Return the edge queue plus:
- Scope, evidence dates, and coverage limits.
- Counts: proposed, rejected, staged, published, and verified edges.
- Verification per applied edge: target checks, body href, anchor, page status, and readback result.
- Remaining blockers and the next measurement date.
Use distinct states: proposed, staged, published, verified, or blocked. Report an unavailable check explicitly. Never report a staged revision as a live result.
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.

