website-seo-audit
Skill3 starsChanged 4 months agoMITView on GitHub
Crawl any website and produce a graded SEO diagnosis — on-page (title, meta, headings, canonical, mobile viewport, image alt, thin content), technical (HTTPS, robots.txt, sitemap.xml, broken internal links, duplicate titles/meta, near-orphan pages), and structured data (JSON-LD / Schema.org validity and required fields). Zero config, no API keys, pure Python standard library. Use when the user wants to audit, diagnose, check, or review a website's SEO, find SEO problems, or asks "how is my site's SEO / 帮我诊断这个网站的SEO".
- Installs packages
2 other projects use a version of this.
Adopted by
Most recently taken up by
- spenchey/ClaudeSkillstheir own version, first seen Apr 6, 2026
- get-proofpilot/claude-skills-catalogtheir own version, first seen Mar 23, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- get-proofpilot/claude-skills-catalog★ 1same name
- spenchey/ClaudeSkills★ 0same 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 repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
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 33
If you're calling it from another working directory, run it from the skill folder (the package must be importable):
- Very specific: line 57
Run the tool on the URL the user gave.
- Distinctive: line 59
Read the Markdown report. Lead with the score/grade and the issue counts.
- Distinctive: line 64
Do not dump the whole raw report unless asked — summarize the score, the critical/warning items, and what to fix first.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Website SEO Audit （网站SEO诊断）
Diagnose any website's SEO by crawling it and checking dozens of on-page, technical, and structured-data signals. No API keys, no setup, no third-party packages — it runs on the Python standard library alone.
When to use this skill
- The user asks to audit / diagnose / check / review a website's SEO.
- The user shares a URL and asks what's wrong with it for search.
- The user wants a before/after SEO comparison, or a report they can act on.
How to run
From this skill's directory:
python3 -m seo_audit https://example.comIf you're calling it from another working directory, run it from the skill folder (the package must be importable):
cd /path/to/website-seo-audit && python3 -m seo_audit https://example.comUseful options:
| Option | Meaning |
-1, --single | Audit only the given URL (no crawl) |
--max-pages N | Max pages to crawl (default 50) |
--max-depth N | Max crawl depth (default 3) |
--json | Machine-readable JSON instead of Markdown |
-o FILE | Write the report to a file |
--ignore-robots | Crawl even if robots.txt disallows (use on sites you own) |
--no-link-check | Skip broken-link detection (faster) |
The command prints a Markdown report to stdout and exits non-zero if any critical issue was found (handy for CI).
How to interpret and report back
- Run the tool on the URL the user gave. Use the default crawl unless they only
want a single page (
--single) or a bigger sweep (--max-pages). - Read the Markdown report. Lead with the score/grade and the issue counts.
- Walk through findings in order: 🔴 critical first, then 🟡 warnings, then the highest-value 🟢 notices. For each, state the problem and its concrete fix.
- Offer next steps: re-run after fixes, crawl deeper, or export JSON.
Do not dump the whole raw report unless asked — summarize the score, the critical/warning items, and what to fix first.
What it checks
- On-page: title (presence/length/uniqueness), meta description, H1 &
heading hierarchy, canonical, mobile viewport,
html lang, image alt text, thin content, Open Graph, mixed content on HTTPS. - Technical: HTTPS, robots.txt (missing / blocks-all / sitemap directive), sitemap.xml (presence/validity), broken internal links (HTTP 4xx/5xx), duplicate titles/meta across pages, pages with no internal links.
- Structured data: JSON-LD syntax validity and required Schema.org fields for Article, Product, Organization, BreadcrumbList, FAQ, Recipe, Event, and more — the signal most crawl-based tools ignore, and what AI answer engines read.
Notes
- Requires Python 3.8+. No
pip installneeded. - Respects
robots.txtby default; pass--ignore-robotson your own sites. - Stays on the same site (apex +
www); external links are not followed.
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.