Audit the whole site

Seven auditors. Five read every page; legal and Site Health read the install. Every finding is named against the node that broke it.

The seven auditors

Site QA — whether a client can still edit the page. Accessibility — headings, alt text, link text, contrast. Performance — image weight, hotlinked assets, module depth. SEO — headings, meta, links, structure. Design Guardian (Divi 5 sites) — generic CTA copy, auto-rotating sliders and H1 problems on a fixed checklist, plus heading sizes measured against your own type scale. Those five read every page. Legal — the compliance furniture and the tags actually loading, read once at site level. Site Health — the install itself: WordPress, PHP and database versions, pending updates, security posture, database bloat and mail, read once at site level. All seven run from wp-admin with no AI account. 5.0.0 added Divi 5 canvases (off-canvas menus, popups and mega menus) to every scan, a check of Divi 5 interactions, the TLS certificate and domain expiry in Site Health, page-builder performance settings and forms, and which plugin loads which files on each page.

How it reports

Every finding names the page, the node and the rule it broke — not a count. Runs are batched and resumable, so a large site saves progress and continues rather than timing out. A finished run reports what was fixed, what is new and what persists since last time.

What it won’t claim

A clean result is a floor, not a WCAG conformance claim. Where part of a page is generated at render time, the audit says so and withholds the count rather than reporting a false clean. Nothing here is legal advice.

What it costs

Nothing. The seven audit groups ship in the free tier — no API key, no quota, no per-page charge. The fixers are free too. The paid plans add fixing a cause on every page at once, scheduled audits, client reports branded with your name and logo and page building — plans from $99/year, differing only by seats.

A typical first run

Runs are chunked, so a large site saves progress instead of timing out a request. Findings land in the wp-admin tabs and are readable by your assistant over MCP — which is where audits get interesting: ask for the three fixes worth doing first, then schedule the re-run and watch the diff move.

The first audit of a site is usually the most valuable twenty minutes you will spend on it: it turns a vague sense that things could be better into a ranked, fixable list. Every audit after that gives you a measured diff: what was fixed, what is new, what is still there. You can put that in front of a client without translating it.

Not only Divi. Every audit here reads stored content and the install rather than a theme’s markup, so the same audits run on Elementor pages and plain block sites as well, apart from Design Guardian, which needs Divi 5 — and Site Health needs no page builder at all. What differs is the fix: on Divi a finding carries the node id this plugin can rewrite itself, and on Elementor it carries the element id, with alt text, heading level, link text and element settings written through Elementor’s own save.

See pricing