Google made GEO “official”: what the docs actually say

In May 2026, Google published an official guide to optimizing for its generative AI features, and in June it updated its hiring guidance to name “GEO” and “AEO” services directly. ¹⁸ The industry read this as Google blessing GEO. The accurate read is the opposite of a blessing, and it is also not the neutral truth. Google’s guide is a primary source with an incentive. Hidden Layer’s job is to quote it exactly, then audit it the same way we audit any vendor: name the claim, name who benefits, and check it against independent evidence.

What Google actually said (verbatim)

These are direct quotes from the guide, not paraphrases. As of 2026-06-22 we verified them against the live Google Search Central page. ¹

• “From Google Search’s perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO.”
• “Structured data isn’t required for generative AI search, and there’s no special schema.org markup you need to add.”
• “You don’t need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search (including its generative AI capabilities), as Google Search itself doesn’t use them.”
• “There’s no requirement to break your content into tiny pieces for AI to better understand it,” and “you don’t need to write in a specific way just for generative AI search.”

In a June update, Google was blunter still about `llms.txt`: maintaining one “won’t harm (nor help) your visibility or rankings in Google Search, as Google Search ignores them.” ² So on Google’s own surfaces the verdict is settled. AI Overviews and AI Mode run on the core Search index, the fundamentals carry, and the AI-specific files and markup that an entire vendor category sells are not Google ranking levers.

Now read Google’s incentive

Quoting Google is necessary but not sufficient. The same impartiality we apply to “AI visibility” vendors applies to Google. “GEO is just SEO, and you don’t need new tools” is true on Google’s surfaces, and it is also exactly what Google would say whether or not it were the whole story. The framing keeps optimization inside Google’s walled garden, where Search Console, Google’s index, and Google’s first-party data are the only instruments. It delegitimizes third-party GEO tools: the guide states plainly that such tools “don’t have access to our internal ranking data” and that no vendor is “approved” by Google, which conveniently positions Search Console as the single source of truth. And the new “you can opt your content out of AI features” control satisfies regulators while making opt-out economically painful.

The claim audit

Here is the part most coverage skips: the popular GEO claims, checked against the largest independent datasets available. Status and confidence are ours; sources and incentives are named. Where a claim cannot be traced to a primary study, we mark it indeterminate rather than repeat it.

What changed, and what didn’t

What changed is the license to say no. Google’s guide gives teams explicit cover to stop buying AI files, special schema, chunking, and bulk LLM rewrites as Google ranking tactics. ¹ What did not change is the hard part. Crawlability, server-rendered content, accurate product data, entity clarity, and original evidence still decide whether you are eligible at all. Nor did the zero-click reality move: fewer than one in three U.S. Google searches still sends a click. ⁹ Eligibility is necessary; it has never been sufficient.

The split Google won’t draw for you

Google’s guide is scoped to Google Search and silent about everything else, and the rest of the agent web does not behave identically. A file irrelevant to Google can matter to a coding agent; product schema irrelevant to an AI Overview can be mandatory for a shopping agent. The correct question is never “does Google use this?” It is “which system are we optimizing, and what does that system actually need?”

What this means for your GEO budget

Move spend away from AI theater and toward durable systems. Highest value: bot access and crawlability, product-data completeness, original evidence-rich content, author and organization clarity, and platform-specific agent readiness. Lowest value: bulk-rewriting pages in an “AI tone,” generating llms.txt as a ranking play, or bolting on schema that does not match what the page actually shows. Mismatched schema is a data-quality liability, not a tactic.