seo-audit
Skill6 starsChanged 3 months agoApache-2.0View on GitHub
Use when a site needs a bounded multi-lane SEO assessment with explicit scope, evidence capture, findings, ownership, and limitations; coordinate specialists rather than produce a universal audit score or unverified implementation claim.
185 other projects use a version of this.
Adopted by
Most recently taken up by
- samsam007b/claude-code-standards-kittheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- serejaris/personal-corp-ostheir own version, first seen Nov 15, 2026
- vercel/evetheir own version, first seen Nov 15, 2026
- joaoguirunas/team-ostheir own version, first seen Nov 15, 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★ 61ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- AgriciDaniel/claude-seo★ 30ksame name
- every-app/open-seo★ 28ksame name
- trycompai/crm★ 12ksame name
- Ryze-AI-Adgent/open-seo-mcp-skills★ 8.4ksame name
- TheCraigHewitt/seomachine★ 7.5ksame name
- vercel/eve★ 5.9ksame name
- legions-developer/evilcharts★ 3.2ksame name
- MaxMiksa/Auto-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 repository27 other files it gives its agents.
- llms.txtllms.txt
- ai-search-researchSkill
- ai-visibility-monitorSkill
- optimise-seoSkill
- seo-action-planSkill
- seo-aeoSkill
- seo-agenticSkill
- seo-architectureSkill
- seo-authoritySkill
- seo-commerceSkill
- seo-competitor-pagesSkill
- seo-contentSkill
- seo-geoSkill
- seo-hreflangSkill
- seo-imagesSkill
- seo-localSkill
- seo-news-discoverSkill
- seo-pageSkill
- seo-performanceSkill
- seo-planSkill
- seo-programmaticSkill
- seo-researchSkill
- seo-schemaSkill
- seo-sitemapSkill
- seoSkill
- seo-technicalSkill
- seo-videoSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 165 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read markdown-delivery-contract.md for every task.
- Very specific: line 19
Read references/audit-scope-protocol.md before starting an audit.
- Distinctive: line 25
If an authorized crawler, analytics property, Search Console property, log source, or application access is unavailable, state the gap.
- Very specific: line 37
No universal SEO score, universal engine-mandatory llms.txt, generic crawler policy, or ranking/citation guarantee.
- Distinctive: line 38
Do not count pages, links, words, or tests as proof of quality.
- Distinctive: line 39
Do not say a crawl, bot request, report row, or tool health check proves indexation, AI retrieval, citation, referral, or conversion.
- Distinctive: line 40
Keep security, privacy, accessibility, and legal risks visible even when they are not search-ranking claims.
“Common” is measured: kept by at least 6 in 10 of the 165 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
Multi-lane SEO Audit
Markdown delivery contract
Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.
Lane outputs: site-audit.md; markdown-coverage.md (combine small related steps with stable section links). Audit full eligible HTML-to-Markdown coverage, direct discovery, source parity and ownership alongside conventional SEO lanes. Do not declare full-site coverage from only llms.txt or an XML sample.
Purpose
Plan and synthesize a site assessment across the lanes that matter for the stated goal. This skill does not assume that every site needs every check, crawl a site without authorization, fabricate a complete inventory, or implement the findings.
Read references/audit-scope-protocol.md before starting an audit.
Scope first
Record objectives, domains/properties, representative URLs/templates, locales, environments, access/consent, data sources, time window, exclusions, and decision owners. Choose only relevant lanes: technical, page/content, structured data, media, sitemaps, hreflang, programmatic systems, competitive evidence, AEO/GEO, or measurement.
If an authorized crawler, analytics property, Search Console property, log source, or application access is unavailable, state the gap. Do not treat public snippets or third-party scores as a substitute for the inaccessible evidence.
Workflow
- Design the evidence plan. Define what capture/report proves each expected condition and which findings need current primary documentation.
- Run bounded lane assessments. Route work to the relevant technical, page/content, schema, media, sitemap, international, programmatic, commerce, local, video, news/Discover, agentic, architecture, authority, conventional-performance, or AI-search specialist. Preserve their artifacts and disagreements.
- Classify findings. Mark confirmed defects, supported opportunities, experiments, and unknowns separately. Do not convert incomplete sampling into site-wide certainty.
- Synthesize without false precision. Prioritize by user/business risk, scope, reversibility, dependency, evidence confidence, and owner readiness—not by one blended SEO number.
- Plan delivery. Send validated findings to
seo-action-planfor owner/approval/verification/rollback, then useseo-planfor cross-team sequencing. Establish a baseline before change only when comparison is requested.
Guardrails
- No universal SEO score, universal engine-mandatory
llms.txt, generic crawler policy, or ranking/citation guarantee. - Do not count pages, links, words, or tests as proof of quality.
- Do not say a crawl, bot request, report row, or tool health check proves indexation, AI retrieval, citation, referral, or conversion.
- Keep security, privacy, accessibility, and legal risks visible even when they are not search-ranking claims.
Formal evidence handoff
When this audit needs a cross-team, approval-ready plan, package evidence-bound findings as an immutable seo-findings.json bundle using the checked-out suite contract. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout. Keep every referenced capture/source below raw/, retain declined claims and limitations, and run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Send only a passing bundle to seo-action-plan; otherwise label the handoff provisional.
Output
Produce a scoped audit charter, evidence inventory, lane findings, limitations, prioritized ownership map, and proposed next steps. Mark any implementation proposal as pending approval and link it to an action plan when a formal handoff is needed.
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.

