[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DRB1M7WPCJDH1ANAEPV4T":3,"skill-same:01M75DRB1M7WPCJDH1ANAEPV4T":65},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75DRB1M7WPCJDH1ANAEPV4T","aeo-geo",null,"Optimize AI engine visibility. Use when: AEO\u002FGEO strategy, citation optimization, entity consistency across AI platforms.","LongLeo287\u002FSEOSONA-OS","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M75CK60XQGYJY3YDGGFJQDYT",2,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: aeo-geo\ndescription: \"Optimize AI engine visibility. Use when: AEO\u002FGEO strategy, citation optimization, entity consistency across AI platforms.\"\n---\n\n# AEO\u002FGEO Intelligence\n\n## When to Use This Skill\n\nActivate this module when the user's request involves any of the following:\n\n- **AI Visibility**: Questions about how a brand, product, or person appears in AI-generated answers (ChatGPT, Perplexity, **Google AI Mode**, Google AI Overviews, Copilot, Gemini, Claude)\n- **Answer Engine Optimization (AEO)**: Optimizing content so it gets selected as a source for AI-generated answers\n- **Generative Engine Optimization (GEO)**: Structuring content and entities so generative AI platforms accurately represent a brand\n- **Citation Tracking**: Monitoring which sources AI models cite when answering queries related to a brand or industry\n- **Entity Consistency**: Ensuring brand information is uniform across all knowledge sources that AI models train on or retrieve from\n- **Knowledge Graph Optimization**: Improving how a brand is represented in Google Knowledge Graph, Wikidata, and other structured knowledge bases\n- **Structured Data for AI**: Implementing schema markup and structured data specifically to improve AI comprehension and citation likelihood\n\n**Trigger phrases**: \"AI visibility,\" \"how does ChatGPT describe my brand,\" \"Perplexity results,\" \"AI Mode optimization,\" \"AI Overview optimization,\" \"answer engine,\" \"generative engine,\" \"LLM optimization,\" \"AI citations,\" \"entity consistency,\" \"Knowledge Graph\"\n\n**Google AI Mode (May 2026 — treat as a distinct surface)**: At Google I\u002FO on 19 May 2026 AI Mode became the default search experience for opted-in users, crossed ~1B MAUs, and switched to Gemini 3.5 Flash as the base model. AI Mode is **not** the same as AI Overviews — it is a separate conversational tab with deeper reasoning, multi-turn follow-ups, and a citation pattern that frequently diverges from AI Overviews for the same query. Brands must audit AI Mode independently. Practical implication: an AEO program that only tests AI Overviews + ChatGPT + Perplexity now has a measurable blind spot.\n\n**Additional I\u002FO 2026 announcements that change AEO scope** ([source: blog.google\u002Fproducts-and-platforms\u002Fproducts\u002Fsearch\u002Fsearch-io-2026](https:\u002F\u002Fblog.google\u002Fproducts-and-platforms\u002Fproducts\u002Fsearch\u002Fsearch-io-2026\u002F)):\n\n- **AI Overview → AI Mode follow-up flow** is live worldwide (desktop + mobile) — users can ask a follow-up directly from an AI Overview and flow into a conversational AI Mode session. AEO implication: the *first* impression in an AI Overview is now also a gateway to multi-turn citation. Optimize for being the foundational citation, not just the brief snippet.\n- **Personal Intelligence in AI Mode** is expanding to ~200 countries and 98 languages, no subscription required, with Gmail \u002F Photos \u002F Calendar connections. AEO implication: AI answers are increasingly personalized — generic brand-search results will be reweighted against the user's own context. Brand schema completeness and entity consistency (NAP, services, hours) matter even more.\n- **AI Information Agents** (user-created, monitoring blogs\u002Fnews\u002Fsocial 24\u002F7) launch for AI Pro & Ultra subscribers in summer 2026. AEO implication: brands that publish structured, dated updates on owned channels will be more legible to user-configured agents than those relying on third-party PR pickup.\n\n**Official Google guidance on AI search optimization** (updated 15 May 2026 — [Google AI Optimization Guide](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fai-optimization-guide)):\n\n- **No `llms.txt` file is needed.** Google's official position: \"You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in generative AI search.\" Do not waste time generating `llms.txt` for Google AI Features. (Other AI search engines may or may not consume it; current Anthropic \u002F OpenAI \u002F Perplexity public positions are also that they do not require it. Document any client pressure to ship `llms.txt` as a low-priority deliverable with no measurable upside.)\n- **No special AI-specific schema is needed.** \"Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add.\" Schema continues to matter for classic SEO and rich results.\n- **Eligibility is standard Search.** \"To be eligible to be shown in generative AI features on Google Search, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements.\"\n\n**Opt-out and AI training controls** ([Google AI Features doc](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fai-features)):\n\n- For AI Overviews and AI Mode (inside Google Search): use existing snippet directives — `nosnippet`, `data-nosnippet`, `max-snippet`, `noindex`. Robots.txt for Googlebot is the canonical control. **There is no AI-specific robots\u002Fmeta directive.**\n- For Google's *other* AI systems (Gemini app training, Vertex AI grounding outside Search): use the **Google-Extended** user agent in robots.txt. This is a distinct control from Googlebot.\n- **NEW (3 June 2026):** Search Console now ships an **opt-out toggle** at the property level — flip it to exclude the site from grounding AI Overviews \u002F AI Mode responses without editing robots.txt. See `\u002Fdigital-marketing-pro:gsc-ai-performance` for the decision framework on when to use it.\n\n**EU AI Act Article 50 (applicable 2 August 2026)** — for AI-generated marketing content surfaced in EU markets, see `skills\u002Fcontext-engine\u002Feu-code-of-practice.md` for the voluntary Code of Practice (WG1 providers \u002F WG2 deployers) and the C2PA `c2pa.ai-disclosure` assertion path. Compliance is plugin-level and applies to `c2pa-metadata` outputs.\n\n## Brand Context (Auto-Applied)\n\nBefore producing any marketing output from this module:\n\n1. **Check session context** — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.\n2. **If you need the full profile**, read: `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fprofile.json`\n3. **Apply brand voice** — Formality, energy, humor, authority levels must shape all content tone and word choices\n4. **Check compliance** — Auto-apply rules for brand's target_markets and industry using `skills\u002Fcontext-engine\u002Fcompliance-rules.md`\n5. **Reference industry benchmarks** — Consult `skills\u002Fcontext-engine\u002Findustry-profiles.md` for the brand's industry\n6. **Use platform specs** — Reference `skills\u002Fcontext-engine\u002Fplatform-specs.md` for character limits and format requirements\n7. **Check campaign history** — Run `python \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcampaign-tracker.py\" --brand {slug} --action list-campaigns` before planning new work\n8. **If no brand exists**, say: \"No brand profile found. Use \u002Fdigital-marketing-pro:brand-setup to create one, or I can proceed with general best practices.\"\n9. **Check brand guidelines** — If `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fguidelines\u002F_manifest.json` exists, load and enforce: `restrictions.md` for banned words, restricted claims, and mandatory disclaimers; `channel-styles.md` for channel-specific tone overrides (may differ from base voice); `messaging.md` for approved key messages, taglines, and positioning language; `voice-and-tone.md` for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.\n\nDo not ask the user for information that already exists in their brand profile.\n\n## Required Context\n\nBefore executing AEO\u002FGEO work, gather:\n\n1. **Brand Identity**: Official brand name, key products\u002Fservices, unique value propositions, and brand positioning\n2. **Current AI Footprint**: Ask the user if they have tested how AI platforms currently describe their brand (or offer to audit)\n3. **Target Queries**: The questions and topics the brand wants to be cited for in AI-generated answers\n4. **Existing Content Assets**: Website URL, blog, knowledge base, Wikipedia presence, schema markup status\n5. **Competitive Landscape**: Key competitors who may already have strong AI visibility\n6. **Industry Vertical**: Needed to assess YMYL (Your Money Your Life) sensitivity and trust signal requirements\n\nIf the user cannot provide all context, proceed with what is available and flag gaps as recommendations.\n\n**Minimum viable context**: Brand name and website URL. Everything else can be inferred or discovered during the audit process.\n\n## Capabilities\n\n- **AI Visibility Audit**: Systematic testing of how a brand appears across the 6 canonical surfaces — Google AI Mode, Google AI Overviews, ChatGPT, Perplexity, Gemini, and Copilot — for target queries (scored with the standard defined in `\u002Fdigital-marketing-pro:aeo-audit`)\n- **Citation Optimization**: Restructuring content to maximize the probability of being cited as a source in AI-generated responses\n- **Entity Consistency Audit**: Cross-referencing brand information across Google Knowledge Graph, Wikidata, Wikipedia, Crunchbase, LinkedIn, and industry databases to identify inconsistencies\n- **LLM Content Strategy**: Creating content specifically designed to be ingested and accurately represented by language models\n- **AI Answer Monitoring Framework**: Setting up systematic tracking of AI mentions and citations over time\n- **Structured Data for AI Citation**: Implementing Organization, Product, FAQ, HowTo, and other schema types that improve AI comprehension\n- **Knowledge Graph Optimization**: Improving entity representation in structured knowledge bases\n- **Topical Authority Mapping**: Identifying content gaps that prevent a brand from being recognized as an authority by AI models\n- **AI-First Content Formatting**: Restructuring existing content with clear definitions, factual statements, and citation-worthy snippets\n- **Competitive AI Visibility Benchmarking**: Comparing brand AI presence against competitors across platforms\n\n## Process\n\n**Primary Workflow: AI Visibility Audit & Optimization**\n\n1. **Discovery & Baseline**\n   - Collect brand details, target queries (10-25 queries), and competitor list\n   - Document current schema markup, Knowledge Graph presence, and Wikipedia\u002FWikidata status\n   - Identify the business model to determine which AI platforms matter most\n   - Catalog existing authoritative content assets (whitepapers, research, data, expert bios)\n   - Assess YMYL classification — brands in health, finance, or legal face higher authority thresholds\n\n2. **AI Platform Testing**\n   - For each target query, document how the brand appears (or fails to appear) on:\n     - **Google AI Mode** (default conversational surface, Gemini 3.5 Flash backbone — May 2026)\n     - Google AI Overviews (classic SERP summary block)\n     - ChatGPT (latest model, web-search mode on)\n     - Perplexity\n     - Gemini (gemini.google.com)\n     - Microsoft Copilot\n   - Score each result: Cited (direct mention with link), Referenced (mentioned without link), Absent, Misrepresented\n   - Capture exact AI-generated text for each query as a baseline\n\n3. **Entity Consistency Check**\n   - Audit brand name, founding date, leadership, product descriptions, and key claims across all knowledge sources\n   - Flag inconsistencies between sources (e.g., different founding years on Crunchbase vs. Wikipedia)\n   - Prioritize fixes by source authority weight\n\n4. **Gap Analysis & Strategy**\n   - Identify patterns: Which query types yield citations? Which don't?\n   - Map content gaps: What authoritative content is missing that AI models need?\n   - Assess structured data gaps: What schema markup is missing or incorrect?\n   - Benchmark against competitors who ARE getting cited\n\n5. **Optimization Execution Plan**\n   - Prioritized list of content to create or restructure\n   - Schema markup implementation plan\n   - Knowledge Graph correction\u002Fenhancement steps\n   - Entity consistency fix checklist\n   - Content formatting guidelines for AI-first optimization\n\n6. **Monitoring & Iteration**\n   - Define monitoring cadence (weekly for priority queries, monthly for full audit)\n   - Set up tracking framework to detect citation changes\n   - Establish KPIs: citation rate, accuracy score, query coverage percentage\n   - Track competitor citation changes as part of ongoing monitoring\n   - Re-test after major content updates or schema implementations to measure impact\n   - Log all AI platform model updates that may affect visibility (new model releases, retrieval changes)\n\n**Secondary Workflow: Citation-Optimized Content Creation**\n\n1. Identify a target query cluster where the brand should be cited but currently is not\n2. Analyze what sources ARE being cited for those queries — study their content structure, authority signals, and formatting\n3. Create or restructure content that surpasses cited sources in:\n   - Factual accuracy and specificity (include precise data, dates, numbers)\n   - Clear definitional statements (AI models favor content with unambiguous definitions)\n   - Structured formatting (clear headings, bullet points, tables that AI can parse)\n   - Source credibility signals (author credentials, citations to primary research, organizational authority)\n4. Implement supporting schema markup (FAQ, HowTo, Article, Organization as appropriate)\n5. Build inbound authority signals (internal links from high-authority pages, external citations)\n6. Re-test AI platform responses 2-4 weeks after publication to measure citation pickup\n\n## Reference Files\n\n- `ai-visibility-audit.md` — Step-by-step audit methodology, scoring rubric, and platform-specific testing protocols\n- `citation-optimization.md` — Content restructuring techniques, citation-worthy formatting patterns, and source authority building\n- `entity-consistency.md` — Cross-platform entity audit checklist, Knowledge Graph optimization, Wikidata editing guidelines\n- `llm-content-strategy.md` — AI-first content creation framework, topical authority mapping, and structured data implementation guide\n\n## Output Formats\n\n| Deliverable | Format | Description |\n|---|---|---|\n| AI Visibility Scorecard | Table\u002FSpreadsheet | Query-by-query visibility scores across all AI platforms |\n| Entity Consistency Report | Document | All inconsistencies found with correction instructions |\n| AEO Content Brief | Document | Content creation\u002Frestructuring briefs optimized for AI citation |\n| Schema Markup Spec | Code snippets (JSON-LD) | Ready-to-implement structured data markup |\n| Monitoring Dashboard Spec | Document | KPIs, tracking methodology, and reporting cadence |\n| Competitive AI Visibility Matrix | Table | Side-by-side comparison of brand vs. competitor AI visibility |\n| LLM Content Strategy | Document | 90-day content plan focused on building AI authority |\n\n## Edge Cases\n\n### Brand with Negative AI Perception\n- **Situation**: AI platforms are generating inaccurate or negative information about the brand\n- **Approach**: Prioritize entity consistency fixes and authoritative source correction before any content optimization. Create factual correction content on high-authority owned properties. Do NOT attempt to manipulate AI outputs directly — focus on fixing the underlying source material. Flag potential reputation management needs to the user.\n\n### New Brand with Zero AI Visibility\n- **Situation**: Brand does not appear in any AI-generated answers\n- **Approach**: Start with foundation-building — create a Wikipedia-worthy web presence (not necessarily Wikipedia itself), establish Wikidata entry, implement comprehensive schema markup, and build topical authority content. Set realistic timelines: AI model knowledge has lag times (weeks to months depending on platform).\n\n### Common-Word Brand Names\n- **Situation**: Brand name is a common word (e.g., \"Apple,\" \"Slack,\" \"Monday\")\n- **Approach**: Entity disambiguation is critical. Emphasize co-occurring terms, use full official names in structured data, ensure Knowledge Graph correctly disambiguates, and optimize content with entity-clarifying context. Always include industry\u002Fproduct qualifiers in target queries.\n\n### Multi-Brand Companies\n- **Situation**: Parent company with multiple sub-brands needing separate AI identities\n- **Approach**: Audit each brand entity separately. Ensure clear parent-child relationships in structured data. Avoid cannibalization where sub-brands compete with each other in AI answers. Create distinct topical authority for each brand.\n\n### Regional AI Engines (Baidu, Yandex)\n- **Situation**: User needs visibility on non-Western AI platforms\n- **Approach**: Acknowledge that optimization strategies differ significantly for Baidu (China) and Yandex (Russia). These require localized content, platform-specific structured data standards, and different knowledge bases. Recommend specialized regional expertise if the request goes deep. Provide general framework but flag limitations in specific platform knowledge.\n\n### YMYL Brands (Health, Finance, Legal)\n- **Situation**: Brands in Your Money Your Life categories face elevated trust requirements from AI platforms\n- **Approach**: AI platforms apply stricter source quality thresholds for YMYL topics. Prioritize: (1) Expert authorship with verifiable credentials on all content. (2) Citations to primary research, government sources, and peer-reviewed studies. (3) Medical\u002Flegal\u002Ffinancial review disclosures. (4) Comprehensive E-E-A-T signals (link to Digital PR module for authority building). (5) Schema markup that explicitly declares author qualifications and organizational credentials. Test AI outputs carefully for accuracy — misrepresentation in YMYL categories carries higher reputational risk.\n\n### Rapidly Evolving AI Landscape\n- **Situation**: AI platforms frequently update their models, retrieval methods, and citation behavior\n- **Approach**: Treat all AEO\u002FGEO strategies as living processes, not one-time optimizations. Build monitoring into every engagement. When a major platform update occurs (new model release, retrieval system change, AI Overview format change), re-run the visibility audit for priority queries. Document observed behavior changes and update the workflow accordingly. Maintain a changelog of platform updates and their observed impact on brand visibility.\n\n## Tips & caveats\n\n- **Google's official position (15 May 2026):** no `llms.txt`, no AI-specific schema, no separate AI eligibility gate. Don't manufacture work around fictional ranking factors — schema + entity consistency + citation-worthy formatting are what works.\n- **AI Mode citation patterns frequently differ from AI Overviews** on the same query (internal observation, 05\u002F2026 — the \"40-60%\" figure is a rough estimate, re-verify against your own probe set). Audit and optimise for both, treating them as distinct surfaces.\n- **Entity consistency across Knowledge Graph, Wikidata, Wikipedia, LinkedIn, Crunchbase is the single highest-leverage AEO investment** — more impactful than schema tweaks.\n- **AI citations are stickier than blue-link rankings** but slower to win. Expect 3-6 months of consistent work before measurable shift.\n- **Don't try to \"trick\" AI into citing you** with stuffed content or fake authority signals. AI platforms detect and demote this faster than traditional search.\n- **`Google-Extended` (robots.txt) opts out of Google's *other* AI systems** (Gemini training, Vertex grounding) — distinct from the in-Search-Console toggle for AI Overviews\u002FAI Mode (rolled out 3 Jun 2026 via `\u002Fdigital-marketing-pro:gsc-ai-performance`).\n- **EU markets** require Article 50 disclosure on AI-generated content (applicable 2 Aug 2026) — see `skills\u002Fcontext-engine\u002Feu-code-of-practice.md`.\n\n## Related Skills\n\n- **Content Engine** — For creating and optimizing the actual content that drives AI citations\n- **Analytics & Insights** — For measuring AI visibility performance and tracking citation changes over time\n- **Digital PR & Authority** — For building the E-E-A-T signals and earned media that strengthen AI trust in a brand\n- **Audience Intelligence** — For understanding which queries your target audience is asking AI platforms\n","# AEO\u002FGEO Intelligence\n\n## When to Use This Skill\n\nActivate this module when the user's request involves any of the following:\n\n- **AI Visibility**: Questions about how a brand, product, or person appears in AI-generated answers (ChatGPT, Perplexity, **Google AI Mode**, Google AI Overviews, Copilot, Gemini, Claude)\n- **Answer Engine Optimization (AEO)**: Optimizing content so it gets selected as a source for AI-generated answers\n- **Generative Engine Optimization (GEO)**: Structuring content and entities so generative AI platforms accurately represent a brand\n- **Citation Tracking**: Monitoring which sources AI models cite when answering queries related to a brand or industry\n- **Entity Consistency**: Ensuring brand information is uniform across all knowledge sources that AI models train on or retrieve from\n- **Knowledge Graph Optimization**: Improving how a brand is represented in Google Knowledge Graph, Wikidata, and other structured knowledge bases\n- **Structured Data for AI**: Implementing schema markup and structured data specifically to improve AI comprehension and citation likelihood\n\n**Trigger phrases**: \"AI visibility,\" \"how does ChatGPT describe my brand,\" \"Perplexity results,\" \"AI Mode optimization,\" \"AI Overview optimization,\" \"answer engine,\" \"generative engine,\" \"LLM optimization,\" \"AI citations,\" \"entity consistency,\" \"Knowledge Graph\"\n\n**Google AI Mode (May 2026 — treat as a distinct surface)**: At Google I\u002FO on 19 May 2026 AI Mode became the default search experience for opted-in users, crossed ~1B MAUs, and switched to Gemini 3.5 Flash as the base model. AI Mode is **not** the same as AI Overviews — it is a separate conversational tab with deeper reasoning, multi-turn follow-ups, and a citation pattern that frequently diverges from AI Overviews for the same query. Brands must audit AI Mode independently. Practical implication: an AEO program that only tests AI Overviews + ChatGPT + Perplexity now has a measurable blind spot.\n\n**Additional I\u002FO 2026 announcements that change AEO scope** ([source: blog.google\u002Fproducts-and-platforms\u002Fproducts\u002Fsearch\u002Fsearch-io-2026](https:\u002F\u002Fblog.google\u002Fproducts-and-platforms\u002Fproducts\u002Fsearch\u002Fsearch-io-2026\u002F)):\n\n- **AI Overview → AI Mode follow-up flow** is live worldwide (desktop + mobile) — users can ask a follow-up directly from an AI Overview and flow into a conversational AI Mode session. AEO implication: the *first* impression in an AI Overview is now also a gateway to multi-turn citation. Optimize for being the foundational citation, not just the brief snippet.\n- **Personal Intelligence in AI Mode** is expanding to ~200 countries and 98 languages, no subscription required, with Gmail \u002F Photos \u002F Calendar connections. AEO implication: AI answers are increasingly personalized — generic brand-search results will be reweighted against the user's own context. Brand schema completeness and entity consistency (NAP, services, hours) matter even more.\n- **AI Information Agents** (user-created, monitoring blogs\u002Fnews\u002Fsocial 24\u002F7) launch for AI Pro & Ultra subscribers in summer 2026. AEO implication: brands that publish structured, dated updates on owned channels will be more legible to user-configured agents than those relying on third-party PR pickup.\n\n**Official Google guidance on AI search optimization** (updated 15 May 2026 — [Google AI Optimization Guide](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Ffundamentals\u002Fai-optimization-guide)):\n\n- **No `llms.txt` file is needed.** Google's official position: \"You don't need to create new machine readable files, AI text files, markup, or Markdown to appear in generative AI search.\" Do not waste time generating `llms.txt` for Google AI Features. (Other AI search engines may or may not consume it; current Anthropic \u002F OpenAI \u002F Perplexity public positions are also that they do not require it. Document any client pressure to ship `llms.txt` as a low-priority deliverable with no measurable upside.)\n- **No special AI-specific schema is needed.** \"Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add.\" Schema continues to matter for classic SEO and rich results.\n- **Eligibility is standard Search.** \"To be eligible to be shown in generative AI features on Google Search, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements.\"\n\n**Opt-out and AI training controls** ([Google AI Features doc](https:\u002F\u002Fdevelopers.google.com\u002Fsearch\u002Fdocs\u002Fappearance\u002Fai-features)):\n\n- For AI Overviews and AI Mode (inside Google Search): use existing snippet directives — `nosnippet`, `data-nosnippet`, `max-snippet`, `noindex`. Robots.txt for Googlebot is the canonical control. **There is no AI-specific robots\u002Fmeta directive.**\n- For Google's *other* AI systems (Gemini app training, Vertex AI grounding outside Search): use the **Google-Extended** user agent in robots.txt. This is a distinct control from Googlebot.\n- **NEW (3 June 2026):** Search Console now ships an **opt-out toggle** at the property level — flip it to exclude the site from grounding AI Overviews \u002F AI Mode responses without editing robots.txt. See `\u002Fdigital-marketing-pro:gsc-ai-performance` for the decision framework on when to use it.\n\n**EU AI Act Article 50 (applicable 2 August 2026)** — for AI-generated marketing content surfaced in EU markets, see `skills\u002Fcontext-engine\u002Feu-code-of-practice.md` for the voluntary Code of Practice (WG1 providers \u002F WG2 deployers) and the C2PA `c2pa.ai-disclosure` assertion path. Compliance is plugin-level and applies to `c2pa-metadata` outputs.\n\n## Brand Context (Auto-Applied)\n\nBefore producing any marketing output from this module:\n\n1. **Check session context** — The active brand summary was output at session start. Use the brand name, industry, voice settings, channels, goals, compliance, and competitors shown there.\n2. **If you need the full profile**, read: `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fprofile.json`\n3. **Apply brand voice** — Formality, energy, humor, authority levels must shape all content tone and word choices\n4. **Check compliance** — Auto-apply rules for brand's target_markets and industry using `skills\u002Fcontext-engine\u002Fcompliance-rules.md`\n5. **Reference industry benchmarks** — Consult `skills\u002Fcontext-engine\u002Findustry-profiles.md` for the brand's industry\n6. **Use platform specs** — Reference `skills\u002Fcontext-engine\u002Fplatform-specs.md` for character limits and format requirements\n7. **Check campaign history** — Run `python \"${CLAUDE_PLUGIN_ROOT}\u002Fscripts\u002Fcampaign-tracker.py\" --brand {slug} --action list-campaigns` before planning new work\n8. **If no brand exists**, say: \"No brand profile found. Use \u002Fdigital-marketing-pro:brand-setup to create one, or I can proceed with general best practices.\"\n9. **Check brand guidelines** — If `~\u002F.claude-marketing\u002Fbrands\u002F{slug}\u002Fguidelines\u002F_manifest.json` exists, load and enforce: `restrictions.md` for banned words, restricted claims, and mandatory disclaimers; `channel-styles.md` for channel-specific tone overrides (may differ from base voice); `messaging.md` for approved key messages, taglines, and positioning language; `voice-and-tone.md` for detailed voice rules beyond the 4 numeric scores. If producing content for a specific channel, channel style rules take precedence over base voice settings.\n\nDo not ask the user for information that already exists in their brand profile.\n\n## Required Context\n\nBefore executing AEO\u002FGEO work, gather:\n\n1. **Brand Identity**: Official brand name, key products\u002Fservices, unique value propositions, and brand positioning\n2. **Current AI Footprint**: Ask the user if they have tested how AI platforms currently describe their brand (or offer to audit)\n3. **Target Queries**: The questions and topics the brand wants to be cited for in AI-generated answers\n4. **Existing Content Assets**: Website URL, blog, knowledge base, Wikipedia presence, schema markup status\n5. **Competitive Landscape**: Key competitors who may already have strong AI visibility\n6. **Industry Vertical**: Needed to assess YMYL (Your Money Your Life) sensitivity and trust signal requirements\n\nIf the user cannot provide all context, proceed with what is available and flag gaps as recommendations.\n\n**Minimum viable context**: Brand name and website URL. Everything else can be inferred or discovered during the audit process.\n\n## Capabilities\n\n- **AI Visibility Audit**: Systematic testing of how a brand appears across the 6 canonical surfaces — Google AI Mode, Google AI Overviews, ChatGPT, Perplexity, Gemini, and Copilot — for target queries (scored with the standard defined in `\u002Fdigital-marketing-pro:aeo-audit`)\n- **Citation Optimization**: Restructuring content to maximize the probability of being cited as a source in AI-generated responses\n- **Entity Consistency Audit**: Cross-referencing brand information across Google Knowledge Graph, Wikidata, Wikipedia, Crunchbase, LinkedIn, and industry databases to identify inconsistencies\n- **LLM Content Strategy**: Creating content specifically designed to be ingested and accurately represented by language models\n- **AI Answer Monitoring Framework**: Setting up systematic tracking of AI mentions and citations over time\n- **Structured Data for AI Citation**: Implementing Organization, Product, FAQ, HowTo, and other schema types that improve AI comprehension\n- **Knowledge Graph Optimization**: Improving entity representation in structured knowledge bases\n- **Topical Authority Mapping**: Identifying content gaps that prevent a brand from being recognized as an authority by AI models\n- **AI-First Content Formatting**: Restructuring existing content with clear definitions, factual statements, and citation-worthy snippets\n- **Competitive AI Visibility Benchmarking**: Comparing brand AI presence against competitors across platforms\n\n## Process\n\n**Primary Workflow: AI Visibility Audit & Optimization**\n\n1. **Discovery & Baseline**\n   - Collect brand details, target queries (10-25 queries), and competitor list\n   - Document current schema markup, Knowledge Graph presence, and Wikipedia\u002FWikidata status\n   - Identify the business model to determine which AI platforms matter most\n   - Catalog existing authoritative content assets (whitepapers, research, data, expert bios)\n   - Assess YMYL classification — brands in health, finance, or legal face higher authority thresholds\n\n2. **AI Platform Testing**\n   - For each target query, document how the brand appears (or fails to appear) on:\n     - **Google AI Mode** (default conversational surface, Gemini 3.5 Flash backbone — May 2026)\n     - Google AI Overviews (classic SERP summary block)\n     - ChatGPT (latest model, web-search mode on)\n     - Perplexity\n     - Gemini (gemini.google.com)\n     - Microsoft Copilot\n   - Score each result: Cited (direct mention with link), Referenced (mentioned without link), Absent, Misrepresented\n   - Capture exact AI-generated text for each query as a baseline\n\n3. **Entity Consistency Check**\n   - Audit brand name, founding date, leadership, product descriptions, and key claims across all knowledge sources\n   - Flag inconsistencies between sources (e.g., different founding years on Crunchbase vs. Wikipedia)\n   - Prioritize fixes by source authority weight\n\n4. **Gap Analysis & Strategy**\n   - Identify patterns: Which query types yield citations? Which don't?\n   - Map content gaps: What authoritative content is missing that AI models need?\n   - Assess structured data gaps: What schema markup is missing or incorrect?\n   - Benchmark against competitors who ARE getting cited\n\n5. **Optimization Execution Plan**\n   - Prioritized list of content to create or restructure\n   - Schema markup implementation plan\n   - Knowledge Graph correction\u002Fenhancement steps\n   - Entity consistency fix checklist\n   - Content formatting guidelines for AI-first optimization\n\n6. **Monitoring & Iteration**\n   - Define monitoring cadence (weekly for priority queries, monthly for full audit)\n   - Set up tracking framework to detect citation changes\n   - Establish KPIs: citation rate, accuracy score, query coverage percentage\n   - Track competitor citation changes as part of ongoing monitoring\n   - Re-test after major content updates or schema implementations to measure impact\n   - Log all AI platform model updates that may affect visibility (new model releases, retrieval changes)\n\n**Secondary Workflow: Citation-Optimized Content Creation**\n\n1. Identify a target query cluster where the brand should be cited but currently is not\n2. Analyze what sources ARE being cited for those queries — study their content structure, authority signals, and formatting\n3. Create or restructure content that surpasses cited sources in:\n   - Factual accuracy and specificity (include precise data, dates, numbers)\n   - Clear definitional statements (AI models favor content with unambiguous definitions)\n   - Structured formatting (clear headings, bullet points, tables that AI can parse)\n   - Source credibility signals (author credentials, citations to primary research, organizational authority)\n4. Implement supporting schema markup (FAQ, HowTo, Article, Organization as appropriate)\n5. Build inbound authority signals (internal links from high-authority pages, external citations)\n6. Re-test AI platform responses 2-4 weeks after publication to measure citation pickup\n\n## Reference Files\n\n- `ai-visibility-audit.md` — Step-by-step audit methodology, scoring rubric, and platform-specific testing protocols\n- `citation-optimization.md` — Content restructuring techniques, citation-worthy formatting patterns, and source authority building\n- `entity-consistency.md` — Cross-platform entity audit checklist, Knowledge Graph optimization, Wikidata editing guidelines\n- `llm-content-strategy.md` — AI-first content creation framework, topical authority mapping, and structured data implementation guide\n\n## Output Formats\n\n| Deliverable | Format | Description |\n|---|---|---|\n| AI Visibility Scorecard | Table\u002FSpreadsheet | Query-by-query visibility scores across all AI platforms |\n| Entity Consistency Report | Document | All inconsistencies found with correction instructions |\n| AEO Content Brief | Document | Content creation\u002Frestructuring briefs optimized for AI citation |\n| Schema Markup Spec | Code snippets (JSON-LD) | Ready-to-implement structured data markup |\n| Monitoring Dashboard Spec | Document | KPIs, tracking methodology, and reporting cadence |\n| Competitive AI Visibility Matrix | Table | Side-by-side comparison of brand vs. competitor AI visibility |\n| LLM Content Strategy | Document | 90-day content plan focused on building AI authority |\n\n## Edge Cases\n\n### Brand with Negative AI Perception\n- **Situation**: AI platforms are generating inaccurate or negative information about the brand\n- **Approach**: Prioritize entity consistency fixes and authoritative source correction before any content optimization. Create factual correction content on high-authority owned properties. Do NOT attempt to manipulate AI outputs directly — focus on fixing the underlying source material. Flag potential reputation management needs to the user.\n\n### New Brand with Zero AI Visibility\n- **Situation**: Brand does not appear in any AI-generated answers\n- **Approach**: Start with foundation-building — create a Wikipedia-worthy web presence (not necessarily Wikipedia itself), establish Wikidata entry, implement comprehensive schema markup, and build topical authority content. Set realistic timelines: AI model knowledge has lag times (weeks to months depending on platform).\n\n### Common-Word Brand Names\n- **Situation**: Brand name is a common word (e.g., \"Apple,\" \"Slack,\" \"Monday\")\n- **Approach**: Entity disambiguation is critical. Emphasize co-occurring terms, use full official names in structured data, ensure Knowledge Graph correctly disambiguates, and optimize content with entity-clarifying context. Always include industry\u002Fproduct qualifiers in target queries.\n\n### Multi-Brand Companies\n- **Situation**: Parent company with multiple sub-brands needing separate AI identities\n- **Approach**: Audit each brand entity separately. Ensure clear parent-child relationships in structured data. Avoid cannibalization where sub-brands compete with each other in AI answers. Create distinct topical authority for each brand.\n\n### Regional AI Engines (Baidu, Yandex)\n- **Situation**: User needs visibility on non-Western AI platforms\n- **Approach**: Acknowledge that optimization strategies differ significantly for Baidu (China) and Yandex (Russia). These require localized content, platform-specific structured data standards, and different knowledge bases. Recommend specialized regional expertise if the request goes deep. Provide general framework but flag limitations in specific platform knowledge.\n\n### YMYL Brands (Health, Finance, Legal)\n- **Situation**: Brands in Your Money Your Life categories face elevated trust requirements from AI platforms\n- **Approach**: AI platforms apply stricter source quality thresholds for YMYL topics. Prioritize: (1) Expert authorship with verifiable credentials on all content. (2) Citations to primary research, government sources, and peer-reviewed studies. (3) Medical\u002Flegal\u002Ffinancial review disclosures. (4) Comprehensive E-E-A-T signals (link to Digital PR module for authority building). (5) Schema markup that explicitly declares author qualifications and organizational credentials. Test AI outputs carefully for accuracy — misrepresentation in YMYL categories carries higher reputational risk.\n\n### Rapidly Evolving AI Landscape\n- **Situation**: AI platforms frequently update their models, retrieval methods, and citation behavior\n- **Approach**: Treat all AEO\u002FGEO strategies as living processes, not one-time optimizations. Build monitoring into every engagement. When a major platform update occurs (new model release, retrieval system change, AI Overview format change), re-run the visibility audit for priority queries. Document observed behavior changes and update the workflow accordingly. Maintain a changelog of platform updates and their observed impact on brand visibility.\n\n## Tips & caveats\n\n- **Google's official position (15 May 2026):** no `llms.txt`, no AI-specific schema, no separate AI eligibility gate. Don't manufacture work around fictional ranking factors — schema + entity consistency + citation-worthy formatting are what works.\n- **AI Mode citation patterns frequently differ from AI Overviews** on the same query (internal observation, 05\u002F2026 — the \"40-60%\" figure is a rough estimate, re-verify against your own probe set). Audit and optimise for both, treating them as distinct surfaces.\n- **Entity consistency across Knowledge Graph, Wikidata, Wikipedia, LinkedIn, Crunchbase is the single highest-leverage AEO investment** — more impactful than schema tweaks.\n- **AI citations are stickier than blue-link rankings** but slower to win. Expect 3-6 months of consistent work before measurable shift.\n- **Don't try to \"trick\" AI into citing you** with stuffed content or fake authority signals. AI platforms detect and demote this faster than traditional search.\n- **`Google-Extended` (robots.txt) opts out of Google's *other* AI systems** (Gemini training, Vertex grounding) — distinct from the in-Search-Console toggle for AI Overviews\u002FAI Mode (rolled out 3 Jun 2026 via `\u002Fdigital-marketing-pro:gsc-ai-performance`).\n- **EU markets** require Article 50 disclosure on AI-generated content (applicable 2 Aug 2026) — see `skills\u002Fcontext-engine\u002Feu-code-of-practice.md`.\n\n## Related Skills\n\n- **Content Engine** — For creating and optimizing the actual content that drives AI citations\n- **Analytics & Insights** — For measuring AI visibility performance and tracking citation changes over time\n- **Digital PR & Authority** — For building the E-E-A-T signals and earned media that strengthen AI trust in a brand\n- **Audience Intelligence** — For understanding which queries your target audience is asking AI platforms\n",{"name":5,"description":7},"main","4fd50b1281e8cd978866b6b4556242605cabf708","2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo",1,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS","https:\u002F\u002Fseosona-os.vercel.app","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-10-09 15:14:13",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add LongLeo287\u002FSEOSONA-OS --skill aeo-geo",{"tool":39,"command":40},"bunx","bunx skills add LongLeo287\u002FSEOSONA-OS --skill aeo-geo",{"tool":42,"command":43},"pnpm","pnpm dlx skills add LongLeo287\u002FSEOSONA-OS --skill aeo-geo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo\u002FSKILL.md",true,[47,53,57,61],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"ai-visibility-audit.md","REFERENCE","参考文档",6386,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo\u002Fai-visibility-audit.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"citation-optimization.md",5496,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo\u002Fcitation-optimization.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"entity-consistency.md",5782,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo\u002Fentity-consistency.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"llm-content-strategy.md",6173,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fframeworks\u002Fdigital-marketing-pro\u002Fskills\u002Faeo-geo\u002Fllm-content-strategy.md",[66,73,80,87,94,101],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M75F0T3V3W7JQQ05X26NNN2T","web_crawler_katana","High-speed web crawling using Katana patterns for deep site mapping, URL discovery, and content extraction.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fweb_crawler_katana\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M75F0Q2QJXDGAFKC7D84GT88","server_log_analyzer","Analyzes Nginx\u002FApache server logs to identify Googlebot crawl patterns, errors, and performance bottlenecks.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fserver_log_analyzer\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M75F0KZP6D8R8XPN2YT35BAJ","schema_markup_generator","Auto-generates JSON-LD structured data for any page type (Article, Product, FAQ, LocalBusiness, etc.).","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fschema_markup_generator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M75F0G3KX4Y86AXJXTKXVEVA","internal_linking_optimizer","Analyzes and optimizes the internal link graph of a website for SEO authority distribution.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Finternal_linking_optimizer\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M75F0CS1RYX4YPJC7N6RAAQJ","google_trends_analyzer","Detects trending topics and seasonal patterns using Google Trends data for content planning and keyword strategy.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fgoogle_trends_analyzer\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M75F0ASMQ1GKPFX82D19SRTN","brand_context_analyzer","Tracks brand mentions, sentiment, and online reputation across web sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FSEOSONA-OS\u002Fblob\u002Fmain\u002F2_KNOWLEDGE\u002Fskills\u002Fseo_technical\u002Fbrand_context_analyzer\u002FSKILL.md",[],[]]