# AI Visibility Measurement

Measures AI engine traffic and cited pages from GA4 referral data.

- Repository: https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills (8540 stars)
- Category: Marketing
- License: MIT
- Last updated: 2026-10-27
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Ryze-AI-Adgent/open-seo-mcp-skills --skill ai-visibility -g -a claude-code -y`
Codex: `npx skills add Ryze-AI-Adgent/open-seo-mcp-skills --skill ai-visibility -g -a codex -y`
Cursor: `npx skills add Ryze-AI-Adgent/open-seo-mcp-skills --skill ai-visibility -g -a cursor -y`
Gemini CLI: `npx skills add Ryze-AI-Adgent/open-seo-mcp-skills --skill ai-visibility -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Ryze-AI-Adgent/open-seo-mcp-skills`

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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?utm_source=github&utm_content=open-seo-mcp-skills

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

The rest: https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills/blob/HEAD/skills/ai-visibility/SKILL.md
