content-geo

Overview

AI answer surfaces (Google AI Overviews and AI Mode, ChatGPT search, Perplexity, Copilot, Claude, Gemini) retrieve passages, compose an answer, and cite a few sources. Use this skill when planning, writing, or auditing content that should be retrieved and cited there. Generative engine optimization (GEO, also sold as AEO) is not a separate discipline: Google's May 2026 AI optimization guide says its generative features are "rooted in our core Search ranking and quality systems." Crawlable, indexable, genuinely useful pages remain the foundation.

Mental model

Each engine expands a prompt into several sub-queries (query fan-out), retrieves passages from its own index or search partners, and cites the passages that best support the answer. A page wins by being retrievable by that engine, holding the clearest and most specific passage for one sub-query, and offering something the commodity pages don't.

Ranking helps but no longer guarantees a citation. Ahrefs' 2026 study (863k keywords) found about 38% of AI Overview citations rank in Google's top 10 for the same query, down from 76% in its July 2025 study (parser changes and the Gemini 3 switch limit comparability). Clicks are scarcer too: Pew's 2025 browsing study found users clicked a traditional result on 8% of visits with an AI summary versus 15% without, and clicked a cited link inside the summary on 1%. Measure citations and impressions, not only clicks.

Rules

Retrieval differs by surface

Answers are nondeterministic and vary by engine, location, and session. Judge trends over repeated runs, never a single screenshot.

Content that earns citations

• Non-commodity first. Google's guide separates commodity content ("based on common knowledge, which could originate from anyone") from content that "provides unique expert or experienced takes," and says "Don't just recycle what others on the internet have already said." Before drafting, name the gain: original data, a first-hand test with specifics, practitioner gotchas, real costs, or a synthesis nobody has published. If an LLM could rebuild the draft from the current top results, send it back to research.
• Answer first. Open each section with a one- or two-sentence direct answer to its heading, then evidence and nuance. Each passage must stand alone: no "as mentioned above," no pronouns pointing at earlier sections.
• Evidence density. In the GEO benchmark (Aggarwal et al., KDD 2024), adding cited sources, quotations, and statistics raised a source's visibility by up to about 40%, while keyword stuffing did not help. Use real, attributed numbers and quotes; never invent them to look citable.
• Cover the fan-out neighbourhood on one strong page: related questions, comparisons, constraints, edge cases, and alternatives. Don't publish a page per query variation; Google's guide says that can violate the scaled content abuse policy and "a high quantity of pages doesn't make a website higher quality."
• Natural structure, no artificial chunking. Google: "There's no requirement to break your content into tiny pieces." Use descriptive headings (question form where readers ask questions), lists and tables only for genuinely parallel items, and paragraph length that follows the topic.
• Experience and authorship. Name a real author with relevant credentials and a bio page. Show first-hand evidence: own screenshots, exact versions and settings, errors met, what failed. Stock heroes and "Admin" bylines add nothing.
• Real freshness. Update facts and dateModified when content changes; don't bump dates without changes.
• Comparison pages. Make each item self-contained (who it suits, key facts, price with an as-of date, limitations), disclose affiliations, and don't rank yourself first without evidence.

Structured data (2026 status)

• Not required for AI features: "Structured data isn't required for generative AI search." It still drives rich-result eligibility and entity disambiguation, and other engines may parse it.
• Use JSON-LD that matches visible content: Article/BlogPosting (headline, author as Person with url/sameAs, datePublished, dateModified), Organization (logo, sameAs), Product/Offer, BreadcrumbList.
• Google stopped showing FAQ rich results on 7 May 2026; HowTo rich results went in 2023. Keep a visible FAQ when it helps readers; leftover markup is harmless but no longer a Google lever.
• Review and AggregateRating markup about your own business on your own site is not eligible for review snippets. Mark up genuine third-party reviews only.

Spam-policy boundaries

