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".
npx skills add https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills --skill seo-audit
Audit the user's site using their own data via the Ryze MCP. No estimates — everything below comes from their actual GSC/GA4.
google_search_console__listSites. If several, use the one matching the user's domain; confirm only when ambiguous.google_search_console__getIndexationSummary — indexed vs not-indexed counts and reasons. Flag anything unusual (large "Crawled — currently not indexed", spikes in excluded pages).google_search_console__runRawSearchAnalytics: last 90 days vs previous 90, dimensions query and page (two calls each period). Compute clicks/impressions/CTR/position deltas.google_search_console__inspectUrl — canonical, indexing state, last crawl.google_analytics__runRawReport — organic sessions + conversions by landing page, same periods. A page can hold rankings but lose revenue; call that out.google_analytics__getAIReferrals for the same window — note whether AI engines are becoming a meaningful channel for this site.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.
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.
Take ryze-ai-adgent/seo-audit from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.