On May 15, 2026, Google published its first official guide for optimizing websites for generative AI features in Search — AI Overviews, AI Mode, and whatever comes next. Within days, half the SEO industry had written a “here’s what it means” post. I read the guide myself, and I read through what other sites said about it. Many early articles focused mainly on explaining concepts like retrieval-augmented generation (RAG) and query fan-out. Those are useful to understand, but as a WordPress site owner I was more interested in what, if anything, I actually needed to change.
I run WordPress sites for a living, including my own, and I work on enterprise WordPress sites professionally. So instead of another summary, here’s what I actually changed — or didn’t change — on real WordPress sites after reading it, plus the five things Google explicitly told us to stop worrying about.
Is SEO still relevant for AI search? Yes, and here’s why that matters for WordPress specifically
Google’s generative AI features run on the same core ranking and quality systems as regular Search. If a page isn’t indexed and eligible to show a snippet, it can’t be retrieved by the AI system and it can’t be cited. That single sentence should end most of the “AI SEO is a new discipline” debate. For WordPress site owners, it means your indexing hygiene — the boring GSC Coverage Report checks, the crawl budget audits, the redirect cleanup — is still the foundation everything else sits on.
10 things to actually do
1. Write from first-hand experience, not a summary of what’s already out there
Google draws a clear line between commodity content (something anyone, including an AI model, could produce) and non-commodity content (something only you could write because you actually did the thing). On my own site, this is why my About Me page exists — not for a ranking trick, but because 16+ years of client history is not something a generic AI summary can replicate.
Include information AI can’t invent
Instead of repeating documentation, include things like:
- screenshots from your own site
- performance numbers
- mistakes you made
- before-and-after examples
- test results
2. Fix your indexing status before anything else
A page that isn’t indexed can’t appear in an AI Overview. Before touching content strategy, check your GSC Coverage Report and clear anything flagged as a crawl error or sitting in “Discovered – currently not indexed.”
Of course, indexing alone doesn’t guarantee an AI Overview citation. It simply makes a page eligible to be considered.
I’ve broken down what every GSC indexing status actually means, and separately what to do when a specific page won’t index.
3. Audit your crawl budget on large or frequently updated sites
This is the one most WordPress developers skip because it feels invisible. On one client site, over 36,000 low-value tag pages were quietly consuming crawl activity that should have gone to actual content. Removing them resolved the crawl budget issue. It’s the kind of problem that never shows up unless you go looking for it — I cover the full diagnostic process in my crawl budget guide.
4. Use semantic HTML for readability, not perfection
Google is explicit that your HTML doesn’t need to be flawless. It needs to be readable — proper heading hierarchy, paragraphs that make sense on their own, structure a screen reader or a browser agent can parse without guessing. This is also just good practice for the Classic Editor workflow if you’re pasting plain HTML instead of relying on a page builder’s div soup.
5. Add real images and video where they add value
Nothing new here if you’re already following standard image and video SEO practices. If you publish video content, make sure discovery and understanding are both covered — I’ve written about why a video sitemap and VideoObject schema aren’t interchangeable, and you typically need both.
6. Keep JavaScript from blocking your content
If your theme or page builder renders key content client-side, make sure Google can actually see it. Divi handles most of this reasonably well out of the box, but always worth checking with the URL Inspection tool if you’re layering custom JS on top.
7. Protect page experience and Core Web Vitals
Slow, janky pages hurt regular rankings and by extension hurt AI visibility, since AI features draw from the same index. If you’re on Divi with WP Rocket or LiteSpeed Cache, I’ve laid out the full approach in my Core Web Vitals for WordPress guide.
8. Clean up duplicate content and redirect chains
Duplicate or near-duplicate pages waste crawl budget and confuse which URL should be the canonical source. Redirect chains and loops are the most common WordPress-specific version of this problem — here’s how to find and fix them.
9. Get your local and ecommerce data structured properly
If a client site sells products or serves a local area, Merchant Center feeds and Google Business Profiles feed directly into what generative AI responses can surface — product info, availability, business details. If local or ecommerce visibility is important, keeping Merchant Center and Google Business Profile information accurate is becoming increasingly important.
10. Keep an eye on agentic experiences, even if you don’t act yet
Google’s guide flags browser agents that read a page’s DOM structure and accessibility tree to complete tasks on a user’s behalf, plus emerging protocols like the Universal Commerce Protocol. Nothing urgent to build today for most WordPress sites, but clean semantic HTML (see #4) is the same groundwork that makes a site agent-friendly later.
5 things Google says you can ignore
1. llms.txt and other special AI files
Google Search does not use these and does not give sites that have them any special treatment. If you want one for other AI systems that do reference them, it won’t hurt you on Google — it just won’t help either.
2. Chunking your content into tiny fragments
I’ve seen clients get talked into breaking a solid, complete article into a dozen thin sections because someone told them “AI likes small chunks.” Google’s systems handle multi-topic pages fine and extract the relevant piece on their own. Write for your actual reader’s length, not an imagined chunking algorithm.
3. Rewriting content specifically for AI parsing
You don’t need a separate “AI-friendly” version of your content or extra long-tail keyword variations bolted on. Synonym and intent understanding is handled on Google’s end.
4. Chasing inauthentic brand mentions
Buying placements or seeding forum mentions to manufacture “authority signals” runs into the same spam systems that already police the rest of Search. It’s not a shortcut, and it can backfire.
5. Overinvesting in structured data as an “AI requirement”
Structured data is still worth doing for rich results eligibility — I still build FAQ schema into my how-to and reference posts — but Google hasn’t introduced any structured data type specifically for AI Overviews. Don’t let a client believe schema alone is the fix if the underlying content or crawlability is the real problem.
The bottom line
Nothing in this guide asks WordPress site owners to tear up their existing SEO checklist. It confirms the checklist was right the whole time: indexing hygiene, real crawl budget management, content that reflects genuine experience, and clean semantic HTML. The acronyms changed. The work didn’t.
