Menu

Individual skill

internal-links

0upvotes

Audits and designs internal links for a site, page family or article. Use for orphan pages, link equity, click depth, hubs, anchor text, old-post backfill and product navigation.

skills/seo/on-page/internal-links/SKILL.md

Read pinned source

Source commit ac823a127782355339f21aef6c87f1ccff751c84

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,098
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Internal links

## Scope and evidence

State the intended outcome: discovery, access to priority pages, semantic hierarchy, a reading path, product conversion, or diagnosis of missing or overlapping pages. Read the relevant project context from root `{project}.md` when available; otherwise use supplied material. Declare included hosts, locales and surfaces (Blog, Docs, Help Center, app).

Classify clickable destinations by ownership: same-host page, same registered domain on another subdomain (ecosystem), another owned domain, owned social/community channel, third party, or same-page fragment. Report these separately. Canonicals, hreflang, redirects, sitemap and Schema URLs can corroborate findings but do not count as clickable edges. For third-party links in Blog articles use outbound-links.

Establish live nodes from the rendered site and existing page inventory. Use [site-structure-inventory](https://github.com/kostja94/vibe-coding/tree/main/skills/site-structure-inventory) if discovery is needed. Cross-check robots, sitemap, CMS, routes, search console, analytics or logs as available. Label disagreements with source and date: a deployment repository can lag production or contain future work. Record crawl exclusions, sampling and unknowns before calling a page an orphan.

## Compare observed and intended links

1. Crawl reachable in-scope pages and extract rendered links. Distinguish navigation, footer, breadcrumb, body, card, CTA, recommendation and fragment. For large inventories, summarize by page family and URL pattern with examples.
2. For each important page, identify its parent, children, justified peers, useful incoming entrances and next user action. Select the [landing-page workflow](references/landing-pages.md) for product, proof and conversion, or the [Blog workflow](references/blog.md) for education and continued reading. For mixed pages, select the primary role, then inspect the bridge to the other family.
Back to top