For WordPress sites

WordPress AI visibility audit:
two scores, one fix path.

Measure your WordPress site the way AI engines experience it: a free local audit of your setup (llms.txt, schema, crawler rules) plus an AI-judged cloud audit of how your content survives extraction - side by side, never blended, each finding shipped with its fix.

The flow

Local first, cloud second, fixes throughout.

Step 1 - free, local
Setup readiness in wp-admin

Install the free plugin and run the local audit: real loopback checks of llms.txt, robots.txt, and sitemap serving, AI-crawler rules, and schema presence. Mechanical, instant, zero external calls.

Step 2 - cloud
AI visibility, judged by AI

Run the cloud audit from wp-admin or scan.citevera.com: 35 checks, three axis scores, the decision funnel, and AI judgment of how your content extracts into answers.

Step 3 - fix and re-measure
Apply fixes, watch both scores

Ship the generated fixes (many apply from the dashboard on WordPress), re-run both audits, and let the bundled weekly citation monitoring confirm engines are picking you up.

Why WordPress specifically

WordPress has failure modes generic audits miss.

A generic AI-readiness scan treats every site the same. WordPress deserves better, because its most common AI-visibility failures are WordPress-specific: plain permalinks silently serving your homepage at /llms.txt, SEO plugins double-emitting schema, page builders whose FAQ markup never reaches the rendered HTML, and robots.txt rules that predate the current AI crawler fleet. The local audit checks reality, not settings - it makes real loopback requests to /llms.txt, robots.txt, and your sitemap, so a check that passes means the endpoint actually serves.

The audit is honest about what it cannot know locally. Whether your content reads well to an AI engine is a judgment call, and the local audit does not pretend to make it - that is the cloud audit's job, and the two scores stay separate on your dashboard for exactly that reason. "Not measured" never moves a score.

Related reading: the complete WordPress AI search guide, 7 WordPress AI search mistakes, and the plugin-by-plugin AEO playbook. For a deeper look at what each audit layer checks, see the AEO audit for WordPress page; for the llms.txt side specifically, the llms.txt WordPress plugin page.

Questions

WordPress audit FAQ

What is a WordPress AI visibility audit?

A structured check of how visible your WordPress site is to AI answer engines - whether ChatGPT, Perplexity, Gemini, and Google AI Overviews can find, read, and cite it. Citevera splits it into two measurements: Setup readiness, a mechanical local audit of your llms.txt, schema, and crawler configuration, and AI visibility, an AI-judged cloud audit of how your actual content survives extraction into answers.

Why two scores instead of one?

Because they fail independently and blending them hides the diagnosis. A site can have perfect llms.txt and schema (high setup readiness) while its content extracts poorly (low AI visibility), or the reverse. Citevera shows both side by side and tells you which side is ahead - a gap over 20 points gets its own callout, because it points at exactly where the next work is.

What does the free local audit check?

The free plugin runs 10+ rule-based checks entirely on your server: whether /llms.txt, robots.txt, and your sitemap are actually served (verified by real loopback requests, not by reading settings), which AI crawlers your rules allow or block, and which schema types are present. It costs nothing, sends nothing anywhere, and runs on demand from wp-admin.

What does the cloud audit add?

The cloud audit runs your pages through the same AI pipeline as scan.citevera.com: 35 checks across AEO, GEO, and Crawlability, a 5-stage decision funnel, and AI judgment of how your content reads to an answer engine. Every finding ships its fix artifact - llms.txt, JSON-LD, robots.txt rules, or a content rewrite.

My audit score changed after I fixed my permalinks but the dashboard still shows the old result. Why?

Endpoint checks are cached for up to an hour, so after a permalink or configuration change the dashboard can briefly score from pre-change results. Re-run the audit or wait out the cache - the underlying check is honest, just not instantaneous.

What does it cost?

The local audit is free forever inside the free plugin. Cloud audits come with paid tiers from $49/mo, or as a $99 one-time full audit with PDF export on citevera.com - no subscription required. Every paid tier also includes weekly citation monitoring across ChatGPT, Claude, and Gemini.

Start with the free local audit.

Install the plugin, run the audit, fix what it finds - then decide whether the cloud audit is worth $99 once.

Get the free plugin