Legal pages are the part of a website everyone ships last and audits never. The pattern on real Divi sites is remarkably consistent: a privacy policy pasted from a generator years ago, a terms page that references a company name from two rebrands back, and a contact form quietly loading a third-party script the policy has never heard of. Nobody notices — until a customer, a regulator, or a platform review does.
First, the disclaimer that is also just true: we are not lawyers, and no plugin replaces one. What software can do is the part lawyers are too expensive for — checking, mechanically and repeatedly, that the legal furniture exists, is published, is linked, and is not contradicted by what the site actually does.
The legal pages a Divi site is expected to have
- Privacy policy — what data you collect, why, who processes it, and the user’s rights. GDPR made this mandatory for anyone with European visitors, which on the internet means you.
- Terms of use — what you promise, what you disclaim, and the rules of engagement, particularly if you sell anything.
- Accessibility statement — increasingly expected, and in parts of the world required. It is a claim, and claims can be checked (more below).
- Working links to all of the above — a policy that exists but is linked from nowhere fails at its one job.
Where sites actually get burned: the gap
The dangerous failure is rarely a missing page — it is the gap between what the policy says and what the site does. The policy discloses Google Analytics; the site also loads a heat-mapper, a chat widget and a font CDN, each with its own data story. The accessibility statement claims WCAG conformance; the accessibility audit finds forty findings. Every one of those gaps is a document contradicting reality in writing, which is the worst kind of paper trail to be generating automatically.
What the legal audit checks
Divi Autopilot’s legal audit reads the whole site once and reports on exactly this gap. It checks that the expected documents exist, are published and are actually linked; it inventories the third-party tags the site really loads — not the ones you remember adding — so you can compare that list against what the privacy policy discloses; and it cross-references your accessibility statement against the accessibility audit’s actual results, so the claim and the evidence live in the same report.
For sites starting from nothing, the plugin can install properly structured legal page scaffolds to fill in — a skeleton with the right sections, not legal advice. Your lawyer reviews the words; the audit keeps checking the plumbing forever after.
Make it a habit, not a project
Legal drift is slow: a plugin update adds a tracker in March, a new form goes live in June, and by December the policy is fiction. This is exactly what scheduled audits are for — the legal check re-runs on cadence, and a new third-party tag shows up as a new finding instead of a surprise. For agencies, the legal section slots into the white-label client report, which turns “we also monitor your compliance pages” into a line item clients are glad to pay for.
Check your own gap today: the legal audit ships with Divi Autopilot. Run it, read the third-party tag inventory, and see whether your privacy policy would recognize your own website.