Claude Skill

ai-visibility

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 i

LLM Mart · 0 points · 10 39 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download Ryze-AI-Adgent-open-seo-mcp-skills-skills_ai-visibility-e33761c.zip · 1 KB

ryze-ai-adgent/open-seo-mcp-skills 1020 109 forks MIT Updated 16d ago

Part of ryze-ai-adgent/open-seo-mcp-skills — 8 skills

Install

skills CLI npx skills add https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills/tree/main/skills/ai-visibility

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install ryze-ai-adgent-open-seo-mcp-skills@llmmart

Git git clone https://github.com/Ryze-AI-Adgent/open-seo-mcp-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole ryze-ai-adgent/open-seo-mcp-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Traffic by engine. google_analytics__getAiTrafficByEngine — sessions per AI source (ChatGPT, Perplexity, Gemini, Claude, Copilot…), current vs previous period.
Trend. google_analytics__getAiTrafficDaily — is AI traffic growing, and did anything spike (a spike = something started citing you; find it).
Cited pages. google_analytics__getAiLandingPages — which URLs AI engines actually send people to. These are your proven-citable pages.
Referral detail. google_analytics__getAIReferrals for source-level detail and conversions — is AI traffic converting better or worse than organic.
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.
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).

Files (open-seo-mcp-skills)

SKILL.md 2.4 KB

---
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).