When to use this
Legal pages are Step 5 in setup on Pro and Growth plans. GDPRChecker asks for URLs to your privacy policy, cookie policy, and terms of use so the consent banner and scanner can link visitors to accurate disclosures. This step is about discoverability and verification—not generating lawyer-drafted text. You remain responsible for policy content; GDPRChecker confirms the URLs respond over HTTPS and match patterns expected for compliance scanning.
Configure legal settings per site from the Sites area or the dedicated legal settings flow referenced in setup. On Growth, Step 5 follows Step 4 Tracker Blocking because policy links often reference your cookie categories and enforcement approach. On Pro, Step 4 is optional, so Legal Pages can continue after Step 3 Consent Banner.
Re-run verification when you migrate policies to a new CMS path or rebrand domains; broken policy links fail scans and undermine trust signals on your compliance report.
Banner preference centers should hyperlink to the same policy URLs you verified—mismatched hosts confuse visitors and fail automated link consistency checks.
Version dates visible on policy pages help demonstrate accountability; verification does not parse legal quality but humans reviewing scans will notice outdated years.
Step-by-step instructions
- Draft or update your privacy and cookie policies with counsel if needed—GDPRChecker does not replace legal review.
- Open your site’s Legal settings in the dashboard and enter HTTPS URLs for privacy, cookie, and terms pages.
- Ensure each URL returns 200 without login walls for anonymous visitors.
- Add footer links on your live site pointing to the same URLs for consistency with scanner expectations.
- Click Verify or run the built-in fetch check for each policy field.
- Fix redirects that loop or return 403 from bot protection—allow GDPRChecker fetch user-agent if your WAF filters automated checks.
- Download or preview the legal settings summary if your workflow needs audit copies.
- Confirm Step 5 · Legal Pages marks complete in the setup wizard.
- Proceed to Step 6 · Runtime Verification—legal completion is required before runtime verification unlocks on Pro and Growth.
Expected result
All three policy types are stored in legalSettingsJson for the site, verification timestamps record success, and setup Step 5 completes. Public scans and compliance reports can cite working policy URLs. Banner preference panels can link visitors to the same documents you verified.
If a policy is genuinely hosted by a parent company, use that canonical URL but document the relationship in the policy text itself.
After major product launches, re-verify legal URLs even when copy unchanged—CMS migrations often break paths silently while banners still link old slugs.
Troubleshooting
Verification fetch failed
Open the URL in incognito. Fix mixed content, cert errors, and geo-blocks. Some cookie banners block policy pages until accept—policies should remain reachable without prior consent.
Cookie policy URL same as privacy
Separate pages are preferred when cookies are discussed in depth. If combined, ensure the single page has a dedicated cookies section and enter that URL in both fields only if accurate.
Step 5 locked
Complete Step 3 Consent Banner first. On Growth, also complete or review Step 4 Tracker Blocking if it is required by your plan state. Publish banner if blocking depends on category labels referenced in policies.
Step 5 not in my wizard
Legal Pages setup requires Pro or Growth. Free accounts do not have the setup wizard — upgrade to Pro to add a protected website and unlock Step 5.