How to implement AEO in WordPress, and where it breaks

Plugins are the easy part. Keeping every fix alive after the next update is the work.

WordPress can carry AEO. Six changes do most of the work: answer-first blocks, FAQ and Article schema, llms.txt, robots rules for AI bots, internal links and page speed.

The trouble is never the install. In a June 2026 thread on r/SEOorganic, one practitioner who said they had tested most WordPress plugins put it flatly: "the AI features are mostly marketing right now." Another commenter in the same thread gave plugins their due, "A plugin that injects good schema gets you most of the way; the rest is how the page is written," and then warned that a heavy page-builder theme makes schema injection matter more.

Both are right. That is the trade-off I keep weighing. A plugin is cheap and fast, and it covers the markup. Webolutions, an agency that sells this work, frames why: "AI engines are not simply indexers; they are interpreters," so the words on the page carry more weight than the markup around them.

So this is an honest list. Each step gets its WordPress route, then the exact point where it breaks. The last part prices what it takes to keep all six working, against moving once.

What does each AEO step look like inside WordPress?

Every one of the six AEO steps has a WordPress route: an editor habit, a plugin setting or a theme file edit. None of them needs custom code on day one.

1. Answer-first blocks: open each question heading in the block editor with a short paragraph that answers it outright.
2. FAQ and Article schema: let one SEO plugin, usually Rank Math or Yoast, write the JSON-LD.
3. llms.txt: switch on the plugin's generator, or upload a hand-written file to the site root.
4. Robots rules for AI bots: use the plugin's file editor so robots.txt allows GPTBot and Google-Extended.
5. Internal links: connect question pages to each other by hand, with anchors that say what the reader gets.
6. Page speed: trim the theme and add a caching plugin.

Start with what the word means. On Lenny Rachitsky's podcast in 2025, the episode description defined AEO as "getting your product to show up in ChatGPT/Claude/Gemini/Perplexity answers." His guest, Ethan Smith of Graphite, named three tactics that worked: landing pages, YouTube videos, and Reddit comments. Only one of those lives inside WordPress.

So the WordPress job is narrower than the hype. It is the landing page, made readable.

The plugin layer covers more of that job than people expect. Rank Math auto-generates JSON-LD for Organization, FAQ and HowTo schema. One AEO plugin in the WordPress directory says it builds Article and FAQ schema on its own and recommends a summary of 300-500 characters at the top of each post, though that is the vendor's own guidance, not a tested benchmark. Strategy guides from agencies add clear definitions and FAQ structures that support retrieval.

A June 2026 thread on r/WordPress went further. Commenters there listed internal linking, FAQ schema, author expertise and fast, crawlable pages as the factors that matter, and noted that Rank Math now builds llms.txt from existing meta descriptions. An analysis of 5 sources, from a podcast to plugin documentation to two practitioner threads, points one way. Before you touch any of it, list the questions buyers actually ask; Dheeraj Sharma, who sells AI content agents, found an LLM alone "hallucinates search volumes and guesses at competition levels."

The common assumption is that installing the right plugin means you are doing AEO. It does not. A plugin writes markup around whatever the page already says. If the page buries its answer, the markup describes a buried answer.

I keep coming back to that. A plugin can't write a sharper first sentence for you, and the first sentence is usually what gets lifted. For the definitions behind each term, our AEO FAQ on AI search optimization goes deeper than this walk-through can.

AEO Content has run 26,577 real AI-visibility audits, and I'd rather a reader take that number as a caution than a boast. A checklist is cheap to write down. Keeping all six items true after the next theme update, the next plugin release and the next cache purge is the part that costs money, and that is where WordPress starts to give way.

Where does each AEO step break on WordPress?

Each step fails at a seam between tools. We have scored 11,000+ domains across 15 sectors and 28 categories, and a score only shows the seam on the day you look.

The first row is the quiet killer. In August 2026, Andreas Lehner described on Substack how a small business rebuilt its page with menus that loaded content through JavaScript after a click. To a crawler, he wrote, the new site was "close to an empty shell." The service descriptions, the pricing and the FAQ all sat behind clicks a crawler never makes. Many WordPress page builders ship the same pattern by default.

Schema fails louder but less visibly. Two SEO plugins, or one plugin and a theme with its own markup, can each describe the same page. Nobody notices until a validator does.

Then come updates. An edit made straight in a theme file is gone the next time the theme updates. A caching plugin keeps serving last week's HTML after you fix the answer block. Robots rules live in more than one place, and the last writer wins.

Lehner put the root problem plainly: a WordPress site depends on WordPress itself, plus its plugins and database, staying patched indefinitely, "which is exactly where small business sites quietly rot: nobody's job to keep maintaining it." He also found that a hosted WordPress install kept no real history of changes. What is live is the only copy.

