AI Readiness Score for WordPress: Grade Your Site for ChatGPT, Perplexity, and Google AI Overviews

Most WordPress sites that "aren't showing up in AI search" don't have a content problem. They have a plumbing problem. A robots.txt rule written years ago to fend off scrapers is quietly blocking GPTBot. There's no Organization schema, so the engine can't confidently tell who published the page. There's no llms.txt, no FAQ markup, and a handful of 404s that PerplexityBot keeps hitting. None of that is visible from the outside — it just looks like "AI doesn't cite us."

The AI Readiness Score exists to make that plumbing visible. It's a free, 0–100 grade in the AuditAE WordPress plugin that scores your site across eight weighted technical checks, tells you exactly which ones you're failing, and links you straight to each fix. This post explains what the score measures, why each check matters, and the fastest path to moving the number.

What the AI Readiness Score actually measures

The score is a single number from 0 to 100, with a letter grade attached, computed entirely from signals already present on your own site. There are no external API calls, no data leaves your server, and you don't need an account to see it. Activate the plugin and the score appears on its own tab and in your wp-admin dashboard widget.

It's built from eight checks, each weighted by how much it actually affects whether an AI engine can read and cite you:

The weighting is the useful part. It tells you where to spend the next hour. A perfect content library scores zero on the things that matter most if your robots.txt is blocking the crawlers — which is exactly why that check is worth a fifth of the entire grade.

Why each check moves AI citations

Citation crawler access (20 points)

This is the heaviest check because it's the most common silent failure. A single Disallow: / aimed at a misbehaving scraper, or a stale rule copied from a tutorial, will keep GPTBot or PerplexityBot out entirely — and from the outside it looks identical to "AI just doesn't cite us." The plugin's robots.txt auditor classifies every tracked AI bot as allowed, limited, or blocked, and flags citation-critical blocks in red. Fixing this one check is frequently the difference between a failing grade and a passing one. (For the full reasoning on why crawl access is the foundation of everything else, see why your #1 ranked page can still be invisible in AI search.)

Schema: FAQ, Organization, and per-post (40 points combined)

Structured data is how an AI engine resolves ambiguity without guessing. FAQPage markup hands the engine clean question-and-answer pairs it can lift verbatim. An Organization node, linked by @id to your articles, lets it say "this brand published this" with confidence. Per-post Article and Product schema gives every page a machine-readable spine. Together these three checks are 40% of the score, because trust and parseability are what separate "crawled" from "cited."

AuditAE's Schema Autopilot writes all of it as @id-linked JSON-LD without touching your post content, and it detects Yoast or Rank Math and reuses their nodes instead of duplicating them — so it coexists with your existing SEO plugin instead of fighting it.

AI-bot 404s and crawl activity (24 points combined)

Two sides of the same coin: are the bots showing up, and are they hitting walls when they do? The AI crawler tracker answers the first question — Google Search Console can't, because it doesn't log GPTBot, ClaudeBot, or PerplexityBot at all. The 404 check answers the second: when an AI bot repeatedly requests a dead URL, you're wasting crawl budget and losing whatever authority that URL once had. The plugin turns those logged 404s into one-click 301 redirects, so the fix falls out of the same data that surfaced the problem.

llms.txt and freshness (16 points combined)

An /llms.txt file is a plain-markdown manifest that points AI tools at the pages you actually want them to read — a low-cost signal that's still rare enough to be a differentiator. The plugin generates and serves one automatically; here's the full case for llms.txt and how to add one to WordPress. Freshness rounds it out: engines deprioritize content that looks abandoned, so the score rewards sites whose posts have been touched in the last year.

How to read — and move — your score

The number on its own is just a diagnosis. Three things make it actionable:

1. Every failing check links to its fix. You're never left wondering what "improve schema coverage" means in practice — the breakdown points you at the exact tab and the exact action, with the point value attached so you can triage by impact.
2. A 7-day delta tells you if your last change worked. Make an edit, come back in a week, and the score shows you the direction of travel. If you unblocked GPTBot on Monday and the number didn't move, something else is wrong — and you'll know to look.
3. A streak indicator rewards momentum. When the score climbs two or more readings in a row, the plugin flags it. Small thing, but AI readiness is a habit, not a one-time audit, and the streak is there to keep the habit going.

A realistic first-afternoon path for a typical site: audit and fix robots.txt (up to 20 points), publish your llms.txt (8), add Organization schema (12), add FAQ schema to your top posts (up to 16), and clear the worst AI-bot 404s (up to 12). That's a plausible 30-to-50-point swing before you've written a single new word of content.

Where the score ends and the work begins

The AI Readiness Score is deliberately a readiness measure, not a citation guarantee. It makes sure the engines can crawl you, parse you, and trust enough to consider you. Whether they then name you in an answer to a specific buyer question is a second, harder layer — one that depends on your authority and how directly you answer, and that you can only measure by checking the answers themselves.

That's the line between the free plugin and the paid product. The score and all eight underlying tools are free and local. When you want the fixes done for you — schema written, redirects created, alt text filled, internal links woven — and you want to know whether you're actually being cited across ChatGPT, Perplexity, and Gemini for the prompts that matter, that's AEBOT, the AuditAE assistant. It reads the same plugin data over a secure connection and closes the loop. The AI search optimization pillar covers that citation-side strategy in full.

But start with the diagnosis. Install the free AuditAE WordPress plugin, get your AI Readiness Score in under five minutes, and let the failing checks tell you exactly where your site is leaking AI visibility.