seo-audit
Skill1 starsChanged 11 days agoMITView on GitHub
Audit and optimize public-facing web pages for search engines and AI search. Covers technical SEO audits (crawlability, Core Web Vitals, structured data), local SEO (LocalBusiness schema, geo-metadata), on-page signals (title tags, meta descriptions, heading hierarchy), and AI search readiness (GEO, llms.txt, structured data for LLM extraction). Use when the user asks about SEO audit, meta tags, structured data, local SEO, Core Web Vitals, crawlability, robots.txt, or public page optimization. Delegates depth to the everything-seo skill.
188 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- harborrank/harborrank-skillstheir own version, first seen Nov 16, 2026
- 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
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 versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 188
- 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
178 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 repository107 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/base.mdcCursor rule
- .cursor/rules/changelog.mdcCursor rule
- .cursor/rules/comments.mdcCursor rule
- .cursor/rules/release.mdcCursor rule
- .cursor/rules/seo-ai-search.mdcCursor rule
- .cursor/rules/testing.mdcCursor rule
- agent-readySkill
- authoring-skills-and-rulesSkill
- blinded-evalSkill
- cloakbrowser-fallbackSkill
- deep-deliberationSkill
- design-rationaleSkill
- dissectSkill
- documentation-writerSkill
- everything-seoSkill
- executeSkill
- generating-app-verifySkill
- inceptionSkill
- kit-workflowsSkill
- marketing-psychologySkill
- media-genSkill
- nlm-skillSkill
- opinionSkill
- proving-change-safetySkill
- refreshing-app-verifySkill
- release-deploySkill
- startup-marketing-brainSkill
- subsystem-walkthroughSkill
- trlSkill
- unmatched-workflowSkill
- agent-readySkill
- authoring-skills-and-rulesSkill
- blinded-evalSkill
- cloakbrowser-fallbackSkill
- deep-deliberationSkill
- design-rationaleSkill
- dissectSkill
- documentation-writerSkill
- everything-seoSkill
- executeSkill
- generating-app-verifySkill
- inceptionSkill
- kit-workflowsSkill
- marketing-psychologySkill
- media-genSkill
- nlm-skillSkill
- opinionSkill
- proving-change-safetySkill
- refreshing-app-verifySkill
- release-deploySkill
- seo-auditSkill
- startup-marketing-brainSkill
- subsystem-walkthroughSkill
- trlSkill
- unmatched-workflowSkill
- agent-readySkill
- authoring-skills-and-rulesSkill
- blinded-evalSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 107
No black-hat SEO: No keyword stuffing, no hidden text, no cloaking, no link-buying, no private blog networks.
“Common” is measured: kept by at least 6 in 10 of the 168 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 & Optimization
Leading words: technical SEO audit, crawlability, Core Web Vitals, structured data, LocalBusiness, schema drift, IndexNow, robots.txt governance.
A phase-separated audit workflow for any public-facing page (local-business
public profiles, landing pages, marketing pages). Depth lives in
references/ and in the companion everything-seo skill.
Phase 1 — Crawl
- [ ] GET /robots.txt is text/plain 200. Allow retrieval bots (OAI-SearchBot,
ChatGPT-User, AppleBot, PerplexityBot) when search=yes; block training
scrapers if policy says so (GPTBot, ClaudeBot, Bytespider); keep
Googlebot fully allowed.
- [ ] Content-Signal on robots.txt matches those User-agent lines, or
n/a: policy not declared yet (name the skip reason).
- [ ] GET /sitemap.xml is XML 200 listing canonical public URLs (not only
"submitted to GSC").
- [ ] Sitemap submitted to Google Search Console + Bing Webmaster Tools.
- [ ] IndexNow implementation present (Bing + Yandex push).🛑 Checkpoint: Confirm the crawl surface is mapped. Do not proceed to
Audit until robots.txt (served + policy) + sitemap served + IndexNow
status are each named. Well-known agent cards → agent-ready.
Phase 2 — Audit
- [ ] Page titles: format "[Business Name] in [City] | [Value Prop]" for
local-business public profiles.
- [ ] Meta descriptions: 120-160 chars, value prop + CTA verb, city if natural.
- [ ] Structured data: LocalBusiness JSON-LD validates in Google Rich Results
Test + Bing Webmaster Tools.
- [ ] Core Web Vitals: INP < 200ms, LCP < 2.5s, CLS < 0.1.
- [ ] Schema drift check: does the JSON-LD match the rendered page content?
(Cypress/Puppeteer test that compares rendered text to JSON-LD fields.)
- [ ] Heading hierarchy: exactly one H1, logical H2/H3 nesting, no skipped
levels.Pull references/local_seo_checklist.md for the full LocalBusiness JSON-LD field list and common mistakes.
🛑 Checkpoint: List every audit failure with the page URL + the specific failure. Do not proceed to Fix until the failure list is enumerated.
Phase 3 — Fix
- [ ] Fix each Phase 2 failure in order: titles → meta → schema → vitals → drift.
- [ ] Bump CONTENT_VERSION (or whatever signal the site uses) so AI indexers
re-fetch.
- [ ] Update llms.txt if new pages were added or page roles changed.
- [ ] Re-run schema validation on every changed page.Phase 4 — Verify
- [ ] Re-run Google Rich Results Test on every changed page — green.
- [ ] Verify robots.txt changes with Google's robots.txt tester.
- [ ] Run a single-page Core Web Vitals check (Lighthouse or field data).
- [ ] Submit changed URLs via IndexNow for Bing + Yandex.
- [ ] Re-check schema drift on the changed pages.Any miss → back to Phase 3.
What NOT to do
- No black-hat SEO. No keyword stuffing, no hidden text, no cloaking, no link-buying, no private blog networks. Algorithmic penalties are recoverable but expensive.
- Do not ignore Bing. Bing + Yandex still drive meaningful traffic in some niches and regions. IndexNow submission is cheap.
- Do not use client-side rendering for content that needs to rank. Use SSR/ISR so the HTML the crawler receives contains the content. CSR-only pages may not be indexed reliably.
- Do not skip the schema drift check. Valid JSON-LD that contradicts the rendered page is worse than no JSON-LD — it signals inconsistency to both classical search and AI extractors.
References
| File | Use it for |
| references/local_seo_checklist.md | LocalBusiness JSON-LD field list, common mistakes, Bing considerations, robots.txt patterns |
../everything-seo/references/semantic_intent.md | AEO/GEO patterns for AI search |
../everything-seo/references/content_automation.md | Content quality + AI writing detection |
../everything-seo/references/technical_seo.md | Deep technical SEO (bot governance, IndexNow, INP) |
../agent-ready/SKILL.md | Well-known agent discovery (not a page-SEO audit) |
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.

