canonical-tag-audit
Skill3 starsChanged 5 months agoMITView on GitHub
Audit a website's rel=canonical tags for SEO. Crawls pages and probes each canonical target to find missing canonicals, multiple conflicting canonicals, canonicals pointing at non-200 or redirecting or noindexed URLs, relative (non-absolute) canonicals, cross-host canonicals, https-to-http protocol downgrades, conflicts between the HTTP Link header and the in-page canonical, and canonicals containing fragments. Use when the user asks to audit, check, validate, or fix canonical tags, rel=canonical, duplicate-content consolidation, or canonicalization on a website.
- Installs packages
In this repository19 other files it gives its agents.
- content-quality-auditSkill
- core-web-vitals-auditSkill
- external-link-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
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 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.
5
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 18
Verify canonicals are absolute, same-host, and https://
- Distinctive: line 22
Before starting, confirm with the user:
- Very specific: line 80
Write a report following references/report-template.md: summary by severity, high-severity issues first, a section of non-self canonicals …
- Very specific: line 86
Missing: add a self-referencing absolute https:// canonical.
- Very specific: line 99
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 109
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
Canonical Tag Audit
Audit a website's rel="canonical" tags and produce an actionable SEO report.
When to use this skill
Use this skill when the user asks to:
- Audit, validate, or check
rel="canonical"tags / canonicalization - Find pages with missing, duplicate, or conflicting canonicals
- Find canonicals that point at dead, redirecting, or noindexed URLs
- Diagnose duplicate-content consolidation problems
- Verify canonicals are absolute, same-host, and
https://
Inputs to collect
Before starting, confirm with the user:
- Site URL or URL list: a live site root to crawl (auto-seeds from
/sitemap.xml), or a text file of URLs with--url-list. - Scope: how many pages to crawl (default 500, cap with
--max-pages). - Probing: whether to probe each canonical target's status/redirect/noindex
(default on;
--no-probefor a fast structural-only pass).
The indexable contract: a canonical should point at a final, canonical, indexable
200URL, ideally the page itself. A canonical that 404s, redirects, or is noindexed breaks consolidation and can drop the page from the index.
Workflow
Step 1: Crawl and probe canonicals
Use scripts/extract_canonicals.py:
python3 scripts/extract_canonicals.py https://example.com --max-pages 500 --output canonical_inventory.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_canonicals.py --from-cache page_cache.json --output canonical_inventory.jsonIt records each page's status, every in-page <link rel="canonical"> (raw href +
resolved URL), the Link: rel="canonical" header, meta robots, and
X-Robots-Tag, then probes each unique canonical target once for status,
redirect, and noindex.
Step 2: Run the audit checks
Use scripts/audit_canonicals.py:
python3 scripts/audit_canonicals.py canonical_inventory.json --output audit_report.jsonStep 3: Evaluate the audit checks
Evaluate each check in references/audit-checks.md. Core checks:
| Check | Severity |
| Missing canonical on an indexable page | High |
| Multiple conflicting canonicals | High |
| Canonical points to a non-200 URL | High |
| Canonical points to a redirect | High |
| Canonical points to a noindex URL | Medium |
| Relative (non-absolute) canonical | Medium |
| Cross-host canonical | Medium |
| Protocol downgrade (https→http) in canonical | Medium |
| Header / HTML canonical conflict | Medium |
| Canonical contains a fragment | Low |
| Non-self canonical (confirm intent) | Info |
Step 4: Produce the report
Write a report following references/report-template.md: summary by severity,
high-severity issues first, a section of non-self canonicals to confirm, and a
prioritized action list.
Step 5: Recommend fixes
- Missing: add a self-referencing absolute
https://canonical. - Non-200 / redirect target: repoint at the final live
200URL. - Multiple / header conflict: emit exactly one canonical (find the duplicate CMS/plugin source).
- Relative / cross-host / protocol downgrade: rewrite to an absolute,
same-host,
https://URL. - Non-self canonicals: confirm each consolidation is intentional.
- Base every recommendation on observed data; do not invent target statuses.
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 rationalereferences/report-template.md: report output structurescripts/extract_canonicals.py: crawl pages and probe canonical targetsscripts/audit_canonicals.py: run audit checks against the inventory
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.

