Google's May 2026 AI Optimization Guide: what actually changed for site owners

Google's May 15, 2026 AI optimization guide changed almost nothing about how you should write, and exactly one thing about what you can control: it confirmed that AI Overviews and AI Mode run on Google's existing core ranking systems, so no llms.txt file, content chunking, AI-specific rewrite or special schema is needed to appear in them — and three weeks later, on June 3, Google added a Search Console switch to opt out of those features entirely. The sentence worth reading twice is the "you don't need it" list, because it describes what Google's own AI surfaces require, not what ChatGPT, Perplexity or Claude do when they build their own indexes.

That distinction is why we didn't change a line of Contexta, our WordPress plugin, when the guide landed — even though two of its features, an llms.txt generator and an answer-first editor, are on Google's list of things you supposedly don't need. It isn't a contradiction. Google is describing what its features want, and Google's features are only one of the places your pages get read. "Google doesn't need it" and "nobody needs it" are different claims, and most of the coverage collapsed them into one.

What actually changed for site owners in Google's May 2026 guide?

Very little about how you write, and two concrete things about what you do. The guide mostly consolidated scattered advice into a single document at developers.google.com/search/docs/fundamentals/ai-optimization-guide and restated a position Google has held for a while: appearing in generative AI features is the same job as ranking in Search. What is genuinely new is a named list of tactics Google now calls unnecessary for its features, and — added in a follow-up on June 3 — a control and a data source that didn't exist before.

1. May 15, 2026

   Google publishes the generative-AI optimization guide; consolidates guidance and calls AEO/GEO "still SEO"

2. May 21, 2026

   Second core update of 2026 begins its global rollout

3. Jun 3, 2026

   Search Console adds a control to opt out of AI Overviews, AI Mode & AI Overviews in Discover — plus new generative-AI impression data

So if you were waiting for a new checklist of AI-specific tasks, the honest read is that Google told you the opposite: keep doing fundamentals, stop doing several things the "GEO" market has been selling. The parts that reward action are the two dated items above, not the reassurance in between.

Does Google really say to skip llms.txt and content chunking?

Yes — the guide states plainly that you don't need machine-readable files, AI text files or Markdown to appear in Google Search, and that you don't need to break content into small pieces because, in its words, Google's systems "understand the nuance of multiple topics on a page." It also says there's no special schema.org markup for generative AI and that chasing inauthentic "mentions" across the web helps less than it looks.

Every one of those statements is true for Google, and we'd tell you the same. The trap is treating them as universal. An llms.txt file is worthless for AI Overviews, but it exists for a different reason — some assistants and crawlers that don't use Google's index do fetch it — so "Google ignores it" settles the Google question and none of the others. The same goes for chunking: Google splits your page into passages server-side, which is why it tells you not to bother, but a retrieval assistant fetching your live URL is at the mercy of the shape you actually published.

So is optimizing for AI just SEO now?

For Google Search, yes — Google's exact framing is that its generative AI features are "rooted in our core Search ranking and quality systems," so from its perspective AEO and GEO are, quoting the guide, "still SEO." A page has to be indexed, eligible for a snippet, crawlable, and built as helpful people-first content; get those right and you're already eligible for AI Overviews and AI Mode with nothing extra to add.

Where this gets oversimplified is the leap from "still SEO for Google" to "still SEO, full stop." The difference between GEO and SEO writing was never mainly about Google — it's about the fact that an answer engine lifts a self-contained passage instead of ranking a page, and that's true whether the engine is Google's or OpenAI's. Google can afford to say "just write well" because its own systems do the passage-splitting for you. An assistant that fetches your page and reads it as-is can't do you that favor, so the writing shape still matters off Google's surfaces even when it's optional on them.

Why does the guide say nothing about ChatGPT or Perplexity?

Because Google's guide only describes Google's products — and ChatGPT, Perplexity and Claude don't run on Google's index. They crawl with their own bots (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot) and answer from their own retrieval, so the guide's reassurances about crawlability quietly assume Googlebot's access, which is a different question from whether an OpenAI or Perplexity bot can reach you at all.

Google AI Overviews & AI Mode

• Reaches you through Googlebot's existing access
• Splits your page into passages server-side, so you needn't
• Ignores llms.txt, AI-only schema and AI-written-for rewrites
• Needs indexed, snippet-eligible, people-first pages

vs

ChatGPT · Perplexity · Claude

• Reach you only if GPTBot / OAI-SearchBot can fetch the page
• Lift your live passages as published, so their shape still counts
• Some do fetch llms.txt; none of that is Google's concern
• Rewarded by the same self-contained, answer-first writing

That reachability line is the one Google's guide can't answer for you, because Google isn't crawling on OpenAI's behalf. A page Googlebot renders perfectly can be invisible to GPTBot if your robots.txt blocks it, your CDN challenges it, or the content only appears after JavaScript runs — and JavaScript-rendered content that assistants never see is one of the most common ways a page passes Google's bar and fails everywhere else. Contexta's AI Visibility check exists for exactly this blind spot: it fetches your pages as each named AI bot, flags a robots.txt or Cloudflare block, and tests whether your content is present without JavaScript. None of that is in Google's guide, and it wouldn't be — it's the part of the map Google doesn't cover.

What is the June 2026 opt-out control, and should you use it?

On June 3, 2026 Google added a Search Console control that lets you decide whether your site appears in and helps ground its generative AI features — AI Overviews, AI Mode and AI Overviews in Discover — and for almost every site the answer is to leave it on, because opting out forfeits all traffic and impressions from those features while doing nothing for your ordinary rankings. Google was explicit that the setting isn't used as a ranking signal outside the generative features, so opting out is purely a "do I want this exposure" decision, not a lever on classic Search.

The more useful half of that update is the data arriving alongside it. Search Console is rolling out impressions from generative AI features, which of your pages show up in AI responses, and country-level breakdowns — the first time Google has reported AI-feature performance in Search Console rather than folding it invisibly into totals. Testing started with a subset of UK site owners before wider rollout, so if you don't see it yet, that's why. When it reaches your property, that report — not the opt-out toggle — is the thing to check weekly.

What should you actually do after reading the guide?

Three things, and none of them is a rewrite. First, do nothing to your content on Google's account — the guide's clearest message is that fundamentals already cover AI Overviews and AI Mode, so don't buy an "AEO package" that promises otherwise. Second, treat the June 3 opt-out as a deliberate choice and, unless you have a specific reason to disappear from AI answers, leave it enabled and start watching the new generative-AI impressions the moment they appear on your property.

Third — and this is the part the guide doesn't reach — verify that the assistants Google doesn't speak for can actually read you. Confirm GPTBot, OAI-SearchBot and PerplexityBot aren't blocked, check that your key pages render their content without JavaScript, and keep your important answers self-contained enough to survive being lifted out of context. Google told you those things are optional for its own features, and for its features they are. For everywhere else your buyers now ask questions, they're still the difference between being quoted and being skipped.