Site platforms

WordPress, and what an answer engine can read of it

WordPress is the easiest platform in this list to fix, because you have the webroot and a plugin already generating most of the markup. It is also the one most likely to be failing a check for a reason nobody chose: the robots.txt is virtual unless a real file exists, and a security or caching plugin installed two years ago is a common source of a crawler block the owner did not know about.

The check worth the most here is the Organization one. Both Yoast and Rank Math will emit a full Organization block with sameAs links from a settings screen most sites never open — five minutes of filling in fields, and the engines get an entity instead of a string.

How we recognise it: a WordPress generator tag, /wp-content/ asset paths, or an X-Pingback header. Run the free readiness check and the fixes it gives you are the WordPress ones below.

What to do

  1. 1.Find out whether your robots.txt is real or virtual

    If there is no robots.txt file in the webroot, WordPress generates one on the fly and your SEO plugin is what edits it. If there is a file, the plugin's editor may be writing somewhere nobody reads. Check the webroot before you edit anything.

    Over SSH or in your host's file manager

    ls -la /path/to/webroot/robots.txt
  2. 2.Fill in Site representation properly

    Yoast: SEO → Settings → Site representation. Set it to an organization, add the name and logo, then add every profile in the social list — those become the sameAs array. Rank Math keeps the same thing under Titles & Meta → Local SEO. This is the single highest-value five minutes on a WordPress site.

  3. 3.Put llms.txt in the webroot

    Next to wp-config.php. It is served as a static file, no plugin involved, and it survives theme changes. Write it as markdown: an H1 with the product name, a line on what it does, then links to the pages worth quoting.

    llms.txt

    # Your company
    
    > One sentence on what you do and who for.
    
    ## Docs
    - [Getting started](https://yourdomain.com/docs/start): what to do first
    - [Pricing](https://yourdomain.com/pricing): plans and what each costs
  4. 4.Check the usual suspects if crawlers are blocked

    A blanket Disallow on a WordPress site is nearly always a plugin rather than a decision. Security plugins, bot-blocker plugins, and some caching plugins all write crawler rules. Wordfence and Cloudflare's bot-fight mode also block AI crawlers at a layer robots.txt cannot show you — if the file looks clean and the crawlers still cannot get in, look there.

The readiness checks on WordPress

CueScout runs eight checks on whether an answer engine can read a site at all. These are the ones whose answer is different on WordPress — the rest are the same everywhere.

AI crawlers allowed in robots.txt

WordPress serves a virtual robots.txt unless a real file exists in your webroot. Yoast (Tools → File editor) and Rank Math (General Settings → Edit robots.txt) both edit it in place; a plugin like Blackhole or a security plugin is the usual source of a block you did not add.

llms.txt present and parseable

Drop llms.txt in your WordPress root next to wp-config.php. It is served as a static file and needs no plugin.

Organization schema with sameAs links

Yoast: SEO → Settings → Site representation — set it to an organization and fill in the social profiles, which is what becomes sameAs. Rank Math has the same thing under Titles & Meta → Local SEO.

FAQPage schema present

Both Yoast and Rank Math ship an FAQ block for the block editor that emits the schema. Add it to a page that already answers real questions rather than making a page to hold the block.

Content readable without JavaScript

A standard theme server-renders. If this is failing you are on a headless or block-heavy setup that hydrates the content client-side, and the fix is in the theme rather than in WordPress.

These describe WordPress’s own settings, which move without warning us. Last checked against the product on 2026-08-14.

What this does not do

  • CueScout reads your site from the outside. It does not log into WordPress, install a plugin, or change anything — there is nothing to authorise and nothing that can break your site.
  • A block at the edge — Cloudflare's bot fight mode, a WAF rule, a host-level bot filter — does not appear in robots.txt. The crawler check can only report what the file says.
  • The Organization fix assumes Yoast or Rank Math. On a site with neither, the JSON-LD has to go in the theme's header.php or via a code-snippets plugin.

Frequently asked questions

Do I need a plugin for any of this?

No. Everything here can be done with a text file and a theme edit. Yoast and Rank Math just make the schema part a settings screen instead of hand-written JSON-LD, which is why the instructions name them.

Will an llms.txt file get overwritten by an update?

No. WordPress core updates touch wp-admin and wp-includes, not files you added to the root. It survives core, theme and plugin updates.

My site passes every check but no engine mentions us. What now?

That is the normal case, and it is the point at which readiness stops being the problem. These checks only establish that an engine can read you. Whether it recommends you depends on what other pages — roundups, community threads, comparison sites — say about your category, which is what Citation Sources is for.

Related

Every integration we publish

See where your WordPress site stands

The readiness check is free, needs no signup, and takes about half a minute. It works out what your site is built on and gives you the fixes written for it.