Can an AI agent
actually read your site?
Paste a URL and get forty checks across five layers in about thirty seconds. Every failure names who has to fix it: you in a plugin setting, your host in a server config, or a writer in the copy. RankReady is the WordPress AI SEO plugin that turns the first three layers green from your dashboard, in about five minutes.
v1.3.1 · 300 active installs · Tested to WordPress 7.1 · Runs alongside Yoast, Rank Math, AIOSEO and SEOPress
A score with no order
tells you nothing.
A site can carry perfect schema and stay invisible, because the server refuses the crawler. A site can be perfectly reachable and never quotable, because every sentence runs forty words. Checks that ignore that dependency send you to the wrong layer.
Reach fails first
If a crawler cannot fetch the page, nothing under it matters. Robots rules for 29 named AI crawlers, Content Signals, blocked /.well-known/ paths, and whether a declared crawler gets the same response a browser does.
Read is where the cost is
Markdown negotiation, q-values in both directions, a 406 on unsupported types, Vary: Accept sent as one merged line, and how heavy the page is on the agent path.
Understand is where WordPress breaks
Article, FAQPage and Person schema, exactly one canonical, heading order, and whether two SEO plugins are quietly writing the same tag twice. That last one is the most common real breakage.
Five layers, in the order
they depend on each other.
Layers one to three are settings on a WordPress site, and RankReady turns them on from the AI Visibility tab. Layer four is writing. Layer five needs code running on your own server when the request arrives.
Reach Layer 1
Crawler rules, Content Signals, server level blocks, and whether the response an agent gets matches the one a browser gets.
Read Layer 2
Content negotiation done properly, correct content types, cache behaviour at the edge, and payload weight on the agent path.
Understand Layer 3
Structured data, one canonical, sequential headings, and a published and updated date a machine can read.
Quote Layer 4
Whether a passage still stands up once it is lifted out of your page. No free checker other than this one measures it.
Measure Layer 5
Which AI crawlers actually arrived. A scan from outside cannot answer this, and the report says so rather than guessing.
Who fixes it
Every failure carries an owner. A 403 on /.well-known/ is an nginx rule, not a missing plugin feature, and being told to fix something you cannot fix is worse than not being told.
Nobody can promise
you a citation.
This is the section competitors leave out. Read it before the feature list rather than after.
It cannot tell you whether ChatGPT will quote you
Nothing can. What the check measures is narrower and true: whether an agent can find your content, fetch it, parse it cheaply, and lift a passage that still makes sense on its own.
A good score is the removal of excuses
Passing every layer removes the reasons an agent cannot use you. Whether it then chooses to is its decision, not a setting you can flip.
Layer five is not answerable from outside
Only something running on your server can log a crawler hit. The check hands that layer to the plugin and labels it, rather than inferring a number.
Fixes are WordPress specific, checks are not
Layers one to four are pure HTTP and HTML, so any site can be scanned. The settings level fixes assume WordPress, and the report says which is which.
The honest answers,
before you have to ask.
Q. Is the check free, and do you keep my URL?
Yes, and no. No signup, no email wall, no credit card. Scans are not stored against your domain and nothing is emailed to you.
Q. Does it work on sites that are not WordPress?
Yes. Layers one to four are pure HTTP and HTML. The fixes offered as a plugin setting are WordPress specific, and the report says so rather than pretending otherwise.
Q. Why does my score differ from Cloudflare's agent readiness check?
Different questions. Cloudflare grades protocol adoption on a level from 0 to 5, including standards very few domains have implemented. This checks whether your content is reachable, parseable and quotable today.
Q. My site already has an llms.txt. Does that make it AI ready?
No, and it is worth being blunt. SE Ranking studied roughly 300,000 domains and found no correlation between having the file and being cited. Ahrefs found 97 percent of llms.txt files received zero traffic. Google has said it does not use the file.
Q. Will fixing everything get me cited?
Unknown, and anyone answering differently is guessing. What it does is remove the reasons an agent cannot use you.
Q. Do I need the plugin to act on the results?
No. Every check is verifiable with curl and view source. RankReady turns the WordPress ones into toggles, which takes about five minutes instead of an afternoon.
Run the check,
then fix it in a toggle.
RankReady is a WordPress AI SEO plugin that turns the reach, read and understand layers on from your dashboard. It runs alongside Yoast, Rank Math, AIOSEO and SEOPress, and setup takes about five minutes.
Free, no account, no credit card · GPL-2.0 · About five minutes from your dashboard