Your website will not update itself for AI search. Nothing changes on a normal WordPress site the day your customers start asking ChatGPT, Perplexity, or Google’s AI answers instead of typing a keyword into a search box. If nobody has deliberately rewritten the site so an assistant can read it, those assistants are answering questions about your category and naming other businesses. Discovery moved. The site stayed exactly where it was.
This is not a ranking dip you can wait out. It is a maintenance problem, and nobody’s job description says “keep the site readable to AI.” What follows is why this happened, why a site cannot fix itself, what “updated for AI” actually means, what it costs to wait, and how to start this week.
The short version: assistants now answer the question directly and name two or three businesses. A default site ships almost none of the machine-readable facts an assistant needs to trust it. Even the tools that promise to do this automatically fail quietly. So this is work you do on purpose, not something that happens to you.
How People Find a Business Changed
For twenty years discovery worked one way. You ranked, the customer clicked, and the visit was yours. The assistant model breaks that chain. The customer asks a question, and the assistant answers it, citing a short list of sources. Your job is no longer to win a click. It is to be one of the few sources worth naming.
Look at the difference in stages. A year ago the path was: search, scan ten blue links, compare, decide. Today a growing share of that path collapses into one step. The customer asks an AI assistant, reads a synthesized answer, and often never opens a website at all. The assistant did the comparison. You were either in the answer or you were not.
This is not theoretical, and it is already measurable. On a live WooCommerce store we manage, Google Analytics 4 shows chatgpt.com as the fourth largest traffic source over the past 180 days, ahead of Bing and several directories. Roughly 1,080 sessions arrived from AI tools in that window: chatgpt.com (around 765), Gemini (31), Perplexity (29), Claude (14), and Copilot (9).
Read that as a business owner, not a marketer. Those are not curious visitors testing a chatbot. Those are people asking a buying question and being handed an answer. In the old world a competitor outspending you on ads could still lose to a better page. In this world, if your site is not readable and quotable, you are simply not in the answer at all.
Why Your Website Does Not Fix Itself
A website has no opinion about the future. It renders exactly what it was built with, and most sites were built for a world where a human clicked a blue link. A default WordPress install ships almost none of what an assistant needs to trust and repeat your facts. There is no switch that flips the moment AI search becomes important.
That gap would be easy to close if the tools that promise to close it worked. Mostly they do not, and they fail silently, which is worse than failing loudly.
Here is a real example. We enabled the llms.txt feature in Yoast SEO v28.3 on a live store we manage. The file went live and returned a 200, so every dashboard light was green. Then we actually read it. 22 of the 41 entries had empty URLs, written as empty link markup, and every Pages entry and every Product entry was blank. The only working links pointed at category and tag archives. The file also leaked internal template entries, some with live typos, and it carried no shipping, returns, or contact facts at all.
On our own site, which also runs Yoast, the promised file returns a 404. The automatic feature did not even fire.
That is the pattern worth internalizing. The plugin gave us the plumbing, not the judgment, and when it produced junk, nothing broke and nobody was alerted. Silence is the default failure mode here. You do not get an error message when you become invisible. We documented the full audit in Yoast llms.txt: why it is not the best way to do AI discovery.
The same story repeats across the categories. A plugin can generate a sitemap, a schema bundle, or an AI file. None of them can decide which pages matter, which facts are true, or whether the output is even correct. That decision is the job. No tool has taken it off your plate.
What “Updated for AI” Actually Means
Assistants do not read vibes. They read and repeat machine-readable facts. An AI-ready site is not a redesign and it is not a rewrite of your marketing copy. It is a specific, unglamorous set of additions, and most of them take minutes rather than weeks.
- Crawler access. Your robots.txt must allow the assistants you want to be found by. If they cannot read you, nothing else matters.
- Structured data. Organization with sameAs and contactPoint, Product with price, availability, and policy links, FAQPage on the pages that answer questions, LocalBusiness if you serve an area, and Article on posts.
- A curated llms.txt. A short file with real links, one line about the business, and the core facts. Not an automatic dump of every URL on the site.
- Clean factual content. Shipping, returns, hours, prices, service area, and guarantees stated plainly on real pages, not buried in a PDF, an image, or a widget.
- Freshness signals. Updated dates, working contact details, and pages that clearly belong to a business that is still trading.
A default site ships almost none of this. That is the whole reason a business can be online, healthy, and completely absent from the answers its own customers are reading. If you want the writing side of the same problem, the companion read is how to get your WordPress site found by AI search. That post covers making pages quotable. This one covers the plumbing underneath.
What It Costs to Wait
The cost of waiting is not a ranking drop you can watch in a dashboard next month. It is absence from an answer you never see. When an assistant answers “who should I use for this,” it names two or three businesses. If your competitor’s site carries clean schema and plain-text policies and yours does not, the assistant quotes the competitor. Your site is not penalized. It is not cited, which looks the same as not existing.
Two things make waiting expensive. First, assistants pull fresh facts from the open web, so whatever is machine-readable about you tends to win, even when it is outdated or flattering to someone else. Second, you cannot see the traffic you never got. There is no report for the customers who asked, received a competitor’s name, and never knew you were an option.
There is also a first-mover effect. Getting structured data and clear facts in place is a one-time chore. Doing it after competitors already own the answers in your category means fighting uphill against sources an assistant has already learned to trust.
How to Start This Week
Think in three gates. Each one is a short, deliberate task, and each one unlocks the next. You can finish all three inside a single working day.
Gate 1: Crawler access (about 15 minutes)
Open your robots.txt and decide, on purpose, which AI crawlers may read your site and which must not. Being blocked is often the quiet reason a site is missing from AI answers. Our walkthrough is how to update your robots.txt for AI crawlers. If Cloudflare sits in front of your site, its default AI bot rules can block crawlers too, which is covered in Cloudflare is blocking AI crawlers.
Gate 2: Structured data (an afternoon)
Add Organization with sameAs and contactPoint, Product with price and policy links, and FAQPage where it fits. Use the schema your theme or SEO plugin already supports, then validate the output on a live page rather than trusting a settings toggle. This is what turns your facts from text an assistant has to guess at into facts it can repeat verbatim.
Gate 3: A curated llms.txt and your core facts (about an hour)
Write the short file by hand, or generate a clean starting point with the free llms.txt generator. Keep it to the pages that matter, one line each, plus shipping, returns, contact, currency, and service area. Then put a recurring reminder on the calendar, because facts drift and a stale file is its own kind of invisible.
The Honest Caveat
llms.txt is still an emerging convention. No major assistant has publicly committed to reading it, and it is not a Google ranking factor. Treat it as the cherry on top, not the foundation. Do the fundamentals first: crawler access, structured data, and clear factual content. Those are the parts that pay today. Skip the fundamentals to chase a file that may or may not be read, and you have optimized the garnish.
The Point
AI optimization is work you do, not something that happens automatically. Nothing on your site changes when discovery shifts. You either sit down and make the site readable to the assistants your customers now ask, or you leave that job to whoever your competitor hired. The tools will not do it for you, and most of them will not even tell you when they fail.
Start with the gate that unblocks everything else: crawler access
If AI crawlers cannot read your site, no amount of schema or good writing will get you into the answer. Our plain-English guide walks through exactly what to allow and what to block in robots.txt, and why the defaults can quietly hide you from the assistants your customers now use.
About The Author
