WordPress · AI & agent readiness

See your site the way an AI agent does.

AIScanner grades your WordPress site over a real HTTP request, applies one-click fixes that never touch your content, and re-scans to prove the score changed.

Reversible fixes Zero telemetry Real HTTP checks
AGENT-READINESS · rubric v1 SCANNING
0
/ 100
Level 4
Interactive
Discoverability92
Content78
Bot Access67
Capabilities58
Verified over live request · GET / 200
The shift

Your readers aren’t all human anymore.

ChatGPT, Claude, Perplexity and a growing fleet of agents now visit sites to answer questions, buy things, and act on behalf of people. They don’t read your theme — they read your signals: robots rules, sitemaps, machine-readable content, and capability descriptors. Most WordPress sites emit almost none of them, and there’s no dashboard telling you so. AIScanner is that dashboard.

How it works

Scan. Fix. Verify — then keep it fixed.

A closed loop, not a one-off report. Every check fetches your site the way a crawler would, so a passing score reflects what an agent actually sees — even when a CDN or a stray robots.txt is overriding WordPress.

STEP 01

Scan over real HTTP

Grades five dimensions against a versioned rubric by fetching live URLs — never trusting internal plugin state. What a crawler sees is what gets scored.

STEP 02

Apply one-click fixes

Every fix writes plugin settings and nothing else. No theme edits, no rewritten posts — so “Turn off” genuinely restores the prior state. Fixes are fully reversible.

STEP 03

Re-scan to prove it

Verify re-fetches over a live request to confirm the score actually moved. A scheduled re-scan catches drift, so what you fixed stays fixed.

What it grades

Five dimensions. Fifteen checks. One weighted score.

Each check earns points toward its dimension; dimensions roll up to an overall 0–100 score and a readiness level. Inapplicable dimensions are excluded from the denominator, so the number always reflects your site.

Dimension13 pts

Discoverability

Can an agent find your content and its structure at all?

D1robots.txt present & sane6
D2XML sitemap4
D3Link header for discovery3
Dimension18 pts

Content

Is the content itself readable by a machine, not just a browser?

C1Markdown content negotiation8
C2/llms.txt6
C3Structured HTML4
Dimension15 pts

Bot Access

Do you state, in machine terms, which agents may do what?

B1Content Signals in robots.txt5
B2Explicit AI bot rules5
B3Web Bot Auth key directory5
Dimension12 pts

Capabilities

Can an agent discover what your site can actually do?

K1API catalog3
K2MCP card3
K3Agent skills3
K4OAuth metadata3
Dimension10 pts

Commerce

Can an agent transact? WooCommerce only

M1UCP signals5
M2x402 signals5
Roll-up= score

Weighted & honest

Points earned ÷ points possible, per dimension and overall. “Couldn’t verify” results stay informational — a blocked loopback never becomes a misleading pass or fail.

Info-tier results excluded from scoring
Detects Yoast / Rank Math / AIOSEO & defers
The readiness ladder

From invisible to agent-native.

Your overall score maps to one of six levels. It’s a real progression — each rung assumes the one below it — and it doubles as a shareable badge.

0 Level 0
Invisible
Agents can’t reliably find or read the site.
score 0–9
1 Level 1
Discoverable
Basic robots & sitemap signals are in place.
score 10–29
2 Level 2
Readable
Content is available in machine-friendly form.
score 30–49
3 Level 3
Governed
You state explicitly which bots may do what.
score 50–69
4 Level 4
Interactive
Capabilities & APIs are discoverable by agents.
score 70–89
5 Level 5
Agent-Native
Fully legible and actionable — the top of the rubric.
score 90–100
Why AIScanner

A scanner you can trust to fix things.

Plenty of tools flag what’s missing. AIScanner fixes it safely, proves the fix, and stays out of your content’s way.

Reversible by design

Every fix writes plugin settings only — no theme edits, no rewritten posts. Turning a fix off restores the exact prior state.

Real HTTP verification

Checks fetch your live site, catching a CDN or physical robots.txt that overrides WordPress — the kind of thing internal state hides.

Privacy-first

Requests hit your own site only. Nothing is sent to any third party, and there is no telemetry — not now, not opt-out-later.

Drift protection

A scheduled re-scan re-checks your score on a cadence, so a theme update or host change that regresses a signal doesn’t go unnoticed.

Plays well with SEO plugins

Detects Yoast, Rank Math and AIOSEO and defers per feature — so you never end up with two sitemaps or two JSON-LD graphs.

Agent-callable MCP server

An optional MCP server exposes scan / fix / verify / revert as tools an agent can call directly. Off by default, gated by a token you generate.

For agents, by design

Let an agent run the whole loop.

Flip on the optional MCP server and your readiness workflow becomes a set of tools an AI agent can invoke itself — scan, apply a fix, verify over HTTP, revert if needed.

  • Off by default. Nothing is exposed until you explicitly enable it in Settings.
  • Bearer-token gated. Stored as a SHA-256 hash, shown once, never included in an export.
  • Hardened. Origin-validated and rate-limited against failed authentication per IP.
Free · GPL-2.0 · WordPress 6.7+

Make your site agent-native.

Install AIScanner, run one scan, and see exactly where you stand with the machines that are already reading the web.

One scan · reversible fixes · no account, no telemetry