What a WordPress SEO and AEO audit checks
A WordPress SEO and AEO audit crawls your site to surface what plugin sprawl hides: conflicting schema from multiple plugins, uncrawled pages, render-blocking scripts, and AI crawlers blocked at robots.txt or by your managed host. It also confirms your content reaches ChatGPT and Perplexity. SEO AEO Specialist scans 50 pages free, then €9 for the full report.
The WordPress-specific problem
WordPress powers most of the web because it lets you add anything with a plugin. That same openness is where SEO quietly breaks. The biggest recurring mistakes are running two SEO plugins at once and creating schema or robots.txt conflicts (mean.ceo). When two plugins emit Article, Organization, or Breadcrumb schema, Google receives contradictory structured data and trusts less of it.
Performance is the second failure. Core Web Vitals almost always fail for four reasons: a heavy theme, plugin sprawl, unoptimized images, and blocking third-party scripts. Every plugin registers its scripts on every page by default, so a 40-plugin site can inject 25 scripts and 15 stylesheets on a page needing five (Overnatic). Common WordPress issues also include uncrawled landing pages and internal links that never reach the pages that need authority (mean.ceo).
The AEO failure is newer and sneakier: AI-crawler access. OpenAI runs three distinct bots, GPTBot (training), OAI-SearchBot (search index), and ChatGPT-User (live browsing), each with its own robots.txt token (No Hacks). Block the wrong one and you drop out of ChatGPT search results. Worse, some managed WordPress hosts block AI bots at the platform level where you can't see it (Search Engine Land). You think you're AEO-ready; the crawlers are getting a 403.
The tactics that actually matter for WordPress
Consolidate to one SEO plugin. Two plugins mean duplicate sitemaps, meta tags, and schema. Choose one, configure it fully, and disable SEO/schema features on the rest (BlogVault).
Audit AI-crawler access deliberately. Decide per bot. To appear in ChatGPT search, allow OAI-SearchBot and ChatGPT-User even if you disallow GPTBot for training (No Hacks). Then verify at the server level that your host isn't blocking them anyway. Note that llms.txt is not an access-control mechanism; robots.txt controls crawl access, llms.txt only provides context (DEV).
Trim plugin-injected assets. Identify plugins loading scripts sitewide when they're needed on one page. Keep the stack curated: one SEO plugin, one performance layer, one image optimizer, one redirect tool (mean.ceo).
Fix crawlability and internal links. Make sure important pages are reachable and linked. Uncrawled landing pages and links that never reach authority-needing pages are common WordPress problems (mean.ceo).
Keep core content server-rendered. Page builders and dynamic blocks can push text into client-side JavaScript. AI crawlers read only the initial HTML and don't execute JS (SearchVIU). Confirm your main content is in the source.
WordPress audit checklist
| Check | Why it matters | Common WordPress failure |
|---|---|---|
| One SEO plugin active | Prevents schema/sitemap conflicts | Two plugins running together |
| AI-crawler tokens set correctly | Controls ChatGPT/Perplexity visibility | Blocking OAI-SearchBot by accident |
| Host not blocking AI bots | Server-level 403s are invisible in WP | Managed host silently blocks |
| Scripts loaded only where needed | Core Web Vitals | 40 plugins injecting sitewide |
| Internal links reach key pages | Distributes authority | Orphaned landing pages |
| Content in initial HTML | AI crawlers can't run JS | Builder blocks render client-side |
| Single canonical per URL | Stops duplicate indexing | Tag/archive pages competing |
| XML sitemap accurate | Guides crawl | Two plugins, two sitemaps |
FAQ
Can I run more than one SEO plugin?
No. Two SEO plugins create conflicts in sitemaps, meta tags, and schema output (BlogVault). Pick one and disable SEO features elsewhere.
How do I let ChatGPT read my site but block AI training?
Use per-bot robots.txt tokens. Allow OAI-SearchBot and ChatGPT-User for search and live browsing while disallowing GPTBot for training (No Hacks).
Is my managed WordPress host blocking AI crawlers?
Possibly, and you can't see it from inside WordPress. Some managed hosts block AI bots at the platform level, returning errors your robots.txt never intended (Search Engine Land). An external audit catches this.
Does llms.txt control AI access?
No. llms.txt provides context to AI systems but is not an access-control mechanism. robots.txt controls crawl access (DEV).
Why are my Core Web Vitals failing?
Usually a heavy theme, plugin sprawl, unoptimized images, and blocking scripts. Every plugin loads its scripts on every page by default (Overnatic).
What does the free audit include?
A scan of 50 pages at no cost, enough to expose plugin conflicts, crawlability gaps, and AI-crawler blocks that repeat sitewide.
Audit your WordPress site
Start free: scan 50 pages at €0 to see schema conflicts, crawlability gaps, and AI-crawler access problems. The full-site report with fixes is €9 one-time. For ongoing checks as you add plugins, change themes, or edit robots.txt, €19/mo per domain re-audits on a schedule.
Wix SEO & AEO Audit | Platform Limits + What You Can Control
See where you stand
SEO AEO Specialist runs a free AI-visibility audit and hands you the exact fixes. One-off report €9, unlimited €19/mo.
Run your free audit →