Claude Skill

seo-audit

Full SEO audit of a site from its real Search Console + GA4 data — indexation health, CTR anomalies, decaying pages, striking-distance keywords, quick wins. Use when asked to "audit my site", "SEO audit", "why is my organic traffic down", or "SEO health check".

LLM Mart · 0 points · 8 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download Ryze-AI-Adgent-open-seo-mcp-skills-skills_seo-audit-e33761c.zip · 1 KB

ryze-ai-adgent/open-seo-mcp-skills 2114 355 forks MIT Updated 3d ago

Part of ryze-ai-adgent/open-seo-mcp-skills — 8 skills

Install

skills CLI npx skills add https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills/tree/main/skills/seo-audit

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install ryze-ai-adgent-open-seo-mcp-skills@llmmart

Git git clone https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole ryze-ai-adgent/open-seo-mcp-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

SEO Audit

Requires

The free Ryze MCP connector (https://connector.get-ryze.ai/mcp). Claude Code: claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

Audit the user's site using their own data via the Ryze MCP. No estimates — everything below comes from their actual GSC/GA4.

Workflow

Pick the property. google_search_console__listSites. If several, use the one matching the user's domain; confirm only when ambiguous.
Indexation. google_search_console__getIndexationSummary — indexed vs not-indexed counts and reasons. Flag anything unusual (large "Crawled — currently not indexed", spikes in excluded pages).
Performance baseline. google_search_console__runRawSearchAnalytics: last 90 days vs previous 90, dimensions query and page (two calls each period). Compute clicks/impressions/CTR/position deltas.
Find the problems:
- Decaying pages — pages whose clicks dropped >30% period-over-period
- CTR anomalies — queries with position ≤ 5 but CTR < 2% (title/meta problem)
- Striking distance — queries at position 8–20 with high impressions (one push from page 1)
- Cannibalization — same query, multiple ranking pages splitting clicks
Spot-check pages. For the 3–5 worst pages, google_search_console__inspectUrl — canonical, indexing state, last crawl.
Cross-check traffic. google_analytics__runRawReport — organic sessions + conversions by landing page, same periods. A page can hold rankings but lose revenue; call that out.
AI traffic. google_analytics__getAIReferrals for the same window — note whether AI engines are becoming a meaningful channel for this site.

Output

A report with: verdict up top (one paragraph, is the site healthy or not and the #1 issue), then sections — Indexation, Losers, Quick wins (striking distance + CTR fixes, ranked by impressions), Cannibalization — each with a table and the specific fix. End with a prioritized 5-item action list.

Fallbacks

If GSC isn't connected, say so and point to Ryze connector setup (https://help.get-ryze.ai/claude/connect) — do not substitute third-party estimates for the site's own data.

Files (open-seo-mcp-skills)

SKILL.md 2.6 KB

---
name: seo-audit
description: Full SEO audit of a site from its real Search Console + GA4 data — indexation health, CTR anomalies, decaying pages, striking-distance keywords, quick wins. Use when asked to "audit my site", "SEO audit", "why is my organic traffic down", or "SEO health check".
---

# SEO Audit

## Requires

The free Ryze MCP connector (`https://connector.get-ryze.ai/mcp`). Claude Code: `claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp`. claude.ai / Desktop / Cursor: add it as a custom connector with the same URL. Setup: https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp

Audit the user's site using their own data via the Ryze MCP. No estimates — everything below comes from their actual GSC/GA4.

## Workflow

1. **Pick the property.** `google_search_console__listSites`. If several, use the one matching the user's domain; confirm only when ambiguous.
2. **Indexation.** `google_search_console__getIndexationSummary` — indexed vs not-indexed counts and reasons. Flag anything unusual (large "Crawled — currently not indexed", spikes in excluded pages).
3. **Performance baseline.** `google_search_console__runRawSearchAnalytics`: last 90 days vs previous 90, dimensions `query` and `page` (two calls each period). Compute clicks/impressions/CTR/position deltas.
4. **Find the problems:**
   - **Decaying pages** — pages whose clicks dropped >30% period-over-period
   - **CTR anomalies** — queries with position ≤ 5 but CTR < 2% (title/meta problem)
   - **Striking distance** — queries at position 8–20 with high impressions (one push from page 1)
   - **Cannibalization** — same query, multiple ranking pages splitting clicks
5. **Spot-check pages.** For the 3–5 worst pages, `google_search_console__inspectUrl` — canonical, indexing state, last crawl.
6. **Cross-check traffic.** `google_analytics__runRawReport` — organic sessions + conversions by landing page, same periods. A page can hold rankings but lose revenue; call that out.
7. **AI traffic.** `google_analytics__getAIReferrals` for the same window — note whether AI engines are becoming a meaningful channel for this site.

## Output

A report with: verdict up top (one paragraph, is the site healthy or not and the #1 issue), then sections — Indexation, Losers, Quick wins (striking distance + CTR fixes, ranked by impressions), Cannibalization — each with a table and the specific fix. End with a prioritized 5-item action list.

## Fallbacks

If GSC isn't connected, say so and point to Ryze connector setup (https://help.get-ryze.ai/claude/connect) — do not substitute third-party estimates for the site's own data.