Yes, generative AI is indexing standard WordPress sites. AI crawlers read public pages much as search crawlers do, from the rendered HTML, so any normal WordPress site can be picked up. The more useful question is whether your pages get cited once they are read, because that is where a standard WordPress install often falls short. A slow, plugin-heavy page is read incompletely and quoted rarely, while a fast, clean, well-structured site gets lifted into answers. WPBuildAI rebuilds WordPress as a fast, semantic site so generative engines can read every page and cite it.

They are indexing them heavily, though mostly for training rather than to send anyone over: Cloudflare found training accounts for roughly 80 percent of AI crawler activity while user-action fetches sit under 5 percent, which is why crawl volume and referral traffic tell such different stories.

Indexed is not the same as cited

Being crawled is the low bar; being chosen as the source for an answer is the real goal, and the two are easy to conflate. Your page can be perfectly indexed, sitting in the engine’s store of known pages, and still never appear in an answer, because when the engine composes a response it picks the sources that are easiest to extract a clear, attributable fact from. The Generative Engine Optimization study measured what generative engines actually quote and found they favour content that is clearly structured, fact-dense, and easy to attribute. A page that buries its answer in theme markup gives the engine little to lift, so it gets indexed and then passed over. That gap, read but not quoted, is where most WordPress sites lose, and it is the gap worth closing.

How AI crawlers read a WordPress site

It helps to know the mechanics, because they explain what to fix. An AI crawler requests your public URL and works with what comes back, the rendered HTML, the headings, the text, the structured data. It does not log into your admin or read your database; it reads the page as a visitor’s browser would receive it. Google’s guidance on AI features confirms that the same crawling and indexing that powers search underpins its AI experiences, so the fundamentals carry over: if a search crawler can read your page well, so can an AI one. This is reassuring, because it means there is no separate, mysterious “AI SEO”, just a page that is genuinely easy for an automated reader to parse, which is the same thing good technical SEO has always meant.

Why it increasingly matters

The citation is becoming the destination, not just a bonus. Ahrefs analysed how AI Overviews change click behaviour and found clicks drop when an AI summary appears, which means being the cited source is increasingly how you stay visible at all. If your page is not quotable, the engine quotes someone else, and you get neither the citation nor the click that used to come from ranking. As more queries are answered by an AI layer above the links, the pages that get cited inherit the visibility that organic results used to capture, and the pages that do not fade from view even when they are technically indexed. The same dynamic applies across AI search citations and Google AI Overviews traffic. Being readable and quotable is no longer optional polish; it is how you remain present in AI-mediated search.

What makes a WordPress site AI-readable

A handful of properties decide whether an AI engine reads your page fully and finds it quotable:

  • Speed and clean rendering, so the content is present and complete when the crawler reads it. Google explains in its JavaScript SEO basics why script-heavy pages render poorly for automated readers.
  • Clear headings and structure, so the answer to a question is obvious and extractable rather than buried.
  • Schema, so the entities and facts on the page are explicitly labelled.
  • Allowed AI crawlers in robots.txt, plus an llms.txt pointing to your clean content.

A heavy theme undercuts the first two especially, which is why a rebuild often does more for AI visibility than any plugin. These foundations are the same as in what generative engine optimization is.

A worked example: two pages, one cited

Picture two WordPress pages answering the same question, “how long does a site migration take.” The first is on a heavy theme: the answer is real but wrapped in nested markup, the page loads slowly, and a chunk of content renders only after scripts run. The second is lean: the answer leads the page in a clear sentence under a plain heading, with schema marking it up, and it loads fast. Both get indexed. But when an AI engine composes an answer, it lifts a clean, attributable sentence from the second page and cites it, because that page made the fact easy to extract, while the first page offered nothing clean to quote. Same question, same correct answer, only one cited. The difference was entirely readability and structure, which is exactly what separates “indexed” from “quoted” and what a rebuild fixes.

Where heavy WordPress falls short

A standard, plugin-heavy WordPress install tends to fail precisely on the traits that win citations. The accumulated themes and plugins slow the response and inflate the markup, so the crawler reads the page more slowly and less completely. Content that loads via script may be missed by a lightweight fetch. The answer to a query is often buried several sections down, under stacked widgets, rather than stated cleanly near the top. And schema is frequently absent or inconsistent. None of this stops indexing, but all of it lowers the odds of being quoted, because the engine has to work harder to find a clean fact and often gives up in favour of an easier source. This is why the fix is structural, not a setting: the weight itself is the problem, and removing it is what makes the page both faster and more quotable.

Should you block AI crawlers?

The opposite question comes up too: can you stop AI from using your content? You can disallow specific AI crawlers in robots.txt, and for a narrow set of content you never want summarised that may be right. For most businesses it backfires, because blocking removes you from AI answers entirely while your competitors stay in them, so you forfeit the citation and any referral it carries. The AI answer still appears for the query; it simply draws on someone else. Unless you have a clear reason to opt out, being readable and cited is the stronger position than being absent. The defensible default for a business that wants to be found is to allow the AI crawlers you care about and make your pages easy to quote, not to hide from them. WPBuildAI sets a clean crawler policy during a rebuild so the engines you want can read your pages.

Common mistakes with AI indexing

The recurring errors come from misunderstanding what AI indexing rewards. Assuming “indexed” means “done” ignores that citation, not indexing, is the goal, so the page is read and never quoted. Treating AI visibility as a separate strategy from technical SEO leads people to chase gimmicks instead of fixing speed and structure, which is what actually helps. Burying the answer deep in a page, under widgets and preamble, leaves nothing clean to lift. Skipping schema gives the engine no labelled facts. And blocking AI crawlers reflexively removes you from answers while competitors remain. Each is avoided by the same move: make the page fast, clean, clearly structured with the answer up front, marked up with schema, and open to the crawlers you want, which turns “indexed” into “cited.”

Key points to remember

Generative AI does index standard public WordPress sites, reading the rendered HTML the way search crawlers do, but indexing is not citation, and a citation is increasingly where the visibility lives as AI answers absorb clicks. The pages that get quoted are fast, cleanly rendered, clearly structured with the answer near the top, and marked up with schema, while heavy, plugin-laden WordPress pages get read incompletely and passed over. Allow the AI crawlers you care about rather than blocking yourself out of answers, and fix the speed and structure that decide quotability rather than chasing a separate “AI strategy.” WPBuildAI rebuilds WordPress as a fast, semantic site so AI engines can read every page and quote you instead of a competitor; send your site URL for a fixed quote.

Not affiliated with Google, OpenAI, WordPress, or Lovable.