seo-audit
Skill1 starsChanged 34 days agoMITView on GitHub
Run a data-driven SEO audit of a website using Google Search Console and GA4 MCP tools. Use when the user asks for an SEO audit, analysis, review, "how is my site doing in search", traffic analysis, indexing status, or sitemap health. Requires the gsc and analytics MCP servers from this plugin to be connected.
185 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 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 repository3 other files it gives its agents.
- indexnowSkill
- onboard-siteSkill
- setup-google-accessSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 166 edited versions we read keep these.
2
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 14
Run these in order (parallelize where independent):
- Distinctive: line 29
Brand dominance: If the brand query itself ranks below position ~5, flag it (schema.org Organization markup, Google Business Profile, …
“Common” is measured: kept by at least 6 in 10 of the 166 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
Produce a prioritized, evidence-based audit. Every claim must come from actual tool output — never estimate or fill gaps with plausible numbers.
If the gsc and analytics MCP tools are not available in this client (common when this skill was installed standalone, without the plugin's .mcp.json), do not attempt the audit with guesses: first walk the user through connecting the servers using the setup-google-access skill, or the manual client configuration in section 4 of https://github.com/PapiScholz/search-visibility-kit/blob/main/SETUP.md (works with any MCP client).
Data collection
Run these in order (parallelize where independent):
list_properties— get the exactsite_url(prefersc-domain:properties).get_account_summaries— get the GA4 property ID.get_performance_overview(28 days) — clicks, impressions, CTR, position, daily trend.get_search_analyticswithdimensions=query(50 rows) and again withdimensions=page(25 rows).list_sitemaps_enhanced— CRITICAL: comparelast_downloadedagainst today andurl_countagainst the live sitemap's real URL count (fetch the sitemap and count<loc>entries). A stale download date or a lower count than reality means Google is working from an outdated map — resubmit withsubmit_sitemapafter confirming with the user.batch_url_inspectionon the top 8-10 pages by impressions — checkcoverage_stateandlast_crawled.- GA4
run_report: sessions/users/engagementRate bysessionDefaultChannelGroup(28 days), andscreenPageViews/totalUsersbypagePath(top 15). - Optional:
run_realtime_reportfor active users right now.
Analysis framework
Evaluate and report in this order:
- Branded vs non-branded queries. Classify every query. A site with ~100% branded queries has a content problem, not a technical problem — say so plainly. Flag non-branded queries at position 1-10 with low impressions as expansion seeds.
- Brand dominance. If the brand query itself ranks below position ~5, flag it (schema.org Organization markup, Google Business Profile, brand-name collisions).
- CTR opportunities. Pages with impressions > 50 and CTR < 2%: recommend title/meta rewrites tied to the actual queries shown.
- Sitemap and index health. Stale sitemap, non-indexed key pages, crawl dates older than ~30 days on important pages.
- Analytics hygiene. Flag admin/CMS paths (e.g.
/admin) appearing in GA4 top pages — recommend internal traffic filtering. - Channel mix. Direct vs organic ratio, engagement rate per channel. High direct + near-zero organic = visibility problem; organic engagement above site average = quality signal worth scaling.
Output
Deliver: what is healthy (2-3 lines), the 3 findings that matter most (each with the metric that proves it), and concrete next actions ranked by impact. Lead with the most uncomfortable finding, not the most flattering one. State data caveats: GSC data lags ~2 days; low-volume sites have noisy daily numbers.
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.

