How Detection Works
Unlike OAuth-based integrations that require you to connect external accounts, SiteAuditPro's WordPress support is entirely automatic. When you run an audit on any site, the scanner checks for WordPress-specific signals in the page source — the wp-content path structure in asset URLs, the WordPress meta generator tag, and characteristic HTML patterns that WordPress themes and core produce by default.
If those signals are present, SiteAuditPro identifies the site as a WordPress installation and immediately layers on an additional set of CMS-specific checks beyond the standard SEO, LLM readiness, and performance analysis. This happens silently in the background — you do not need to configure anything, connect any credentials, or manually select WordPress as your CMS. The detection runs on every scan, and the extra checks are applied automatically whenever WordPress is found.
This approach means that even if you are auditing a client site or a new domain you have not previously scanned, the WordPress-specific checks are present from the very first audit. There is no setup step to forget.
Requirements
Because WordPress detection is fully automatic, the requirements are minimal:
- A SiteAuditPro Premium plan — WordPress-specific CMS checks are not available on the Free tier
- Your site must be running WordPress, either self-hosted (wordpress.org) or WordPress.com Business plan (which allows custom themes and plugins)
- No manual configuration needed — detection is automatic and runs on every scan
WordPress.com sites on lower plans (Personal, Premium) that do not support custom themes or plugins will not exhibit all of the WordPress markers that SiteAuditPro looks for, and may not be reliably detected. Self-hosted WordPress installations using any reasonably standard theme will be detected correctly in virtually all cases.
There is no API key to obtain, no OAuth flow to complete, and no settings to toggle. If you are on a Premium plan and scan a WordPress site, the CMS-specific checks are included automatically.
What Gets Checked
Once WordPress is detected, SiteAuditPro runs a set of checks specifically tailored to how WordPress sites are structured and how their SEO is typically managed. These checks complement the standard audit findings rather than replacing them — you still get your full technical SEO, LLM readiness, and performance scores, plus the following WordPress-specific analysis:
- SEO plugin detection across the most widely used options — Yoast SEO, RankMath, All in One SEO Pack, and others — with checks verifying not just that a plugin is present but that it is actively contributing structured metadata to the page
- WordPress-specific schema markup validation that checks whether the CMS or an SEO plugin is injecting JSON-LD or microdata correctly, and whether the schema types in use are appropriate for the content
- XML sitemap configuration checks for both WordPress's built-in sitemap (
wp-sitemap.xml) and the sitemap formats generated by SEO plugins, verifying that sitemaps are accessible, correctly formatted, and referenced in the site's robots.txt - Theme performance analysis that identifies render-blocking scripts and stylesheets enqueued by the active theme, flags excessive DOM size caused by page builder output, and checks whether theme assets are being loaded efficiently
- Plugin conflict detection that looks for patterns associated with multiple conflicting SEO plugins running simultaneously, duplicate meta tag generation, or other plugin interactions that can silently degrade SEO performance
- WordPress REST API availability checks to confirm whether the REST API is accessible and correctly configured, which affects compatibility with headless setups, third-party tools, and certain SEO plugin features
Taken together, these checks cover the most common points of failure for WordPress SEO — the places where a technically capable platform most often produces suboptimal results due to misconfiguration, plugin conflicts, or theme-level performance issues.
Interpreting Results
WordPress-specific check results appear in your audit alongside the standard findings. Each check shows a pass, warn, or fail status, a score, and a detail message that explains what was found and what action, if any, is recommended.
Results for plugin detection are informational as much as evaluative. A result that says "Yoast SEO detected" with a passing score confirms that a capable SEO plugin is present and active. The detail message will note whether Yoast's meta tags are appearing correctly in the page's <head> — if the plugin is installed but its output is not making it to the page due to a caching or theme conflict, the check will warn or fail rather than pass.
Theme performance warnings are among the most actionable results. A warning about render-blocking resources tells you that your theme is loading scripts or stylesheets in a way that delays the browser from rendering page content — which directly impacts Core Web Vitals scores and user-perceived load time. The detail message will indicate how many render-blocking resources were detected and whether they originate from the theme, a plugin, or both.
Sitemap checks produce pass results when a valid sitemap is found at a standard location and is referenced from robots.txt, warn results when a sitemap exists but is not referenced or has structural issues, and fail results when no sitemap can be found at any expected location. If your SEO plugin generates a custom sitemap URL, make sure that URL is submitted to Google Search Console and referenced in robots.txt to ensure the check passes.
Plugin conflict detection flags situations where multiple SEO plugins appear to be active simultaneously — for example, finding both Yoast and RankMath meta tags in the same page. This is a genuine problem in practice: running two full SEO plugins at once typically results in duplicate meta tags, conflicting canonical tags, and unpredictable sitemap behavior. The audit will fail this check and include a recommendation to deactivate all but one SEO plugin.
Optimization Tips
Install and properly configure one SEO plugin — not multiple. Yoast SEO and RankMath are both excellent choices, but running both simultaneously causes real problems. Duplicate meta descriptions, competing XML sitemaps, and conflicting canonical tag logic are all common outcomes of having two active SEO plugins. Pick one, configure it thoroughly, and deactivate the other completely rather than just disabling it.
Use a well-coded theme and check its performance footprint. Page builders like Elementor and Divi produce feature-rich results, but they also tend to enqueue large amounts of CSS and JavaScript on every page regardless of whether those assets are used. If your theme performance check shows a high number of render-blocking resources or an inflated DOM node count, consider switching to a lighter theme or using a performance plugin to defer non-critical assets.
Keep WordPress core, themes, and plugins updated. Outdated WordPress installations are a security risk, but they also frequently affect SEO — older versions of popular SEO plugins may produce schema markup that does not match current Google guidelines, or may miss support for newer structured data types. Staying current ensures that the SEO plugin behavior the audit is evaluating matches the plugin's intended behavior.
Leverage WordPress's built-in lazy loading for images. Since WordPress 5.5, the platform adds loading="lazy" to images automatically. If your audit results show images without lazy loading, this may indicate that your theme is outputting images outside of the standard WordPress functions, bypassing the automatic attribute injection. Check your theme's image output functions to ensure they use wp_get_attachment_image() or similar native functions.
Consider a caching plugin if performance scores are low. WordPress without caching serves dynamically generated HTML on every request, which is slower than serving cached static output. Plugins like WP Super Cache, W3 Total Cache, or LiteSpeed Cache can dramatically improve Time to First Byte scores. If your performance audit score is below 60, a caching plugin is often the single highest-impact change you can make without touching code.
One aspect of WordPress auditing worth bearing in mind: detection accuracy depends on the site's HTML being publicly accessible and not heavily modified to strip WordPress fingerprints. Some security-hardened WordPress installations deliberately remove the generator meta tag and obscure wp-content paths to reduce attack surface. If your site uses this kind of hardening and CMS detection does not trigger, your standard audit results are still fully accurate — you simply will not see the WordPress-specific layer of checks on top of them.
For sites that are detected correctly, the WordPress-specific checks provide a fast, zero-configuration way to catch the most common CMS-level SEO issues before they have a chance to compound. SEO plugin misconfigurations, theme performance problems, and sitemap gaps are all issues that standard HTML-level checks will not catch — they require understanding how WordPress is supposed to work to recognize when it is not working correctly. That is exactly what the CMS detection layer is designed to surface.