Marketing · AI · May 2026 · ~6 min read
Sixty per cent of Google searches already end without a click, and AI chatbots (ChatGPT, Claude, Perplexity, Gemini, Copilot) absorb a growing share of informational queries each month. GEO — Generative Engine Optimization is the discipline that makes your content appear inside the answers those engines produce, not below them. This guide explains how to align your site with that new channel in 2026 without throwing away what already works in classic SEO: keep what works (E-E-A-T, schema, topical authority) and add what is new (llms.txt, citation-worthy passages, FAQPage, passage indexing, control of OpenAI, Anthropic and Perplexity crawlers).
What is GEO and why it matters in 2026
GEO — Generative Engine Optimization — is the practice of adjusting content, structured data and crawl permissions to maximize the probability that a generative engine (ChatGPT with web search, Claude with web search, Perplexity, Gemini, Copilot) cites your site in its answer. The term appeared in 2023-2024 with academic papers like GEO: Generative Engine Optimization (Aggarwal et al., Princeton) and became established in 2025-2026 as a professional category.
Pew Research measured in 2024 that 26% of US adults had used an AI chatbot to look up information, and SimilarWeb reported that ChatGPT reached 100 million monthly users in January 2023. OpenAI reported (Sam Altman, October 2025) that the platform had grown to more than 800 million weekly active users. When a user asks Claude "what is the AI Act" or Perplexity "best CRM for SMBs", the answer is a synthesis with citations — and only sites the LLM was allowed to read, judged authoritative and granted explicit permission to cite will appear.
LLM crawlers in 2026
Before optimizing, understand which bots exist. OpenAI publishes GPTBot (training), OAI-SearchBot (live search) and ChatGPT-User (on-demand fetch). Anthropic publishes ClaudeBot (training), Claude-Web and Claude-User (live fetch). Perplexity uses PerplexityBot and Perplexity-User. Google introduced Google-Extended to control use of content by Bard/Gemini without affecting traditional Googlebot. Microsoft Bingbot also serves Copilot.
The llms.txt standard
llms.txt is a proposal by Jeremy Howard (Answer.AI) published in September 2024 that standardizes a markdown file at the root of the domain to guide LLMs to canonical pages. It does not replace robots.txt or sitemap.xml: it complements them. The minimal anatomy includes a heading with the site name, a one-line description and a curated list of canonical URLs grouped by topic or vertical.
Schema and structured data for LLMs
LLMs with live search do not "reason" about HTML: they extract information via embedding and parsing. Schema.org remains the most reliable guide because it normalizes entities (Person, Organization, Article, FAQPage, Product, LocalBusiness) the LLM can map to its internal graph. Must-have types for a B2B consulting brand: Person with sameAs to LinkedIn, X, Crunchbase; Article with headline, datePublished, dateModified, author; FAQPage; BreadcrumbList; WebSite with SearchAction; SpeakableSpecification.
Passage indexing and citable content
Google's passage indexing (announced 2020, rolled out 2021) changed the unit of relevance: the engine can rank a specific passage within a long article, not only the URL as a whole. LLMs with search inherited this logic. The recipe for a citable passage: H2 as a natural question, first paragraph as direct answer (40-80 words), figure with source citation, stable anchor and visible caveats.
FAQPage and zero-click answers
The FAQ block at the end of the article is not decoration: it is the most cited format by generative engines because it already comes in normalized question-answer format. Rules: 5-7 questions max, real questions not marketing, 60-100 word answers with figure or date when possible, FAQPage schema with mainEntity array of Question with acceptedAnswer.text, and matching the body content as H2 questions.
How to measure visibility in generative engines
Google Search Console does not measure appearance in ChatGPT, Claude or Perplexity. Available metrics in 2026: referrer traffic in GA4 filtered by chatgpt.com, perplexity.ai, claude.ai, copilot.microsoft.com, gemini.google.com; brand monitoring platforms (Profound, Otterly, Peec.ai, AthenaHQ, Goodie AI, Daydream); manual mention tracking (run 20 representative prompts monthly); and server logs filtered by user agent.
Frequently asked questions
What is the difference between SEO and GEO?
SEO optimizes to appear in SERPs (10 blue links). GEO optimizes to appear inside the synthetic answers generated by ChatGPT, Claude, Perplexity, Gemini or Copilot. The key difference is the unit of relevance: SEO works with full URLs, GEO works with citable passages.
Does blocking GPTBot or ClaudeBot hurt my SEO?
Not directly. Blocking OpenAI's GPTBot or Anthropic's ClaudeBot training bots does not affect Googlebot or Bingbot. But if you also block live-search crawlers (OAI-SearchBot, Claude-Web, PerplexityBot) you give up appearing in those engines' answers.
Is llms.txt mandatory or just a best practice?
Not mandatory. llms.txt is an open proposal (Answer.AI, 2024) that no LLM requires today. But several technical platforms (Anthropic, Vercel, Cursor, Stripe) already publish it because it improves the quality of the answers LLMs give about their products.
How do I know if ChatGPT or Claude are citing my site?
Two ways. Manual: run 15-20 representative prompts from your sector and check if your domain appears in the citations. Tool: platforms like Profound, Otterly, Peec.ai or AthenaHQ automate thousands of monthly prompts and detect your share of voice. Complement with GA4 filtering referrer chatgpt.com and perplexity.ai.
How long does it take for LLM optimization to show impact?
Much less than SEO. Live-search LLMs (ChatGPT Search, Claude with web search, Perplexity) refresh their context in hours to days every time a user runs a new query. Publishing an article with FAQPage, schema and citable passages on Monday can translate into citations on Tuesday or Wednesday.
Is it worth publishing content specifically for LLMs?
Only if it also works for humans. Creating synthetic FAQs and long lists of definitions "for the LLM to cite" is going back to early-2000s keyword stuffing. Write for a curious professional reader, add schema and citable passages as a technical layer, and let the LLM choose.
What mistakes should I avoid when doing GEO in 2026?
Five recurring antipatterns. (1) Blocking all LLM bots "just in case" and disappearing from the channel. (2) Publishing llms.txt with thousands of URLs as noise. (3) Hardcoding FAQPage with invented questions. (4) Forgetting the dateModified — LLMs discount content without visible freshness. (5) Citing other sources without verifying them.