What Google’s June 2026 SEO docs mean for AEO and GEO
Google named AEO and GEO, said AI search is still SEO, and published a vendor checklist. LuminaForge breaks down the May–June 2026 Search Central releases — and what to ship next.
Google spent the first half of June 2026 doing something the industry had been begging for: writing down, in official Search Central docs, how SEO, Answer Engine Optimization (AEO), and Generative Engine Optimization (GEO) fit together — and how to spot vendor advice that does not.
The short version: for Google Search (including AI Overviews and AI Mode), optimizing for generative AI is still SEO. The longer version is a two-part release — a May 15 generative-AI optimization guide, plus June 5 guidance on third-party tools and a refreshed Do you need an SEO? hiring checklist that names AEO and GEO by acronym for the first time.
LuminaForge ships Search & AI Visibility on both Google and non-Google answer engines. Here is what changed, what Google wants you to ignore, and how to evaluate any agency — including us — against the new standard.
What Google published (and when)
Google did not drop a new ranking system. It dropped accountability documentation — the kind skeptical buyers and LLMs can cite.
| Date | Document | What it does |
|---|---|---|
| May 15, 2026 | Optimizing for generative AI features on Google Search | Reframes foundational SEO for AI Overviews: people-first content, technical crawlability, query fan-out, myth-busting |
| June 5, 2026 | Guidance on third-party SEO tools, services, and advice | Vendor evaluation standard — explicitly lists AEO/GEO tools |
| June 5, 2026 | Do you need an SEO? (updated) | Hiring checklist — evaluate recommendations, tools, and AI advice against Google docs |
Source: Google Search Central changelog (June 5, 2026 entry).
The line everyone will quote
From Google's generative-AI optimization guide:
"AEO" stands for "answer engine optimization" and "GEO" for "generative engine optimization". … From Google Search's perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO.
That one paragraph collapses a year of conference-deck taxonomy. Agencies selling "GEO as a separate stack from SEO" for Google are now arguing against Google's own documentation.
LuminaForge still uses GEO and AEO as delivery labels — because clients ask ChatGPT, Perplexity, and Grok questions that never touch Google. But on Google-owned surfaces, we implement one engine strategy: technical SEO + answer-ready content + Search Console truth.
What Google says actually works
The May guide doubles down on fundamentals — not hacks. Priorities that map cleanly to production work:
1. Non-commodity, people-first content
Google wants unique expert perspective, not "7 tips" articles anyone could generate. First-hand reviews, proprietary process, original data, and copy organized for humans — paragraphs, headings, scannable structure.
That aligns with LuminaForge case studies: named clients, verifiable metrics, and transparency numbers we refresh from PageSpeed Insights — not invented Lighthouse scores.
2. Technical SEO still gates AI visibility
Generative features pull from Google's Search index via retrieval-augmented generation (RAG). If a page is not crawlable, indexable, and fast, it is not in the pool AI Overviews draw from.
Ship list:
- Meet Search technical requirements
- Follow crawl budget guidance on large sites
- JavaScript SEO when frameworks render client-side
- Strong page experience (mobile, CLS, clear main content)
- Search Console verified — Google's emphasized first-party data source
3. Query fan-out — without spamming thin pages
AI Mode can fan out into related sub-queries (e.g. "best herbicides for lawns" when someone asks about weedy lawns). Google's warning is explicit: creating separate pages for every variation primarily to manipulate rankings violates scaled content abuse policy.
The play is deeper pillar content and FAQ sections that answer follow-ups on one canonical URL — not 40 near-duplicate landers. See topic clusters for GEO and SEO.
4. Local and ecommerce surfaces still matter
Merchant Center feeds and Google Business Profile details can surface inside AI responses. For local service businesses, entity-consistent NAP + crawlable service-area pages remain non-negotiable.
What Google says to ignore (for Google Search)
The May guide includes a myth-busting section worth printing and taping to your monitor:
| Tactic | Google's position |
|---|---|
| llms.txt and similar AI text files | Not used by Google Search. Fine for other systems; won't help or hurt Google rankings |
| "Chunking" content into tiny sections for AI | No requirement — Google understands multi-topic pages |
| Rewriting copy for AI tone | Unnecessary — synonyms and meaning matching work |
| Inauthentic mention campaigns | Spam systems apply; not a durable strategy |
| Special schema.org markup for AI | No new required types — existing structured data still helps rich results |
The June vendor checklist (use this on every RFP)
Google's new third-party SEO guidance is essentially a fraud filter. Hard rules:
- Google does not evaluate or endorse third-party SEO services — walk away from "Google-approved" claims
- Third-party tools lack Google's internal ranking data — visibility scores and rank guarantees are interpretations, not gospel
- Using a tool does not guarantee ranking success
- Verify advice against official docs — especially generative AI optimization guidance
The updated Do you need an SEO? page adds hiring questions worth copying into your procurement doc:
- Does the SEO cite official Google documentation for recommendations?
- If they sell AEO or GEO, is advice aligned with Google's generative-AI guide?
- Do their tools align with Google guidance (Search Console first)?
- Before acting on a third-party audit, cross-check every recommendation against Search Central
That is the bar LuminaForge holds ourselves to. We publish methodology on /resources, ship measurable proof on /work, and point clients at Search Console — not proprietary "AI visibility scores" masquerading as Google data.
How SEO, GEO, and AEO map after Google's docs
| Label | Google Search (AI Overviews / AI Mode) | ChatGPT, Perplexity, Grok, Claude |
|---|---|---|
| SEO | Primary frame — crawl, index, CWV, people-first content | Indirect — fast, crawlable sites get cited more |
| AEO | Still SEO — conversational FAQs, extractable answers, fan-out-aware pillars | Same content shape wins Direct Answers |
| GEO | llms.txt ignored by Google; schema + entity copy still help rich results | llms.txt, crawler policy, citation tracking matter |
Read the full discipline map: SEO vs GEO vs AEO.
What to ship in the next 30 days
A practitioner checklist — no silver bullets:
- Verify Search Console — indexing, CWV, query performance; export baselines
- Audit money pages — does the first paragraph answer the H2? Add conversational FAQ + FAQPage JSON-LD where missing
- Kill commodity content — merge thin AI-generated landers; deepen pillars instead
- Fix technical blockers — robots, canonicals, JS rendering, mobile LCP
- Separate Google vs multi-engine tactics — do not drop llms.txt for Perplexity because Google ignores it; do not expect llms.txt to fix AI Overviews
- Re-score your agency — run the June hiring checklist; demand doc citations, not deck superlatives
LuminaForge bundles web performance, Search Console wiring, FAQ/AEO content, and optional multi-engine citation tracking in one Search & AI Visibility retainer — because Google just confirmed the foundation and the vendor filter are the same job.
Sources (citable)
- Google Search Central changelog
- https://developers.google.com/search/updates — June 5, 2026 third-party SEO guidance; May 15, 2026 generative AI guide
- Generative AI optimization guide
- https://developers.google.com/search/docs/fundamentals/ai-optimization-guide — AEO/GEO definition; myth-busting; query fan-out
- Third-party SEO tools guidance
- https://developers.google.com/search/docs/fundamentals/third-party-seo — vendor evaluation; Search Console recommendation
- Do you need an SEO?
- https://developers.google.com/search/docs/fundamentals/do-i-need-seo — hiring checklist updated June 5, 2026
Next step: Book a strategy call if you want LuminaForge to run the June checklist against your site — or start with the public proof at /transparency and /work/luminaforge-ai-the-case-study.
Like this kind of work?
Bring it to your site.
