seo-audit
Skill0 starsChanged 4 months agoMITView on GitHub
Audit a web page or a whole site for technical and on-page SEO problems, ranked by what actually moves rankings. Use when asked to review SEO, diagnose why a page does not rank, check metadata and structured data, or prepare a page for indexing.
185 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- alpit-patel/seo-aeo-geo-kittheir own version, first seen Nov 8, 2026
- foverse/seoversetheir own version, first seen Nov 8, 2026
- insight68/Skillstheir own version, first seen Nov 8, 2026
- figueroaignacio/ignaciofigueroa.devtheir own version, first seen Nov 8, 2026
- ftzi/livespectheir own version, first seen Nov 8, 2026
Used with
Projects with it also use openseo-review-web-content, openseo-release-notes and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
JwuthriSkillopenseo-review-web-content
Write and review content for the OpenSEO website (web/) — blog posts, guides, feature pages, FAQs. Distills the philosophy for on-brand, useful, accurate content. Use whenever adding or editing user-facing prose in web/content or web/src.
Also in 5 projects that use this
JwuthriSkillopenseo-release-notes
Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.
Also in 6 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
xfstudioSkillmicro-saas-launcher
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
Also in 5 projects that use this
akii-technologies-ltdSkillkeyword-clustering
Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.
Also in 12 projects that use this
- +4 more from nicepkg
- +2 more from Jwuthri
Other versions185 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 185
- coreyhaines31/marketingskills★ 59ksame name
- anthropics/knowledge-work-plugins★ 35ksame name
- every-app/open-seo★ 27ksame name
- AgriciDaniel/claude-seo★ 20ksame name
- trycompai/crm★ 12ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- legions-developer/evilcharts★ 3.2ksame name
- MaxMiksa/Auto-Company★ 3.2ksame name
- MaxMiksa/Autonomous-Company★ 3.2ksame name
175 more not listed
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 repository9 other files it gives its agents.
- brand-voiceSkill
- document-extractionSkill
- image-genSkill
- linkedin-carouselSkill
- nextjs-conventionsSkill
- og-generatorSkill
- pharosSkill
- skill-distributionSkill
- supabase-migrationsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 167 edited versions we read keep these.
5
Distinctive
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 17
Do not use it for keyword research or content strategy.
- Very specific: line 54
no structured data where the content type clearly has a schema (Article, FAQPage, BreadcrumbList, Product)
- Distinctive: line 67
Write findings as: what is wrong, what it costs, and the exact fix.
- Distinctive: line 77
Never report a count without the list.
- Distinctive: line 84
A low word count: Not a ranking factor on its own.
- Distinctive: line 86
Missing keywords meta tag: No search engine has used it for over a decade.
“Common” is measured: kept by at least 6 in 10 of the 167 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.
Files
SEO audit
Audit a page the way a search engine reads it: fetch the rendered HTML, check what is actually in it, and rank findings by impact rather than by how easy they are to spot.
When to use this
Reach for this skill when someone asks why a page is not ranking, wants metadata or structured data checked, is about to publish something and wants it indexable, or asks for "an SEO check" in any wording.
Do not use it for keyword research or content strategy. This skill inspects what exists.
How to run it
- Get the rendered HTML. Server-rendered markup is what matters. Fetch the URL, or for a local project read the built output rather than the source component.
Run the checker.
python3 scripts/audit.py <url-or-file> --jsonIt returns findings grouped as
critical,importantandpolish.- Read the findings in that order and stop adding your own. The temptation is to
list every deviation from a best-practice checklist. Do not. A page with a missing
<title>does not need a note about image lazy-loading in the same breath.
What gets checked
Critical — the page cannot rank or cannot be indexed:
noindexin a meta robots tag or anX-Robots-Tagheader- missing or empty
<title> - missing
<h1>, or more than one - canonical pointing somewhere unexpected (another host, a redirect, itself via a different protocol)
- the main content is absent from server-rendered HTML and only appears after hydration
- 4xx/5xx on the URL itself or on the canonical target
Important — the page ranks worse than it should:
<title>outside 30-60 characters, or duplicated across pages- meta description missing, or outside 120-160 characters
- heading hierarchy that skips levels
- images without
alt, links whose only text is "hier" or "lees meer" - no structured data where the content type clearly has a schema (
Article,FAQPage,BreadcrumbList,Product) - structured data present but failing validation
- Open Graph or Twitter card incomplete, so shares render bare
Polish — real but small:
- no
langattribute - absolute internal links where relative would do
- trailing-slash inconsistency against the rest of the site
Reporting
Write findings as: what is wrong, what it costs, and the exact fix. One line each.
CRITICAL <title> is empty
Google renders the URL as the result title. Nothing else on this page
matters until this is fixed.
→ app/kennis/[slug]/page.tsx:31 — generateMetadata returns no title when
post.seoTitle is undefined; fall back to post.title.Never report a count without the list. "12 images missing alt text" is not actionable; the twelve paths are.
Things that look like problems and are not
- A canonical that points to itself. That is correct and expected.
- Multiple
<h2>s. Fine. Only<h1>is constrained. - A low word count. Not a ranking factor on its own. A short page that answers the query completely beats a padded one.
- Missing keywords meta tag. No search engine has used it for over a decade.
Files
scripts/audit.py— the checker. Runs offline against a file, or fetches a URL.references/schema-types.md— which structured-data type fits which page, with the required fields for each.
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.

