Who it is forAn SEO lead or site owner who needs a prioritized list of fixes for a site and does not want to rely on scraped rank estimates.
The problemAudits built on estimated positions can point to the wrong pages, and checking Search Console and GA4 by hand takes hours.
The outcomeA ranked list of audit findings covering indexation, CTR anomalies, decaying pages and quick wins, based on your connected accounts.
What you need first
- Claude Code, or Claude with custom connectors (Cursor and other MCP clients can add the same URL)
- A Google account with access to the Search Console, GA4 and Google Ads properties you want to analyze
- A Ryze workspace sign-in, with Google Search Console and GA4 connected once
- The target domain, for example mysite.com
Steps
- Run
claude mcp add ryze --transport http https://connector.get-ryze.ai/mcpto add the Ryze connector (optional in Claude Code, since the plugin bundles it). - Run
claude plugin marketplace add Ryze-AI-Adgent/open-seo-mcp-skills. - Run
claude plugin install open-seo-mcp-skills@ryze. - Sign in to Ryze, pick your workspace, and connect your Google Search Console and GA4 accounts.
- Ask Claude: "run an SEO audit on mysite.com" and review the findings by priority.
Prompt for your agent
Using the open-seo-mcp-skills seo-audit skill through the Ryze MCP, run a full site audit on <target-domain> covering indexation, CTR anomalies, decaying pages and quick wins. Return a ranked list of findings with the data source for each. Verify that every figure comes from the connected Search Console or GA4 account, not an estimate.
Caveat. The audit reads only the Search Console and GA4 accounts you connect in your Ryze workspace, so results cover only those properties.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page