Atlas / Skills / ryze-ai-adgent / open-seo-mcp-skills

open-seo-mcp-skillsSAFE

skills/ryze-ai-adgent/open-seo-mcp-skills

Free SEO MCP server + open-source SEO and GEO skills for Claude: keyword research, rank tracking, audits, backlinks, AI visibility on your real GSC/GA4/ads data. claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
—
Hosts
4 documented
License
MIT
Stars
5,203
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://www.get-ryze.ai/how-to-connect-claude-to-google-meta-ads-mcp?utmsource=github&utmcontent=open-seo-mcp-skills)

Skip the setup: use the hosted Ryze MCP (Google sign-in, Search Console and GA4 connected in one step, approval-gated changes).

[Connect Ryze in one click →](https://www.get-ryze.ai/developers?utm_source=github&utm_content=open-seo-mcp-skills)

Open-source SEO + GEO skills for Claude on a free SEO MCP server (the Ryze connector) — keyword research, rank tracking, site audits, backlinks, competitor gaps, AI visibility — running on your own Search Console, Analytics and ads data through the Ryze MCP, with DataForSEO built in for the data Google won't give you.

No subscription for the tool. No markup on API calls. The skills are MIT — take them, change them, ship them.

Why this exists

"Open source SEO tools" are having a moment. Look closer and most are a UI over the DataForSEO API: you either bring your own key and pay per request, or pay a hosted subscription plus a ~28% markup on every data call. The code is free; the data never was.

This takes the opposite approach:

  • Your rankings come from your actual Google Search Console — real positions, real clicks, not estimates
  • Your traffic comes from your actual GA4 — including AI referral traffic (ChatGPT, Perplexity, Claude, Gemini)
  • Your keyword volumes come from Google Ads keyword planner data
  • Competitor keywords, backlinks and SERPs come from DataForSEO, already wired into the Ryze connector — no key to manage, no markup layer to build
  • Ahrefs and Semrush are also connectable if you already pay for them

Quick start

claude mcp add ryze --transport
Read from source at commit 0aea061222bbOBSERVED · 2026-10-13
02

Install

Commands as the repository documents them. They are shown, not run.

claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp
claude plugin install open-seo-mcp-skills@ryze
git clone https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills && cp -r open-seo-mcp-skills/skills/* ~/.claude/skills/
03

Host compatibility

What the documentation claims. We have not run a compatibility test.

HostStatusNotes
claude-codementioned
claude-desktopmentioned
copilotmentioned
cursormentioned
04

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: ai-visibility
description: Measure real AI-engine visibility — traffic from ChatGPT, Perplexity, Claude, Gemini and which pages they cite — from actual GA4 referral data, not prompt sampling. Use when asked "AI visibility", "GEO/AEO check", "do LLMs cite us", "traffic from ChatGPT", or "how do we show up in AI search".
---

# AI Visibility

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

Every "AI visibility tracker" samples prompts and guesses. GA4 records the actual clicks AI engines send. Measure the real thing first, then diagnose.

## Workflow

1. **Traffic by engine.** `google_analytics__getAiTrafficByEngine` — sessions per AI source (ChatGPT, Perplexity, Gemini, Claude, Copilot...), current vs previous period.
2. **Trend.** `google_analytics__getAiTrafficDaily` — is AI traffic growing, and did anything spike (a spike = something started citing you; find it).
3. **Cited pages.** `google_analytics__getAiLandingPages` — which URLs AI engines actually send people to. These are your proven-citable pages.
4. **Referral detail.** `google_analytics__getAIReferrals` for source-level detail and conversions — is AI traffic converting better or worse than organic.
5. **Diagnose the winners.** Read the top 2–3 cited pages (fetch them). Note the pattern: direct answers high on the page, stats/definitions, clean headings, schema. That pattern is the citation recipe for this site.
6. **Find the misses.** Cross-reference with `google_search_console__runRawSearchAnalytics`: pages with strong organic queries but zero AI referrals — candidates to restructure toward the citation recipe from step 5.

## Output

Verdict (AI traffic share of organic, trend, top engine), then: engine table, cited-pages table with conversions, the citation recipe observed on winning pages, and a top-5 list of pages to restructure. Keep it concrete — name the pages and the exact change.

## Fallback

If the GA4 AI-traffic tools aren't available in the workspace, build the same report with `google_analytics__runRawReport` filtered on `sessionSource` matching known AI referrers (chatgpt.com, perplexity.ai, gemini.google.com, claude.ai, copilot.microsoft.com).
05

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codePASS
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (1)

INFOInventory / provenance · inv.oversize · CWE-1104
ghs-toplight.png
ghs-toplight.png
Why it matters. 4048907 bytes not read

Gates applied: no_behavioural_pass.

Audited 2026-10-13 · audit v0.4.1 · source sha 0aea061222bbfull audit observations/trust-audit/skill/ryze-ai-adgent__open-seo-mcp-skills.json · Report an issue / request a re-scan
06

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-130aea061222bbSAFEB89first audit
07

Questions

What does the open-seo-mcp-skills skill do?

Free SEO MCP server + open-source SEO and GEO skills for Claude: keyword research, rank tracking, audits, backlinks, AI visibility on your real GSC/GA4/ads data. claude mcp add ryze --transport http https://connector.get-ryze.ai/mcp

Is open-seo-mcp-skills safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can open-seo-mcp-skills access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

Which assistants does open-seo-mcp-skills work with?

Its documentation mentions claude-code, claude-desktop, copilot and cursor. That is what the text claims, not a compatibility test we ran.

How current is this page?

The grade is for one exact copy of the source (0aea061222bb), read on 2026-10-13. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement