Free tool · No email required
Plugin retrievability check
Give it a wordpress.org plugin slug. It fetches the vendor’s site the way each AI retrieval crawler does and tells you what actually comes back — certificate, redirects, robots rules, live response code, and whether your content is in the HTML they receive.
This is the half of “AI visibility” that is mechanically checkable. It is also the half that is broken far more often than anyone expects, and the half no other free checker looks at properly.
Why a slug and not a URL?
Because the slug is enough. The wordpress.org plugin API gives up your homepage, your category, your install count and your last-updated date from those few characters, so you do not have to tell me anything I can look up myself.
It also means this tool knows what you sell, which is how it can tell you your category at the end — and that is the first thing that matters once the mechanical checks pass.
What it checks
| Check | Why it is on the list | If broken |
|---|---|---|
| TLS certificate | An expired certificate fails the fetch before a word is read. This site was invisible to every retrieval crawler for 152 days on exactly that. | Total |
| HTTPS and redirect chain | Requests that do not land cleanly on https lose retrievers along the way. | Partial |
| robots.txt, split by purpose | Retrieval crawlers and training crawlers are different bots. Blocking training is a business decision; blocking retrieval removes you from answers. | Total |
| Live response per crawler | A robots.txt allow is not a server 200. Bot protection at the CDN sits in front of robots.txt and refuses the request anyway. | Total |
| Content in the raw HTML | Retrieval crawlers generally parse HTML rather than executing scripts. Client-rendered content can be an empty shell to them. | Total |
| XML sitemap | The ordinary discovery path. | Partial |
| llms.txt | Reported, and scored zero on purpose. See below. | None observed |
The fourth row is the one to pay attention to, because it is the only place this tool tells you something no other free checker will. Plenty of sites publish a robots.txt that welcomes every retrieval crawler and then have a firewall rule quietly returning 403 to all of them. Reading the file tells you the intention. Only a live request tells you what happens.
Why does llms.txt score zero?
Because Ahrefs checked 137,000 sites that had published one and found 97% of those files had never been requested by any crawler at all. Not read and ignored — never fetched.
Free checkers list it among their scored signals because it is trivially easy to check, and a checkable thing makes a tidy line in a report. It is reported here so you know where you stand, and weighted at nothing so it cannot flatter a site that is actually unreachable. The full argument, and how to check your own access log in a minute, is here.
What this tool cannot tell you
This checks whether retrieval crawlers can reach you. It says nothing about whether you are cited. Those are different problems with different fixes, and collapsing them into one “visibility score” is the central mistake in this whole product category.
The clearest proof of that is a plugin you can run through the tool yourself. All-in-One WP Migration has over five million active installs and passes every check on this page. Across ten measured plugin categories on two engines, it was named in exactly one answer — the one where the question already contained its name.
Retrievability is necessary and nowhere near sufficient. Passing everything here means you are eligible, not chosen. What decides the rest is whether you appear in the pages the engine actually reads for your category — and that is a question about other people’s pages, which no automated check of your own server can answer.
So I run that half by hand. Send me your slug and I will pull the full source list for your category from both Perplexity and Google AI Mode, and tell you who is being read and whether you are in it.
Notes on how it runs
Nothing is stored against you and no email is asked for. Results are cached for an hour, so a second check of the same plugin returns the first run rather than hammering someone’s server. Each check makes about a dozen ordinary HTTP requests to the homepage on file at wordpress.org and takes five to fifteen seconds.
It only ever fetches the public homepage listed on the plugin’s own wordpress.org page, over http or https on standard ports, and it refuses anything that resolves to a private address. It is a diagnostic, not a scanner.
Once the checks here pass, the question becomes which prompts your buyers actually type. The prompt set builder generates the fifteen I run in a paid audit, weighted towards the shapes that produce citations.
Now the half a tool cannot do
Send me your wordpress.org slug. I will run your category question on both engines, open the full source lists, and send back which domains the answer was built from — including the ones naming your competitors and not you. Free, no call, usually within a day.