# Geo AI Visibility

> GEO / AI Visibility

- Skill: `dasexperten/geo-ai-visibility` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add dasexperten/geo-ai-visibility`
- Raw SKILL.md: https://api.skillmd.com/api/skills/dasexperten/geo-ai-visibility/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: dasexperten (https://skillmd.com/u/dasexperten)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/dasexperten/geo-ai-visibility

---

# GEO / AI Visibility

## Purpose

Improve and report Generative Engine Optimization (GEO): how AI systems crawl, understand, cite, and refer traffic to the brand site — without inventing metrics.

## When to Use

- AI Overviews / ChatGPT / Perplexity visibility work  
- AI bot crawl policy (allow/deny)  
- Entity, FAQ, and proof structure for answer engines  
- Reviewing AI Crawlers / Site authority panels in ERP  

## When NOT to Use

- Classic keyword ranking only → `seo-performance-monitor` / `keyword-research-strategist`  
- Ubersuggest DA refresh only → `ubersuggest-site-pulse`  
- Pure Clarity session replay → `microsoft-clarity-analyst`  

## Inputs

- Domain dossier `references/domains/dasexperten.com/geo-ai-visibility.md`  
- Clarity AI Visibility export (if available)  
- GA4 AI-referrer segments  
- CF AI Crawl Control stats (when live)  
- Priority pages and entity facts  

## Workflow

1. Read dossier status table (which sources are live).  
2. Map entities, claims, and proof for priority pages.  
3. Check crawl policy: robots, bot list, accidental blocks.  
4. Diagnose content for answer-readiness (direct answers, FAQ, schema).  
5. If CF/Clarity/GA4 data exists, report real numbers only.  
6. If data is missing, mark **pending** — never invent crawler counts.  
7. Recommend top actions for GEO + classic SEO synergy.  

## Output

- GEO diagnosis  
- Live vs pending data sources  
- Entity / question map gaps  
- Crawl policy notes  
- Content & schema actions  
- ERP UI honesty check (demo markers present if stub)  
- Priority actions  

## Common Mistakes

- Inventing AI crawler request totals  
- Treating Ubersuggest DA as “AI authority”  
- Forgetting `· demo data` on stub ERP panels  
- External outreach that says “backlink / SEO”  

## Related

- `ai-seo-optimizer`, `schema-markup-specialist`, `ubersuggest-site-pulse`  
- Dossier: `references/domains/dasexperten.com/geo-ai-visibility.md`