Index of every page on this site: llms.txt
All skills
ryze-ai-adgent avatar

/ai-visibility

@f587b0a
Run it yourself

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

Use this Skill: https://skilld.dev/gh/ryze-ai-adgent/open-seo-mcp-skills/ai-visibility

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈78 tokens for metadata: the name and description. ≈543 when used: this file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈309 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

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

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill provides a workflow for tracking AI search engine traffic by integrating Google Analytics and Search Console via a vendor-specific MCP connector. A security finding of low severity was identified related to the processing of external website content.

  • Socket24d

    1 alert: gptAnomaly

  • Snyk24d

    Risk: MEDIUM · 1 issue

Signed by skilld at f587b0a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 weeks ago.

Activeupdated 4 weeks ago

README badge

README badge for ryze-ai-adgent/open-seo-mcp-skills/ai-visibility