agentleFS
PapiScholzPapiScholz/search-visibility-kit/skills/seo-audit/SKILL.md

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

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.
  • JwuthriSkill

    openseo-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

  • JwuthriSkill

    openseo-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

  • nicepkgSkill

    community-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

  • nicepkgSkill

    ph-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

  • xfstudioSkill

    micro-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-ltdSkill

    keyword-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

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
  1. Distinctive:

    Run these in order (parallelize where independent):

    line 14
  2. Distinctive:

    Brand dominance: If the brand query itself ranks below position ~5, flag it (schema.org Organization markup, Google Business Profile, …

    line 29

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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):

  1. list_properties — get the exact site_url (prefer sc-domain: properties). get_account_summaries — get the GA4 property ID.
  2. get_performance_overview (28 days) — clicks, impressions, CTR, position, daily trend.
  3. get_search_analytics with dimensions=query (50 rows) and again with dimensions=page (25 rows).
  4. list_sitemaps_enhanced — CRITICAL: compare last_downloaded against today and url_count against 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 with submit_sitemap after confirming with the user.
  5. batch_url_inspection on the top 8-10 pages by impressions — check coverage_state and last_crawled.
  6. GA4 run_report: sessions/users/engagementRate by sessionDefaultChannelGroup (28 days), and screenPageViews/totalUsers by pagePath (top 15).
  7. Optional: run_realtime_report for 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.