Where WordPress sites usually lose points
WordPress is not slow or hard to index by itself. The problems come from what gets added: a page builder, a dozen plugins each loading their own CSS and JavaScript, a theme that outputs its own meta tags next to an SEO plugin’s, and a caching layer that nobody configured. The result is a site that passes the on-page checks and fails performance, or one where the robots.txt written by a security plugin quietly blocks crawlers you wanted.
The audit reads the final HTML the way a crawler does, so it sees the combined output of theme and plugins rather than any one setting. When it flags a duplicate description or a blocked crawler, the fix is usually one setting in one plugin, and the report names the owner for each issue so you know whether to open the admin panel or call a developer.
What this audit looks at for wordpress sites
The audit runs the same 60+ checks as the main tool. The items below are the ones that most often decide the outcome for this kind of site, with the fix we recommend.
- Duplicate title and description tags
- Themes and SEO plugins sometimes both output meta tags. The audit reads the final HTML and flags duplicates and lengths.
- Script and style bloat
- Page builders and plugins enqueue scripts on every page. The audit counts external and inline scripts, measures HTML size and pulls Lighthouse opportunities.
- Image dimensions and lazy loading
- Missing width and height attributes cause layout shift. The audit checks image attributes and real-user CLS.
- Sitemap and robots.txt
- WordPress generates a sitemap at /wp-sitemap.xml unless a plugin replaces it. The audit discovers the sitemap through robots.txt and the common paths and checks whether the page is listed.
- Security headers
- Most hosts do not set HSTS, CSP or X-Content-Type-Options by default. The audit checks each header and the certificate.
- AI crawler rules
- Some security plugins block AI crawlers by default. The audit tests robots.txt and fetches the page as GPTBot, OAI-SearchBot, ClaudeBot and PerplexityBot to show what they actually get.
Frequently asked questions
- Do I need an SEO plugin to pass?
- No. Plugins make titles, descriptions and schema easier to manage, but the audit reads the output HTML, not the plugin. A well-built theme without a plugin can score higher than a plugin-heavy site.
- Why is my performance score low on a fast host?
- Performance is measured on a simulated mobile device and from real Chrome users. Render-blocking CSS and JavaScript from plugins and page builders usually dominate, not server speed.
- Does the audit detect my WordPress version or plugins?
- It does not fingerprint the site. It reports what affects search and AI visibility: headers, tags, structured data, performance and crawler access.
- Can I audit a staging site?
- Only if it is publicly reachable without a password. Local and password-protected sites cannot be fetched.