DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to find keywords a competitor ranks for that you do not with Open SEO MCP Skills

Compare a competitor's keyword footprint with your own Search Console queries to find gaps.

Who it is forA content or SEO manager planning new pages after noticing a competitor takes traffic in a topic area.

The problemManually comparing two sites' keyword lists is slow, and third-party estimates may not match what your site actually earns.

The outcomeA list of competitor keywords missing from your own rankings, with DataForSEO data for the competitor and your Search Console data for your site.

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

  1. Run claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp to connect the Ryze MCP.
  2. Run claude plugin marketplace add Ryze-AI-Adgent/open-seo-mcp-skills.
  3. Run claude plugin install open-seo-mcp-skills@ryze.
  4. Ask Claude: "what keywords does competitor.com rank for that I don't?"
  5. Sort the gap list by opportunity and pick topics to feed into the content-brief skill.

Prompt for your agent

Using the open-seo-mcp-skills competitor-gap skill through the Ryze MCP, list keywords that <competitor-domain> ranks for and <target-domain> does not. Return the gap list with the data source for each row, sorted by opportunity. Verify that your-site rankings come from Google Search Console before you call a keyword a gap.

Caveat. Competitor keyword data comes from DataForSEO through the Ryze connector, and your side of the comparison comes only from your connected Search Console account.

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