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".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
google_analytics__getAiTrafficByEngine — sessions per AI source (ChatGPT, Perplexity, Gemini, Claude, Copilot…), current vs previous period.google_analytics__getAiTrafficDaily — is AI traffic growing, and did anything spike (a spike = something started citing you; find it).google_analytics__getAiLandingPages — which URLs AI engines actually send people to. These are your proven-citable pages.google_analytics__getAIReferrals for source-level detail and conversions — is AI traffic converting better or worse than organic.google_search_console__runRawSearchAnalytics: pages with strong organic queries but zero AI referrals — candidates to restructure toward the citation recipe from step 5.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.
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).
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Backlink profile for any domain — referring domains, authority, anchors, new/lost links, and a side-by-side vs a competitor. Use when asked "check my backlinks", "backlink profile of X", "who links to them", or "link gap vs competitor".
日本語の概要は準備中です。原文の説明を表示しています。
Find keywords a competitor ranks for that the user's site doesn't — the content gap, prioritized by volume and winnability. Use when asked "what does competitor.com rank for", "keyword gap vs X", "steal competitor keywords", or "why do they outrank us".
日本語の概要は準備中です。原文の説明を表示しています。
SERP-driven content brief for a target keyword — what ranks, what to cover, headings, questions, internal links from your own data. Use when asked for a "content brief", "outline to rank for X", "what should this article cover", or before writing any SEO page.
日本語の概要は準備中です。原文の説明を表示しています。
Keyword research from a seed topic — ideas, real Google volume/CPC, intent, difficulty, clustered into a plan. Use when asked to "find keywords", "keyword research for X", "what should I rank for", or "build a keyword plan".
日本語の概要は準備中です。原文の説明を表示しています。
Rank tracking without a tracker subscription — position movers between any two periods from real Search Console data. Use when asked "how are my rankings", "what moved this week/month", "track my keywords", or "did the update hit me".
日本語の概要は準備中です。原文の説明を表示しています。
Full SEO audit of a site from its real Search Console + GA4 data — indexation health, CTR anomalies, decaying pages, striking-distance keywords, quick wins. Use when asked to "audit my site", "SEO audit", "why is my organic traffic down", or "SEO health check".
日本語の概要は準備中です。原文の説明を表示しています。