external-link-audit
Skill3 starsChanged 5 months agoMITView on GitHub
Audit a website's external (outbound) links for SEO. Crawls pages to find broken external links, redirected targets, insecure HTTP links, missing rel attributes on affiliate or sponsored links, unsafe target="_blank" usage, and risky or low-quality link destinations. Use when the user asks to audit, analyze, check, or clean up external links, outbound links, broken links to other sites, or affiliate link compliance.
- Installs packages
In this repository19 other files it gives its agents.
- canonical-tag-auditSkill
- content-quality-auditSkill
- core-web-vitals-auditSkill
- full-seo-auditSkill
- heading-structure-auditSkill
- image-seo-auditSkill
- internal-link-auditSkill
- keyword-cannibalization-auditSkill
- llms-txt-auditSkill
- meta-data-auditSkill
- mixed-content-auditSkill
- open-graph-auditSkill
- pagination-auditSkill
- redirect-auditSkill
- robots-txt-auditSkill
- schema-markup-auditSkill
- site-architecture-auditSkill
- sitemap-auditSkill
- soft-404-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 2 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when the user asks to:
- Very specific: line 16
Check affiliate, sponsored, or paid links for correct rel attribution
- Distinctive: line 22
Before starting, confirm with the user:
- Very specific: line 33
If a sitemap is available (/sitemap.xml), fetch it to get the canonical page list.
- Very specific: line 37
Use scripts/extract_external_links.py to crawl the site and collect every external link into a JSON inventory:
- Very specific: line 50
Use scripts/check_external_links.py to resolve the HTTP status of each external target (deduplicated per URL) and run all audit checks:
- Very specific: line 56
Add --sponsored-domains amzn.to,partner.example to flag affiliate domains missing rel="sponsored".
- Very specific: line 76
Write a report following the structure in references/report-template.md:
- Very specific: line 87
Remove or replace the dead link https://gone.example/page on /blog/post-1.
- Very specific: line 88
Update http://partner.example on /resources to https://partner.example
- Very specific: line 89
Add rel="sponsored" to the affiliate link https://amzn.to/xyz on /reviews/widget
- Very specific: line 90
Add rel="noopener" to the target="_blank" link on /about
- Very specific: line 96
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 …
- Very specific: line 106
If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
External Link Audit
Audit the external (outbound) links 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 external/outbound links on a website
- Find broken external links (link rot) or redirected destinations
- Check affiliate, sponsored, or paid links for correct
relattribution - Find insecure
http://outbound links or unsafetarget="_blank"usage - Review which external domains a site links to and how often
Inputs to collect
Before starting, confirm with the user:
- 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. - Scope: full site, a specific section (e.g.,
/blog/), or a list of URLs. - Crawl limits: max pages (default 500) and max depth (default 5) for live crawls.
- Known paid/affiliate domains: domains that must carry
rel="sponsored"(e.g.,amzn.to, affiliate networks), if any.
Workflow
Step 1: Gather the page set and extract external links
- 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
.htmlfiles.
Use scripts/extract_external_links.py to crawl the site and collect every external link into a JSON inventory:
python3 scripts/extract_external_links.py https://example.com --max-pages 500 --max-depth 5 --output external_links.json
# already crawled once (e.g. in a full SEO audit)? skip the crawl and reuse the shared cache:
# python3 scripts/fetch_pages.py https://example.com --output page_cache.json
# python3 scripts/extract_external_links.py --from-cache page_cache.json --output external_links.jsonFor every external link, the inventory records: source page, target URL, target domain, anchor text, rel attributes, target attribute, and whether the link is in <nav>/<footer> or in main content.
Step 2: Check link targets and run the audit
Use scripts/check_external_links.py to resolve the HTTP status of each external target (deduplicated per URL) and run all audit checks:
python3 scripts/check_external_links.py external_links.json --output audit_report.jsonAdd --sponsored-domains amzn.to,partner.example to flag affiliate domains missing rel="sponsored". Add --skip-status-checks to run only the static checks without network requests.
Step 3: Evaluate the audit checks
Evaluate each check defined in references/audit-checks.md. The core checks are:
| Check | Severity |
| Broken external links (4xx/5xx or unresolvable targets) | High |
Affiliate/paid links missing rel="sponsored" | High |
Insecure http:// external links | Medium |
| Redirected external links (3xx targets) | Medium |
target="_blank" without rel="noopener"/noreferrer | Medium |
User-generated content links missing rel="ugc"/nofollow | Medium |
| Generic anchor text on external links | Low |
| Excessive external links on a page (> 100) | Low |
| Sitewide (nav/footer) external links | Low |
Step 4: Produce the report
Write a report following the structure in references/report-template.md:
- Summary: pages crawled, external links found, unique domains, issue counts by severity
- Domain overview: most-linked external domains with link counts and follow/nofollow split
- Issues: one section per failing check, listing source page, target URL, anchor text, and a specific fix
- Prioritized action list: ordered by severity and estimated impact
Step 5: Recommend fixes
For each issue, give a concrete, copy-pasteable recommendation, e.g.:
- Remove or replace the dead link
https://gone.example/pageon/blog/post-1; link to an archived copy or an equivalent live resource - Update
http://partner.exampleon/resourcestohttps://partner.example - Add
rel="sponsored"to the affiliate linkhttps://amzn.to/xyzon/reviews/widget - Add
rel="noopener"to thetarget="_blank"link on/about
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.docxscripts/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.csvscripts/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 checkreferences/report-template.md: report output structurescripts/extract_external_links.py: crawl a site and build the external link inventoryscripts/check_external_links.py: resolve target statuses and run audit checks
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.

