Agent skill · Content & Marketing

seo-geo

Optimize content for AI Overviews (formerly SGE), ChatGPT web search, Perplexity, and other AI-powered search experiences. Generative Engine Optimization (GEO) analysis including brand mention signals, AI crawler accessibility, llms.txt compliance, passage-level citability scoring, and platform-specific optimization. Use when user says "AI Overviews", "SGE", "GEO", "AI search", "LLM optimization", "Perplexity", "AI citations", "ChatGPT search", or "AI visibility".

Infrasity-Labsgithub.com/Infrasity-LabsGitHub ↗
claude-codeMIT
Install
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill seo-geo --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 3
SKILL.md size: 9 KB
Bundled scripts: none
Path: .claude/skills/seo-geo/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 97
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# AI Search / GEO Optimization (May 2026) ## Primary Source: Google's AI Optimization Guide Google's official position, published under Search Central docs: > "Optimizing for generative AI search is **still SEO** from Google's > perspective. AEO and GEO are rebranded labels for the same work." Read `references/google-ai-optimization-guide.md` for the full synthesis, myth-busting list (`llms.txt`, chunking, AI-rephrasing, mention-farming — all rejected by Google as ineffective), and the Who/How/Why test for content quality. Audits should frame GEO findings as **SEO fundamentals applied to AI-search surfaces**, not as a separate optimization discipline. When community recommendations contradict Google's primary source, defer to Google and note the contradiction in the report. ## Key Statistics | Metric | Value | Source | |--------|-------|--------| | AI Overviews reach | 1.5 billion users/month across 200+ countries | Google | | AI Overviews query coverage | 50%+ of all queries | Industry data | | AI-referred sessions growth | 527% (Jan-May 2025) | SparkToro | | ChatGPT weekly active users | 900 million | OpenAI | | Perplexity monthly queries | 500+ million | Perplexity | ## Critical

What's inside
Steps it walks through
  1. Primary Source: Google's AI Optimization Guide
  2. Key Statistics
  3. Critical Insight: Brand Mentions > Backlinks
  4. GEO Analysis Criteria (Updated)
  5. 1. Citability Score (25%)
  6. 2. Structural Readability (20%)
  7. 3. Multi-Modal Content (15%)
  8. 4. Authority & Brand Signals (20%)
  9. 5. Technical Accessibility (20%)
  10. AI Crawler Detection
  11. llms.txt Standard
  12. RSL 1.0 (Really Simple Licensing)
  13. Platform-Specific Optimization
  14. Output
Ships with 2 files
  • references/google-ai-optimization-guide.md
  • references/llmstxt-evidence.md
More from dev-gtm-claude-skills
All skills →
About this skill
What does the seo-geo skill do?

Optimize content for AI Overviews (formerly SGE), ChatGPT web search, Perplexity, and other AI-powered search experiences. Generative Engine Optimization (GEO) analysis including brand mention signals, AI crawler accessibility, llms.txt compliance, passage-level citability scoring, and platform-specific optimization. Use when user says "AI Overviews", "SGE", "GEO", "AI search", "LLM optimization", "Perplexity", "AI citations", "ChatGPT search", or "AI visibility".

How do I install it?

Run `npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill seo-geo --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going