Most WordPress age-gate plugins show a pop-up on the page. The files, feeds and sitemaps around it often stay open. These are the gaps our scanner looks for on WordPress sites, each linked to its fix page.
Ofcom's guidance (16 Jan 2025) lists self-declaration as not capable of being highly effective, and its placement guidance describes a front gate with nothing explicit before the check. JMStV § 4 Abs. 2 and Arcom's référentiel describe their own requirements. Which of these applies to your site depends on your visitors. A lawyer can confirm whether that's you.
Sources: Ofcom: Guidance on highly effective age assurance and Part 5 duties (16 Jan 2025, checked 12 Oct 2026) · JMStV § 4 (checked 14 Oct 2026) · Arcom: référentiel announcement (11 Oct 2024, checked 2 Nov 2026)
A plugin decides what the page shows. It usually doesn't protect direct file URLs, sitemaps or the REST API. Our scan checks those separately.
By default, WordPress core exposes a sitemap at /wp-sitemap.xml and a media endpoint at /wp-json/wp/v2/media. Our scan reads both, as No451Bot, and reports what they list.
Most are settings or small server rules. Signed media links add a short check per file request. The fix pages give our time estimates.
No. The checklist covers what our scanner can see. Whether a law applies, and what it asks of your site, is for the regulator and your lawyer.
Not legal advice. This page summarises and links to primary sources; it does not tell you what the law requires of your specific site.