# AEO for WordPress: How to Make Your Site Perform in AI Search

By: Justin Abrams
Published: 2026-05-24

WordPress is the most open of the major site platforms. Here is how to use that freedom for AEO, from robots.txt to llms.txt to Markdown twins, so AI search cites you.

*WordPress, self hosted, is the most open of the major site platforms. Where Shopify and Squarespace constrain you, WordPress hands you the keys. Here is how to use that freedom for Answer Engine Optimization.*

WordPress runs a very large share of the web, and in its self hosted form it is the most open of the major site platforms. We have now looked at AEO on Shopify, where you are a listing inside a shared catalog, and on Squarespace, where your control narrows to a single checkbox. WordPress is the opposite case.

Self hosted WordPress hands you the keys: the files, the code, the headers, the whole stack. Nearly everything in our foundational guide for custom sites, [Is Your Website Optimized For LLMs?](https://www.causeofakind.com/blog/is-your-website-optimized-for-LLMs), is genuinely available to you. That is the opportunity. The catch is that freedom cuts both ways. The same openness that lets you do everything also lets you, or a bloated theme, or a careless plugin, quietly work against you. This article is about using the freedom well.

## First, know which WordPress you are on

"WordPress" means two different things, and the difference decides what this article can promise you.

WordPress.org is the free, open source software that you install on your own hosting. It gives you complete control: any plugin, any theme, direct file access, and the ability to edit code. WordPress.com is a hosted service run by Automattic, where capabilities are tied to your plan. Its higher tier plans unlock plugins and custom code and behave much like self hosted WordPress. Its lower tiers are closer to a managed builder.

This article assumes self hosted WordPress, or WordPress.com on a plan that allows plugins and custom code. If you are on a lower WordPress.com tier, you have fewer levers, and our companion article on AEO for Squarespace is closer to your situation.

## Move 1: Confirm crawlers can actually reach you

Before any optimization, rule out the two ways a WordPress site quietly hides from AI.

The first is a single checkbox. Under Settings, Reading, there is an option labeled "Discourage search engines from indexing this site." It exists for sites still in development, and it is the most common reason a freshly launched WordPress site is invisible. When it is checked, WordPress adds noindex signals and discourages crawlers across the board. Confirm it is unchecked on your live site.

The second is robots.txt. WordPress serves a virtual robots.txt by default, and unlike a managed platform, you control it completely. The easiest path is your SEO plugin's robots.txt editor, found in Yoast under Tools and File editor, and in Rank Math under General Settings. Or drop a physical robots.txt file in your site root, which overrides the virtual one. Either way, make sure the major AI crawlers are welcome:

```text
User-agent: GPTBot
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: ClaudeBot
Allow: /
User-agent: PerplexityBot
Allow: /

Sitemap: https://yoursite.com/sitemap_index.xml
```

One more check, and it is not WordPress itself: your host or CDN. Some managed hosts and CDN configurations block AI bots by default. If your robots.txt looks correct but no AI crawler ever appears in your logs, look there next.

## Move 2: Turn on llms.txt and structured data through your SEO plugin

This is where the WordPress ecosystem does the heavy lifting for you. The SEO plugin you almost certainly already run has caught up to AEO.

Yoast SEO now generates an llms.txt file natively, in both its free and paid versions. You enable it in the plugin's site feature settings, and Yoast builds and refreshes the file on a weekly schedule, automatically selecting your most relevant and recently updated content. If you run Rank Math, SEOPress, or AIOSEO instead, the dedicated Website LLMs.txt plugin generates one and integrates cleanly with each of them.

A fair caveat, in keeping with our evidence first habit: the experiments on llms.txt are mixed, and even Google's John Mueller has [questioned the standard](https://www.searchenginejournal.com/yoast-seo-wordpress-plugin-adds-support-for-llms-txt/549220/). Treat llms.txt as low cost housekeeping, not a growth lever. The reason to switch it on is simply that here it is one click.

The bigger win from the same plugins is structured data. Yoast, Rank Math, SEOPress, and AIOSEO all output structured data automatically, including Article, Organization, and breadcrumb types wired into a connected graph. Make sure your plugin's schema settings are filled in completely, especially your Organization or Person details and your logo, so the machine readable description of who you are is accurate.

## Move 3: Keep your theme and page builder from burying the content

Here is where WordPress's freedom can betray you. The platform serves clean, server rendered HTML by default, which answer engines love. Heavy page builders and bloated themes can undo that.

Some page builders wrap your content in deeply nested layers of div markup, and some dynamic widgets load content with JavaScript that a simple crawler never executes. The result is a page that looks rich to a human and reads as noise to a machine.

You do not have to abandon your builder, but you should be deliberate. Put your real content in proper heading and paragraph blocks with a correct heading hierarchy, not in decorative text widgets. Prefer a lightweight block theme or a well built classic theme over the heaviest builders for the content that matters most. And check the actual rendered source of an important page: if your core content is not there in plain HTML, neither a crawler nor an answer engine can use it.

## Move 4: Serve Markdown twins of your best pages

This is the freedom payoff, the thing a Squarespace site cannot do natively and a WordPress site can.

A Markdown version of a page is almost pure content, the cleanest possible format for an answer engine to read. On WordPress you have several honest paths to publishing them. The Website LLMs.txt plugin can attach Markdown files to your llms.txt entries. Other plugins generate full Markdown mirrors of your content. And because you can edit code, a developer can add a route that serves a `.md` twin of any post directly from WordPress itself.

However you generate them, advertise them. A few lines in your theme's functions.php tell crawlers reading your HTML that a clean copy exists:

```php
add_action('wp_head', function () {
    if (is_singular()) {
        // point this at wherever your Markdown twin is served
        $md = get_permalink() . 'index.md';
        echo '<link rel="alternate" type="text/markdown" href="' . esc_url($md) . '">' . "\n";
    }
});
```

That single capability is the clearest illustration of the difference between platforms. Squarespace needs a separate subdomain to do this. WordPress can do it in place.

## Move 5: Write the content that earns the citation

Everything so far gets machines to your content. This earns the citation, and no plugin does it for you.

Answer engines quote the specific and the sourced. The study from Princeton and IIT Delhi found that [content citing sources and including real statistics](https://arxiv.org/abs/2311.09735) was substantially more likely to appear in AI answers. So write that way. Lead each important page with a direct answer. Use real headings. Add an FAQ to pages where buyers have recurring questions. And turn vague claims into concrete ones:

```text
Weak:
"We offer a wide range of services to help your business
grow and succeed online."

Strong:
"We are a WordPress development agency in Austin. Since 2014
we have built and maintained 200 client sites, and our
managed care plans keep them loading in under 1.5 seconds."
```

WordPress makes this easy to act on, because publishing and editing is its native strength. The constraint was never the tool. It is the writing.

## Move 6: Instrument it, because you finally can

On a managed platform you often cannot see your raw traffic. On self hosted WordPress you can. You have server access, so you can read your access logs and watch for GPTBot, ClaudeBot, and PerplexityBot arriving, and for human visitors landing from chatgpt.com or claude.ai. The Website LLMs.txt plugin even has an opt in feature that reports whether the major AI crawlers are reading your llms.txt.

Use that visibility. AI visibility is an observability problem, and WordPress is one of the few site platforms that actually hands you the logs to treat it like one.

## What to expect

Be realistic, and be encouraged. Self hosted WordPress can match a hand built custom site for AEO. There is almost nothing in the modern playbook you cannot implement here, which is rare among site platforms.

The honest flip side is that the work is yours. WordPress will not stop you from shipping a bloated, builder heavy, plugin tangled site that machines struggle to read. Freedom assumes responsibility. Keep the site lean, keep the content clean, and keep an eye on the logs.

And treat AEO the way a serious operator treats SEO: a compounding channel, not a switch. Do these six things, maintain them, and read the trend over months rather than days.

## The COAK take

Shopify hands you a catalog. Squarespace hands you a checkbox. WordPress hands you the keys. That is the whole difference, and it means a WordPress site has no excuse. Every technique in the modern AEO playbook is available to you.

So use the freedom on purpose. Control your robots.txt, switch on llms.txt and schema, keep your theme honest, serve Markdown twins, write something specific and true, and watch your logs. None of it requires leaving WordPress, and most of it does not even require a developer.

For the full custom site foundation that WordPress lets you implement completely, see [Is Your Website Optimized For LLMs?](https://www.causeofakind.com/blog/is-your-website-optimized-for-LLMs).

And if you want a partner who can take a WordPress build all the way to that ceiling, that is what we do. Cause of a Kind is full stack, full service, on shore and in house. We help cool people build great products, and we make sure the answer engines know their name.

Canonical URL: https://www.causeofakind.com/blog/aeo-for-wordpress-how-to-make-your-site-perform-in-ai-search