geo-platform-optimizer
Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually
What this skill does
# GEO Platform Optimizer ## Core Insight Only **11% of domains** are cited by BOTH ChatGPT and Google AI Overviews for the same query. Each AI search platform uses different indexes, ranking logic, and source preferences. A page optimized for Google AI Overviews may be invisible to ChatGPT, and vice versa. Platform-specific optimization is not optional — it is the foundation of any serious GEO strategy. ## How to Use This Skill 1. Collect the target URL and the site's primary topic/industry 2. Run each platform checklist below against the site 3. Score each platform on the 0-100 rubric 4. Generate GEO-PLATFORM-OPTIMIZATION.md with per-platform scores, gaps, and action items --- ## Platform 1: Google AI Overviews (AIO) ### How AIO Selects Sources - 92% of AIO citations come from pages already ranking in the **top 10 organic results** — traditional SEO is the gateway - However, 47% of citations come from pages ranking **below position 5** — AIO has its own selection logic favoring clarity and directness over raw rank - AIO strongly favors pages with **clean structure, direct answers, and scannable formatting** - Featured snippet optimization has ~70% overlap with AIO optimization - AIO prefers **concise, factual, unambiguous answers** — hedging and filler reduce citation probability ### Optimization Checklist 1. **Question-Based Headings**: Use H2/H3 headings phrased as questions matching real user queries. Check Google's "People Also Ask" for the target topic and mirror those exact phrasings. 2. **Direct Answer in First Paragraph**: After each question heading, provide a clear 1-2 sentence answer immediately. Then expand with supporting detail. The first sentence should be a standalone citation candidate. 3. **Tables and Structured Comparisons**: AIO heavily cites tables. Convert any comparison, pricing, specification, or feature data into HTML tables. Use clear column headers. 4. **Ordered and Unordered Lists**: Step-by-step processes should use ordered lists. Feature lists should use unordered lists. AIO extracts these directly. 5. **FAQ Sections**: Add a dedicated FAQ section with 5-10 real questions. Use proper H3 headings for each question. While FAQPage schema rich results are restricted to govt/health sites since Aug 2023, the content pattern still helps AIO extraction. 6. **Definitions and Glossary Boxes**: For any industry-specific term, provide a clear definition. Format: "**[Term]** is [concise definition]." AIO frequently cites definitions. 7. **Statistics with Sources**: Include specific numbers with attribution. "According to [Source], [statistic]." AIO prefers citeable, specific claims over vague assertions. 8. **Publication Date**: Include a visible publication date and last-updated date. AIO deprioritizes undated content for time-sensitive queries. 9. **Author Byline**: Display author name with credentials. Link to an author page with bio, credentials, and sameAs links. 10. **Page Depth**: Keep target pages within 3 clicks of homepage. AIO rarely cites deep, orphaned content. ### Scoring Rubric (0-100) | Criterion | Points | How to Score | |---|---|---| | Ranks in top 10 for target queries | 20 | 20 if yes, 10 if top 20, 0 if beyond | | Question-based headings present | 10 | 2 points per question heading, max 10 | | Direct answers after headings | 15 | 3 points per direct answer, max 15 | | Tables present for comparison data | 10 | 10 if tables used appropriately, 5 if partial, 0 if absent | | Lists for processes/features | 10 | 10 if present, 5 if partial | | FAQ section with 5+ questions | 10 | 10 if 5+, 5 if 1-4, 0 if none | | Statistics with citations | 10 | 2 points per cited stat, max 10 | | Publication/updated date visible | 5 | 5 if both dates, 3 if one, 0 if none | | Author byline with credentials | 5 | 5 if full byline, 3 if name only, 0 if none | | Clean URL + heading hierarchy | 5 | 5 if H1>H2>H3 clean, 3 if minor issues, 0 if broken | --- ## Platform 2: ChatGPT Web Search ### How ChatGPT Selects Sources - Uses **Bing's search index** as its foundation (not Google) - Top citation sources by domain share: **Wikipedia (47.9%)**, Reddit (11.3%), YouTube, major news outlets - ChatGPT heavily weights **entity recognition** — if your brand exists as a structured entity (Wikipedia, Wikidata, Crunchbase), it is far more likely to be cited - Prefers **authoritative, well-established sources** over new or niche sites - Longer, more comprehensive articles get cited more often than short pieces - ChatGPT tends to cite **the most canonical source** for a claim rather than the original ### Optimization Checklist 1. **Wikipedia Presence**: Check if the brand/person/product has a Wikipedia article. If not, assess notability criteria. If notable, create a draft. If an article exists, ensure it is accurate and current. 2. **Wikidata Entity**: Verify the entity exists on Wikidata (wikidata.org). If not, create a Wikidata item with key properties: instance of, official website, social media links, founding date, headquarters location. 3. **Bing Webmaster Tools**: Verify the site is registered in Bing Webmaster Tools. Submit sitemap. Check for crawl errors. 4. **Bing Index Coverage**: Use `site:domain.com` on Bing to verify key pages are indexed. Bing may have different indexed pages than Google. 5. **Reddit Authority**: Check for brand mentions on Reddit. Identify relevant subreddits. Assess whether the brand participates authentically in discussions. 6. **YouTube Presence**: Verify YouTube channel exists with relevant content. Video descriptions should contain full URLs and entity information. 7. **Authoritative Backlinks**: ChatGPT/Bing weight .edu, .gov, and major publication backlinks heavily. Audit backlink profile for these sources. 8. **Entity Consistency**: Brand name, founding date, leadership, and key facts must be consistent across Wikipedia, Crunchbase, LinkedIn, and the official website. 9. **Comprehensive Content**: Pages targeting ChatGPT citation should be **2000+ words** with thorough topic coverage. ChatGPT prefers single authoritative sources over combining multiple thin pages. 10. **Clear Attribution**: Include "About" sections, company descriptions, and founding stories. ChatGPT uses these for entity grounding. ### Scoring Rubric (0-100) | Criterion | Points | How to Score | |---|---|---| | Wikipedia article exists and is accurate | 20 | 20 if exists, 10 if stub, 0 if none | | Wikidata entity with 5+ properties | 10 | 10 if complete, 5 if basic, 0 if none | | Bing index coverage of key pages | 10 | 10 if full, 5 if partial, 0 if poor | | Reddit brand mentions (positive) | 10 | 10 if active discussions, 5 if mentions, 0 if none | | YouTube channel with relevant content | 10 | 10 if active, 5 if present but sparse, 0 if none | | Authoritative backlinks (.edu, .gov, press) | 15 | 3 points per authoritative backlink category, max 15 | | Entity consistency across platforms | 10 | 10 if consistent, 5 if minor discrepancies, 0 if major | | Content comprehensiveness (2000+ words) | 10 | 10 if thorough, 5 if adequate, 0 if thin | | Bing Webmaster Tools configured | 5 | 5 if verified, 0 if not | --- ## Platform 3: Perplexity AI ### How Perplexity Selects Sources - Top citation sources: **Reddit (46.7%)**, Wikipedia, YouTube, major publications - Perplexity places the **heaviest emphasis on community validation** of all AI search platforms - Strongly favors **discussion threads** where claims are debated, validated, or expanded by multiple participants - Prefers recent content — publication date is a strong ranking signal - Cites **multiple sources per answer** (typically 5-15), so there is more opportunity for mid-authority sites to appear - Uses its own crawling infrastructure in addition to search APIs ### Optimization Checklist 1. **Active Reddit Presence**: The brand or its representatives should participate authentically in relevant subreddit discussions. Not promotional — helpful, specific, and commu
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.