How AI Answer Engines Read Your WordPress Site (and How to Make Them Read It Right)
How AI Answer Engines Read Your WordPress Site (and How to Make Them Read It Right) When someone asks ChatGPT, Perplexity or Claude a question today, the answer often comes straight from a website — with no click, no v
How AI Answer Engines Read Your WordPress Site (and How to Make Them Read It Right)
When someone asks ChatGPT, Perplexity or Claude a question today, the answer often comes straight from a website — with no click, no visit, no search results page in between. If your WordPress site cannot be read cleanly by those answer engines, you simply do not exist in their answers.
I learned this the practical way. I run a WordPress tutorial site, Learn WordPress Online, with 26 step-by-step guides. The guides rank on Google, but I wanted them usable by AI engines too. Here is exactly what I did, what worked, and what did not — tested on my own live site on 16 November 2026.
Why WordPress sites are hard for AI engines to read
A default WordPress install does three things that make an AI crawler's job harder than it needs to be. First, its robots.txt says nothing about AI crawlers at all, so each engine has to guess whether it is welcome. Second, there is no llms.txt file — the simple text file that tells an AI model what a site contains and where to find it. Third, most guides are plain article pages with no structured data describing the steps they teach, so an engine has to infer the procedure from prose.
None of this is broken. It is just unoptimised. Fixing it took me under an hour, with free tools only.
Step 1: Let the crawlers in with robots.txt
AI crawlers respect robots.txt. If your file does not mention them, they may still crawl, but you have given them no explicit permission — and some site owners block them by default.
I added explicit allow groups for the main AI crawlers to my robots.txt: GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended and CCBot, alongside the usual Googlebot and Bingbot groups. Each group is a simple two-line rule — User-agent, then Allow: /. The WordPress admin area stays disallowed, with admin-ajax.php explicitly allowed so the site keeps working.
One honest note: allowing a crawler is a permission, not a guarantee. It does not force any engine to read your site, and it does not make your content appear in answers. It only removes the first barrier.
Step 2: Give them a map with llms.txt
The llms.txt standard is a plain-text file at the root of your site that lists what the site is and links to its key pages. It was proposed specifically so large language models can understand a site without crawling every page.
I installed the free Website LLMs.txt plugin, which generates the file automatically from your published pages and posts. On my site it produced a file listing all 26 guides, each with its title and URL, under a one-line description of the site. The file is live at /llms.txt and took about two minutes to generate.
The plugin's settings are simple: include pages and posts, cap the word count per entry, regenerate when you publish. There is nothing to buy and no account to create. If you would rather write the file by hand, it is just markdown — a heading, a short description, and a list of links.
Step 3: Give your guides structure with HowTo schema
This was the step that surprised me. My site uses Rank Math, a popular free SEO plugin, and I assumed its free version could add HowTo structured data to my guides. It cannot. The HowTo schema type is locked behind the paid Pro version, and the free version only outputs Article schema.
So I used the free Code Snippets plugin instead. One PHP snippet, hooked to wp_head, outputs a JSON-LD HowTo block on the five guides I chose first. The snippet checks the post ID, then builds the steps from each article's own wording — step name and step text, numbered in order. No total time is included, because none of my articles states one, and inventing one would be dishonest data.
The pattern is short: check is_single() and the post ID, build an array of steps, encode it with wp_json_encode, and print it inside a script tag of type application/ld+json. The Rank Math Article block stays in place — the two coexist without conflict.
Step 4: Verify it actually works
Structured data that nobody checks is just hope. I verified the result three ways. First, I opened the live page source and confirmed the full HowTo JSON-LD block was present on the page. Second, I ran the page through validator.schema.org — the result was zero errors and zero warnings on the HowTo item. Third, I confirmed the llms.txt file serves live with all 26 guide links.
One result worth reporting honestly: Google's Rich Results Test shows the Article item but does not list HowTo at all. That is expected, not a failure — Google removed HowTo rich results from search in 2023. The HowTo schema here is not for Google rankings. Its value is semantic: it gives AI answer engines a clean, machine-readable version of the procedure, which is exactly what they need to quote your steps accurately.
What this does not do
Three honest limits. First, none of this guarantees your content appears in any AI answer — the engines choose their sources, and quality and relevance still decide. Second, it does not improve your Google ranking; HowTo schema has no rich-result payoff on Google any more. Third, it is a one-time setup, not a traffic strategy — you still need guides worth quoting.
What it does do is remove every technical excuse an AI engine has for skipping your site. If your content is good, it can now be found, read and quoted correctly.
The bottom line
Making a WordPress site readable for AI engines is four small jobs: an explicit robots.txt, a generated llms.txt, HowTo schema added with a free plugin, and a real verification pass. No paid plugin, no developer, no rebuild. I did it on a live site in under an hour, and the only cost was the time to check each step actually worked.
About the author: Mohd Shah Ahmad runs Learn WordPress Online (learnwordpressonline.co.za), where he publishes step-by-step WordPress and WooCommerce guides — every step tested on a real install, with screenshots.
Read all 34 step-by-step WordPress and WooCommerce guides at https://learnwordpressonline.co.za/all-guides/
Originally published by Dev.to AI. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.