Practitioners are blunt about where that leaves plugins. In a December 2025 thread on r/AISEOforBeginners, two commenters said they had not seen a WordPress plugin that meaningfully does AEO, and one summed it up: "The judgment layer is still human."

I agree with that line, and I'd extend it. So ask your developer one plain question for each row of the table: what undoes this fix, and who notices when it happens? AEO Content's team includes a full-stack engineer and content infrastructure architect with 20 years of building enterprise systems, and even with that depth, a stack of plugins that each own one piece of the page is fragile by design.

The research section below walks through how that plays out after install. Most owners don't have that person. Some fix it on a schedule; others decide to move your site to an AEO website and stop patching seams, and the difference between those choices shows up first on the invoice.

What does it cost to keep WordPress AEO working versus moving once?

Patching WordPress is a monthly bill; moving is a single one. After the move, one client went from a quiet site to 10 booked calls in 3 weeks.

Price both sides honestly. The old stack, as priced on our AEO website page, runs $3,980 a month: a developer, an agency, a marketer, a host and a CMS. Every one of those line items exists because something in the previous section can break. The migration is $3,000 one time. The old site stays live while the new one is built, and a person reviews every page before launch.

Read the table once more. The one-time price is smaller than a single month of the old stack.

I built LiveHelpNow into an Inc. 5000 inductee (#84, 2015-2018), and as an operator I read a recurring line item differently than a one-time one. A monthly cost compounds quietly. A one-time cost ends.

The results after the move are what make the math matter. These are the client figures, as reported in our case studies:

• HelpSquad (WordPress to AEO website): about 20 inbound leads a day two months after the switch, against 5 a month before we started; AEO Rank 68 to 82.
• Modern Wealth (WordPress with Elementor): 10 booked calls in 3 weeks; Google clicks +61%.
• Counseling & Nature (Squarespace): 5 appointments in 2 weeks; AI engine visits 149 to 1,448 a week.
• Understood Care (Webflow): AEO Rank 37 to 82; 132 AI Overview citations.
• Seamless Chex (Webflow): AI engines link it on 28 of 40 buyer questions.

What our own client data shows

Here is one lead channel from our own client data. HelpSquad, a customer service outsourcing company, left WordPress in spring 2026. Online bookings confirmed through its new site went from 52 in August to 81 in September, and October was on pace for about 89. Counting calls and email as well, HelpSquad now gets about 20 leads a day.

"Never in my wildest dreams could I have anticipated all these leads. This is a situation every small business dreams of."

Jason, CEO of HelpSquad

Two of the five started on WordPress. The other three started on Squarespace or Webflow, which tells me the problem is the patched builder, not one brand of it. 14 client sites have moved so far.

Alex and I bring a combined 40+ years of SEO and content infrastructure experience to AEO, and the pattern in those results is not a plugin setting. It is a page built so the answer is present on arrival, which is also why our research-driven content built on evidence lands differently on a clean site than on a patched one.

The promise behind the work is plain: named in AI answers in 90 days, or AEO Content works free until you are. That promise depends on pages a crawler can actually read. So price the checking, not only the fix.

Checking is harder than it sounds, because the usual dashboards will not show the problem. Webolutions, an agency that sells AI search work, writes that answers on ChatGPT and Perplexity "rarely show visible citations or link pathways unless specifically requested," and that leaders now ask why organic traffic falls while rankings look stable. Treat that as an agency's view rather than a measurement, but the practical point holds. A rank tracker will not tell you whether last month's patch survived. Ask whoever quotes the monthly retainer which line item covers that check, and how many hours it assumes. Those hours belong in the monthly column of the cost comparison. If you would rather spend them on the answers than on the plumbing, moving your site to an AEO website takes plugins, theme and cache off the list.

Should you keep patching WordPress or move once?

Patch WordPress if someone owns the six steps every week. If nobody does, move once, because every fix that needs re-checking becomes a cost that never ends.

The tooling is drifting toward the crawler. A commenter in the June 2026 r/SEOorganic thread described a newer category of tools that serve a clean, data-dense version of a site to GPTBot and Google-Extended instead of the JS-heavy theme. That is a workaround for a page built wrong. I'd rather build it right.

The same commenter added a warning I take seriously: "Getting mentioned and getting represented accurately are two different problems, and the plugin layer only solves the first."

A clean page solves more of the second. Answers present on arrival. Prices that match what you charge. One source of markup, not three.

So here is the offer, plainly. The move is $3,000, one time. Your old site stays live until the new one is ready, and a person reviews every page before launch.