← ClaudeAtlas

geo-trackinglisted

The canonical measurement skill for AI visibility, fully doable without paid tools or API keys. Sets up GA4 AI traffic reporting (custom channel group with a complete referrer regex placed above Referral), runs a monthly 50-100 buyer prompt panel to compute brand mention rate, citation rate, and share of voice versus competitors across ChatGPT, Perplexity, Google AI Overviews, Claude, and Gemini, and reads server logs for verified AI crawler and assistant fetcher hits as a leading indicator. Use this skill whenever the user wants to track AI traffic, measure ChatGPT or Perplexity referrals, see AI assistant visits in GA4, monitor brand mentions in AI answers, run prompt tracking, compute share of voice, build a monthly GEO report, prove AI visibility to a client, or detect AI bots in server logs. It is the repo reference for measurement. For building the prompt panel itself, use seo-keyword-research. For improving citation rates once gaps are found, use geo-visibility.
Thibaultbm/claude-seo-geo · ★ 2 · AI & Automation · score 78
Install: claude install-skill Thibaultbm/claude-seo-geo
# GEO Tracking: Measuring AI Visibility AI visibility is measurable today, for free, at three layers of the funnel. Each layer answers a different question: | Layer | Data source | Question it answers | Lag | |---|---|---|---| | Traffic | GA4 | How many visits and conversions do AI assistants send? | Trailing (after the click) | | Answers | Prompt panel | What do AI engines say about the brand when buyers ask? | Current state | | Retrieval | Server logs | Are AI systems reading the pages right now? | Leading (before citations appear) | Run all three. GA4 alone undercounts structurally, panels alone miss revenue proof, logs alone say nothing about what answers contain. The combination is the measurement system; paid platforms are an optional layer on top, never the starting point. This skill is the canonical measurement reference in this repo. Build the prompt panel with seo-keyword-research; act on the gaps with geo-visibility. ## Company knowledge first (Obsidian) If the working environment contains an Obsidian vault or any local knowledge base (a folder of .md notes, often with a .obsidian directory), read the relevant notes before acting: brand and product facts, target keywords, competitors, and the SEO action log of what was already tried. Ground every recommendation in that context instead of asking the user for facts the vault already holds. At the end of the session, append the actions taken to the vault's SEO action log so the next session starts informed. Vaul