agentleFS
JakeLabateJakeLabate/Claude-SEO-Skills/skills/internal-link-audit/SKILL.md

internal-link-audit

Skill3 starsChanged 5 months agoMITView on GitHub

Audit a website's internal linking structure for SEO. Crawls pages to find broken internal links, orphan pages, redirect chains, deep pages, missing or weak anchor text, and internal link distribution issues. Use when the user asks to audit, analyze, or improve internal links, site structure, link equity, or crawlability of a website.

  • Installs packages

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to:

    line 12
  2. Distinctive:

    Before starting, confirm with the user:

    line 22
  3. Very specific:

    If a sitemap is available (/sitemap.xml), fetch it to get the canonical page list.

    line 32
  4. Very specific:

    Use scripts/crawl_links.py to crawl a live site and extract all internal links into a JSON link graph:

    line 36
  5. Very specific:

    Use scripts/analyze_graph.py to analyze the link graph:

    line 52
  6. Very specific:

    Write a report following the structure in references/report-template.md:

    line 74
  7. Very specific:

    Add 2–3 contextual links to the orphan page /services/seo-audit from topically related pages

    line 86
  8. Very specific:

    If the user wants the report as a .docx (for example, to share with stakeholders or attach to a ticket), save the Markdown report to a file …

    line 93
  9. Very specific:

    If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's …

    line 103

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Internal Link Audit

Audit the internal linking structure of a website and produce an actionable SEO report.

When to use this skill

Use this skill when the user asks to:

  • Audit or analyze internal links on a website
  • Find broken internal links or redirect chains
  • Identify orphan pages (pages with no internal links pointing to them)
  • Review anchor text quality for internal links
  • Improve crawl depth, site architecture, or internal link equity distribution

Inputs to collect

Before starting, confirm with the user:

  1. Site URL or local files: a live site root URL (e.g., https://example.com), a sitemap URL, or a local folder of HTML files.
  2. Scope: full site, a specific section (e.g., /blog/), or a list of URLs.
  3. Crawl limits: max pages (default 500) and max depth (default 5) for live crawls.

Workflow

Step 1: Gather the page set

  • If a sitemap is available (/sitemap.xml), fetch it to get the canonical page list.
  • Otherwise, crawl from the homepage following only same-host links.
  • For local HTML folders, enumerate all .html files.

Use scripts/crawl_links.py to crawl a live site and extract all internal links into a JSON link graph:

python3 scripts/crawl_links.py https://example.com --max-pages 500 --max-depth 5 --output link_graph.json

Step 2: Build the link graph

For every page, record:

  • Outgoing internal links: target URL, anchor text, rel attributes (nofollow), whether the link is in <nav>/<footer> or in main content
  • HTTP status of each target (200, 3xx, 4xx, 5xx)
  • Page metadata: title, canonical URL, meta robots (noindex, nofollow)

Step 3: Run the audit checks

Use scripts/analyze_graph.py to analyze the link graph:

python3 scripts/analyze_graph.py link_graph.json --output audit_report.json

Evaluate each check defined in references/audit-checks.md. The core checks are:

CheckSeverity
Broken internal links (4xx/5xx targets)High
Orphan pages (in sitemap but zero inbound internal links)High
Redirect chains and redirected internal links (3xx targets)Medium
Deep pages (click depth > 3 from homepage)Medium
Generic anchor text ("click here", "read more", bare URLs)Medium
Pages with excessive outgoing links (> 150)Low
Nofollow on internal linksLow
Links to non-canonical or noindexed URLsMedium
Low inbound link count on important pagesMedium

Step 4: Produce the report

Write a report following the structure in references/report-template.md:

  1. Summary: pages crawled, total internal links, issue counts by severity
  2. Issues: one section per failing check, listing affected source page, target page, anchor text, and a specific fix
  3. Opportunities: pages that deserve more internal links, suggested anchor text using target page keywords
  4. Prioritized action list: ordered by severity and estimated impact

Step 5: Recommend fixes

For each issue, give a concrete, copy-pasteable recommendation, e.g.:

  • Replace the broken link /old-page on /blog/post-1 with /new-page
  • Add 2–3 contextual links to the orphan page /services/seo-audit from topically related pages
  • Change anchor text "click here" on /about to descriptive text containing the target page's primary keyword

Optional: export the report

As a Word document (.docx)

If the user wants the report as a .docx (for example, to share with stakeholders or attach to a ticket), save the Markdown report to a file and convert it:

python3 scripts/md_to_docx.py report.md --output report.docx

scripts/md_to_docx.py uses only the Python standard library (no pip install) and renders headings, tables, lists, links, bold/italic, and code blocks. Offer this whenever a user asks for a Word doc, a .docx, or a shareable/downloadable report.

As a CSV of findings (.csv)

If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's audit_report.json directly:

python3 scripts/findings_to_csv.py audit_report.json --output findings.csv

scripts/findings_to_csv.py is also standard-library only. It writes one row per finding, with check and severity columns prepended and list fields (e.g. the pages sharing a duplicate value) joined with ; . Unlike the .docx, which reformats the written report, the CSV is a direct dump of the structured findings: offer it whenever a user wants the data itself, a spreadsheet, or to slice findings by check or severity.

Resources

  • scripts/md_to_docx.py: convert the Markdown report into a Word (.docx) document (standard library only)
  • scripts/findings_to_csv.py: flatten the audit findings JSON into a CSV, one row per finding (standard library only)
  • references/audit-checks.md: full definitions, thresholds, and rationale for every audit check
  • references/report-template.md: report output structure
  • scripts/crawl_links.py: crawl a site and build the internal link graph
  • scripts/analyze_graph.py: run audit checks against a link graph JSON file

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.