generative-engine-optimization
When the user wants to optimize for AI search visibility (ChatGPT, Claude, Perplexity, AI Overviews). Also use when the user mentions "GEO," "AEO," "generative engine optimization," "AI search visibility," "LLM optimization," "GitHub GEO," "Grokipedia," "optimize for ChatGPT," "AI Overviews," "Bing Copilot," "Yandex AI," "Perplexity optimization," "GEO strategy," or "AI search optimization." For third-party publishing strategy (which platforms to use), use parasite-seo. For GitHub repos, README, and Awesome lists, use github. For Medium.com only, use medium-posts. For Grokipedia edits, use grokipedia-recommendations. For traditional Google SERP strategy, use seo-strategy.
What this skill does
# Strategies: GEO (Generative Engine Optimization) Guides GEO/AEO strategy for AI search visibility. GEO optimizes content for ChatGPT, Claude, Perplexity, and AI search summaries (Google AI Overviews, Bing Copilot, Yandex Search with AI)—getting cited in AI-generated answers rather than ranking in traditional SERPs. See **serp-features** for AI search as SERP features; **featured-snippet** for snippet optimization that overlaps with AI Overviews. **When invoking**: On **first use**, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Scope - **GEO** = Generative Engine Optimization - **AEO** = Answer Engine Optimization - **LLMO** = Large Language Model Optimization - **AIO** = Artificial Intelligence Optimization All refer to the same goal: visibility in AI assistant responses. ## GEO vs. SEO | Dimension | SEO | GEO | |-----------|-----|-----| | **Goal** | Rankings in search results | Citations in AI answers | | **User path** | Click → visit → convert | Answer in-place; may not visit | | **Content** | Full page optimization | Clear, citable paragraphs | | **Metrics** | Clicks, traffic | Citations, brand mentions | | **Platforms** | Google, Bing, Yandex (organic) | AI Overviews, Copilot, Yandex AI, ChatGPT, Perplexity | **Both matter**: Create content that ranks and gets cited. AI search summaries (AI Overviews, Copilot, Yandex AI) are **SERP features**—see **serp-features**. When SERP features cause **zero-click** (user gets answer without clicking), citation becomes the primary value; optimize for being cited, not just ranked. ## AI Search Platforms (SERP Features + Standalone) | Platform | Type | Source Selection | Optimization Focus | |----------|------|------------------|---------------------| | **Google AI Overviews** | SERP feature | Top 10–12 organic; Gemini; favors older domains (49% over 15 yrs) | Traditional SEO; structured data; citable blocks | | **Bing Copilot Search** | SERP feature | Bing index; GPT-4; 9.81% domain overlap with Google; favors younger domains (18.85%); LinkedIn signals for B2B | Bing optimization; LinkedIn presence; structured content | | **Yandex Search with AI / Neuro** | SERP feature | Real-time Yandex search; YandexGPT; Russia-focused | Yandex indexing; Russian content; cited sources | | **Perplexity** | Standalone | 200B+ URL index; independent crawl; favors recency, semantic alignment | Content freshness; semantic markup; mid-tier site opportunity | | **ChatGPT (web search)** | Standalone | GPTbot; high-authority, frequently updated, LLM-friendly; favors older domains (45.8%) | Backlinks; structured data; authority signals | **Citation behavior**: AI Overview citations 20–35% higher CTR than equivalent organic. Copilot: shortest responses, fewest links (~3.13/response). Perplexity: prominent URL citations, high trackability. [Geneo](https://geneo.app/blog/chatgpt-vs-perplexity-vs-google-ai-overview-geo-comparison/), [GEO AIO](https://geoaiomarketing.com/how-bing-copilot-selects-sources-compared-to-perplexity/) **Platform traffic context**: Among standalone AI tools, ChatGPT captures ~60%+ of independent Gen AI traffic, Gemini ~20%+, while Claude, Perplexity, and Grok each account for ~2-4%+. These tools reach users directly. SERP features (AI Overviews, Copilot) reach users through existing search flows rather than as independent destinations. Prioritize optimization effort proportionally. ## How GEO Works (RAG & Search Supply) GEO operates through **RAG (Retrieval-Augmented Generation)**—AI tools retrieve content first, then generate answers. The retrieval supply type varies by platform and determines which content surfaces for citation. ### Retrieval Supply Types | Type | Description | Platforms | |------|------------|-----------| | **Self-built index** | Platform maintains its own crawl and search index | Perplexity (200B+ URL index, PerplexityBot); ChatGPT (OAI-SearchBot index) | | **Bound search engine** | Platform uses a fixed first-party search API | Copilot (Bing); Google AI Overviews / AI Mode (Google Search + query fan-out) | | **Third-party API** | Platform contracts a third-party search API | Claude for Government (Brave Search API); smaller AI tools using Tavily, Exa, You.com | | **Hybrid** | Combination of self-built + external API | ChatGPT (OAI-SearchBot + possible search partners); Claude Web Search (supplier not publicly disclosed) | ### Platform Retrieval & Implications | Platform | Primary Supply | Strategic Implication | |----------|---------------|----------------------| | **Google AI Overviews / AI Mode** | Google Search (query fan-out) | Strong traditional SEO + structured data is the most reliable path | | **Bing Copilot** | Bing index | Requires Bing indexing; LinkedIn signals for B2B visibility | | **ChatGPT (web search)** | OAI-SearchBot + partners | High-authority, frequently updated content favored; backlinks matter | | **Perplexity** | Proprietary crawl | Content freshness; semantic alignment; mid-tier sites have opportunity | | **Claude (web search)** | Not publicly disclosed | Focus on general crawlability and clear structured content | **Third-party search APIs** (Tavily, Exa, You.com, Brave Search API) feed smaller AI tools and custom agents. Content that is crawlable and indexed via standard web search reaches these APIs through their supply indexes. **Core model training** (long, costly, not widely actionable): focus on RAG optimization. ## AI Crawlers & Discovery AI crawlers fall into three categories with different implications for content strategy: | Type | Purpose | Examples | Implication | |------|---------|---------|-------------| | **Training crawlers** | Gather data for model training | GPTBot, ClaudeBot, Google-Extended, Meta crawlers | Blocking via robots.txt prevents training data use; **does not** affect real-time search/retrieval by the same provider | | **Index/RAG crawlers** | Build search index for retrieval | OAI-SearchBot, PerplexityBot, Claude-SearchBot, Bytespider (Cohere), AppleBot | **Must allow** for RAG-based AI citation; critical for GEO | | **Real-time crawlers** | Fetch content on-demand at query time | ChatGPT-User (opt-in via web search) | Content must be accessible without a login; paywalls may block citation | **Content discovery**: "Push" submissions for general web content are primarily supported through Bing IndexNow. Google's Indexing API is limited to JobPosting and BroadcastEvent pages only (not general content). OpenAI, Anthropic, Perplexity, xAI, Meta, and DeepSeek do **not** offer public submission portals—their crawlers discover content through standard crawl and sitemaps only. AI crawlers generally do **not** execute JavaScript—critical content must be in initial HTML. See **rendering-strategies** for SSR, SSG, CSR; **site-crawlability** for AI crawler optimization; **robots-txt** for allow/block decisions. [Vercel/MERJ study](https://vercel.com/blog/the-rise-of-the-ai-crawler) (2024) ## Content Best Practices | Practice | Purpose | |----------|---------| | **Direct-answer format** | Answer specific questions in clear paragraphs | | **Entity signals** | Clear brand, product, author identity; see **entity-seo** | | **Citable paragraphs** | Each block understandable on its own | | **Distribution** | Website, **YouTube** (Google prioritizes YouTube in search; ~78% of social media citations in AI Overviews come from YouTube + Reddit), forums, Reddit—thoughtful comments can outrank blog posts | ### Article-Level GEO For blog posts and articles, structure content for AI citation. Studies find content with TL;DR, structured formats, and clear answers is cited substantially more by AI engines. | Element | Guideline | |---------|-----------| | **TL;DR or Key Takeaways** | Choose one: **TL;DR** = 50–100 word bold summary paragraph; **Key Takeaways** = 5–7 bullet point
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".