• Scaled content abuse covers mass-produced or mass-rewritten pages, AI-assisted or not, and Google's guide applies it to attempts to manipulate generative AI responses.
• Site reputation abuse: third-party pages placed on a host to exploit its ranking signals violate policy even with first-party involvement (Google's November 2024 clarification). Pitch placements only where the topical fit is genuine.
• The helpful content system was folded into core ranking in March 2024; there is no separate update to wait out. Core updates (latest confirmed: 27 March to 8 April 2026) re-evaluate quality broadly. Don't quote ranking-shift percentages without a primary source.

Crawlers and controls

User-agent: OAI-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
User-agent: Bingbot
Allow: /

• Training crawlers are separate tokens: GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot. Blocking them is the owner's licensing choice and does not remove the site from search citations.
• User-initiated fetchers (ChatGPT-User, Perplexity-User, Claude-User) act for a person; OpenAI and Perplexity state robots.txt may not apply to them.
• Google's AI features use Googlebot. Limit display with nosnippet, data-nosnippet, or max-snippet; the Search Console "Search generative AI" control (all sites since 31 August 2026) removes a site from AI Overviews, AI Mode, and Discover AI features and is not a ranking signal elsewhere. Google-Extended limits training, not appearance.
• Serve key content in the initial HTML. Several AI crawlers don't execute JavaScript, so client-rendered text may be invisible to them.
• llms.txt: Google Search ignores it ("You don't need to create new machine readable files, AI text files, markup, or Markdown"). Keeping one for developer tools is harmless; don't promise visibility from it.

Measurement

• Google Search Console Generative AI performance report (June 2026): impressions in AI Overviews, AI Mode, and Discover by page, country, and device. Impressions only, and already counted in the Web totals.
• Bing Webmaster Tools AI Performance report (public preview February 2026): Copilot and Bing AI citations, cited pages, and grounding queries; no clicks.
• A fixed set of 10 to 20 niche prompts re-run monthly across engines, logging which page and passage got cited. Segment referral traffic from chatgpt.com, perplexity.ai, copilot.microsoft.com, and gemini.google.com. Treat vendor citation trackers as samples.

Agentic experiences

Google's guide flags agents that act for users (book, compare, buy). Browser agents read screenshots, the DOM, and the accessibility tree, so semantic HTML, labelled controls, and accessible forms matter. For commerce, track the Universal Commerce Protocol (UCP) as it matures. No new markup is required.

Examples

Answer-first section, wrong:

How long does a full reindex take? When we look at how indexing works, there are many factors at play. Researchers have studied this extensively...

Right:

How long does a full reindex take? On our 40 GB test index, a full reindex took 18 minutes on 8 vCPUs and 52 minutes on 2. Time scales roughly with document count; the settings that change it are below.

Fan-out coverage, wrong: separate pages for "reindex time", "how long reindex", and "reindex duration large index". Right: one page answering the time question first, then hardware scaling, partial reindex, zero-downtime swaps, and common failures, each under its own heading.

Checklist

• The page states a non-commodity gain (data, test, experience, synthesis) in the first screen.
• Every section opens with a standalone answer; no passage depends on an earlier one.
• Numbers and quotes are real, attributed, and dated; none invented for citability.
• Related sub-questions are covered on this page, not spun into near-duplicate pages.
• Named author with credentials and bio; first-hand evidence where the topic allows.
• JSON-LD matches visible content; no self-serving review markup; no claim that FAQ or HowTo markup earns Google features.
• Search crawlers allowed, key content in initial HTML, Bing submission done, Google generative AI control left on unless the owner opts out.
• Citation tracking set up (Search Console, Bing AI Performance, fixed prompt set) and judged over repeated runs.

References

Reviewed 2026-10-12.

• Google: optimizing for generative AI features and AI features and your website
• Google: Search generative AI control and generative AI performance reports
• Google spam policies and AI-generated content guidance
• OpenAI crawlers, Perplexity crawlers, Anthropic crawlers
• Aggarwal et al., GEO: Generative Engine Optimization (KDD 2024)
• Pew Research, AI summaries and clicks (2025)