← ClaudeAtlas

geo-visibilitylisted

The canonical skill for getting cited and recommended by AI engines (ChatGPT, Google AI Overviews and AI Mode, Perplexity, Claude, Gemini). Explains how each engine selects sources, applies passage-level citability rules (answer-first H2 blocks, self-contained chunks, definitions, sourced statistics, comparison tables), scores pages with a 5-pillar GEO rubric graded 0-100, checks what AI crawlers actually see, and enforces entity consistency plus third-party presence (reviews, YouTube, listicles, versus pages). Use this skill whenever the user mentions GEO, AEO, LLM SEO, AI visibility, AI citations, AI Overviews, being recommended by ChatGPT, brand in AI answers, citability, llms.txt, entity SEO, or asks why competitors appear in AI answers and they do not, or how to optimize content for AI engines. It is the repo reference for citability rules. For measuring mentions, citations, and AI traffic, use geo-tracking. For choosing target prompts and keywords, use seo-keyword-research.
Thibaultbm/claude-seo-geo · ★ 2 · AI & Automation · score 78
Install: claude install-skill Thibaultbm/claude-seo-geo
# GEO Visibility: Getting Cited by AI Engines Generative Engine Optimization (GEO) is the work of becoming a source AI engines retrieve, quote, and recommend. This skill is the canonical reference in this repo for passage-level citability rules: when another skill needs "how to write so AI engines cite it", the rules live here. One framing governs everything below: AI engines do not rank 1000 pages, they sample a short list of sources per subquery and quote passages from them. That changes the job from "rank the page" to "make every passage quotable and make the brand legible everywhere models look". GEO sits on top of SEO, never instead of it: a page that is not indexed cannot be retrieved, and a page that is not retrieved cannot be cited. ## 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. Vault structure, read-first and write-back protocols: the obsidian-brain skill. ## Definitions - GEO (Generative Engine Optimization): the practice of earning citations and recommendations inside