Divi Autopilot

Audit the whole site

Six auditors — five read every page, legal reads the site — every finding named against the node that broke it.

The six 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 — 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.

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.