To implement age verification on a website properly, put the check at the point of entry, so no explicit content (including thumbnails, previews and embeds) loads before a user passes; route users to the right method for their country; verify the result on your server, not in the browser; and keep written records of what you use and why. Then test it like an attacker would and keep the evidence.
The steps below follow the order a developer and compliance lead would work through together. They are written with the UK Online Safety Act in mind, as it has the most detailed guidance, with notes for France, Italy and Germany.
General information, not legal advice. Confirm the rules for each country you target.
Step 1: Map what must sit behind the check
Start with an inventory of every page and asset type on your site and decide which are pornographic. Under the Online Safety Act Part 5, the duty covers pornographic content you publish or display, and the Act specifically includes:
- content that is only visible after a user clicks through blurred, distorted or obscured content;
- embedded content, such as a video player pulled from another site;
- content generated by an AI tool on your service in response to a user's prompt.
Text-only content is excluded from Part 5, but the images and video around it are not. Remember that content does not need nudity to be pornographic: the test is whether it is reasonable to assume it was produced solely or principally for sexual arousal, and titles and captions count.
Age verification before content: where to place the gate
Ofcom's January 2026 note on why age check placement matters describes four common designs:
| Gate type | What users see before the check | Ofcom's view |
|---|---|---|
| Front gate | A landing page with no content | The safest approach for dedicated adult sites |
| Blur gate | Blurred thumbnails, sometimes with titles | Only acceptable if blurring is strong enough that nothing visible is pornographic |
| Image gate | Clear, non-explicit images and titles | Every image, preview and title shown must be non-pornographic |
| In-video gate | Part of a video before the check | Higher risk; stopping before nudity does not make earlier footage non-pornographic |
For user-generated adult services, Ofcom expects the check at the point of entry. If you are unsure, use a front gate.
Step 2: Decide your geo-targeting by jurisdiction
Different countries need different flows. Build a routing table that maps each country to the methods and settings you will use. A typical starting point:
- UK: methods capable of being "highly effective", such as facial estimation with a challenge age, photo ID, open banking, mobile operator or credit card checks.
- France: a flow meeting Arcom's technical standard, including at least one double-anonymity option.
- Italy: an AGCOM-compliant certified third party with double anonymity, repeated at each access.
- Germany: a KJM-assessed system for closed user groups.
- Everywhere else: decide whether to verify everyone (simplest and safest), apply the strictest standard across the board, or geo-block markets you do not want to serve.
Use a reputable IP geolocation source, and decide what happens when location is unknown. The safe default is to apply your strictest flow.
Step 3: Choose and contract your provider
Select a certified vendor whose methods cover your routing table, and sign a data processing agreement before any user data flows. Our guide to choosing an age verification provider has a full checklist.
Step 4: Age verification integration steps
- Serve the gate from your server. Do not load explicit content and then hide it with JavaScript or CSS; a user can disable scripts or read the page source. The content should not reach the browser until the user has passed.
- Send users to the vendor flow by redirect, embedded widget or SDK, passing a session reference but no unnecessary personal data.
- Receive the result server-side. Accept only signed tokens or server-to-server callbacks, check the signature and expiry, and bind the result to the user's session.
- Set a session or reusable credential according to each country's rules. Italy expects checks at each access; elsewhere, a session lasting a reasonable time, or a reusable token, may be acceptable.
- Fail closed. If the vendor is unavailable, the user should see a holding page, not the content.
- Protect every route. Gate direct media URLs, CDN links, RSS feeds, sitemaps with image previews, APIs and mobile apps, not just HTML pages. Signed, short-lived media URLs help.
Step 5: Age check page design
The landing page in front of the gate is both a compliance and a conversion asset. Good practice:
- Show only non-explicit material: your brand, a plain description of the service, pricing and help links.
- Explain in one or two sentences why the check is required and what data is processed, linking to your privacy notice.
- Offer more than one method, with the quickest first, and say how long each takes.
- Make it work on small screens, with large buttons and camera prompts that explain themselves.
- Never suggest ways to get around the check, such as VPNs. Ofcom's guidance says providers should not encourage children to circumvent age assurance.
For tactics that keep more users moving through the flow, see reducing age verification drop-off.
Step 6: Record keeping and privacy
Section 81 of the Online Safety Act requires adult content providers to keep a written, easily understandable record of the kinds of age verification or estimation they use and how they use them, including how they considered users' privacy when choosing them. You must also publish a summary of that record. In practice, keep:
- your content inventory and gate placement decisions;
- your country routing table and the reasons for each method;
- vendor due diligence, certificates and contracts;
- your data protection impact assessment and privacy notice;
- change logs whenever you alter methods, thresholds or placement.
Keep logs that show a check took place for each session, but not the user's identity or images. Our guide to age verification and GDPR explains how to minimise data.
Step 7: Testing and audit evidence
Before launch, and again after every significant change, test the flow as a determined teenager would:
- visit every content type in a private window and confirm nothing explicit loads before the check;
- try direct media URLs, old bookmarked links, search engine image results and shared links;
- disable JavaScript and inspect the page source;
- tamper with the result token and replay old tokens;
- test from each target country, including with location unknown;
- test on low-end mobile devices and slow connections.
Save screenshots, test scripts and results with dates. That bundle is the audit evidence you will want if Ofcom or another regulator sends an information request, and Ofcom has fined providers for failing to respond to such requests.
Step 8: Monitor, review and update
Age verification is not a launch-and-forget project. Rules, vendor models and your own site all change, so build a light review cycle:
- Weekly: watch completion rates by method and country, vendor error rates and support tickets. A sudden drop often means a broken integration rather than user behaviour.
- Monthly: re-run your logged-out test of new pages, templates and content types, especially after a redesign, CMS update or new CDN.
- Quarterly: check regulator updates in each market and confirm your vendor has made any required changes.
- Annually: repeat vendor due diligence, refresh your DPIA and update the published summary of your age assurance record.
Assign a named owner for each task. When a regulator asks who is responsible for age assurance, "the developers" is not a good answer. Business partners may ask too: white-label providers, payment processors and affiliate programs can ask how your gate works before they approve you, and a clear owner and paper trail make that conversation short.
Common mistake: gating the video pages but leaving explicit thumbnails on category pages, tag pages and the home page. Regulators look at what a logged-out visitor sees first.
Frequently asked questions
Can I use a WordPress age gate plugin?
A plugin that shows an "Are you over 18?" pop-up is self-declaration and does not meet UK or EU standards for adult content. Plugins that integrate a certified vendor and block content server-side can work, but test them carefully, especially for caching and direct media URLs.
How long can a verified session last?
The UK rules do not set a fixed period, but the session must not let a child easily use an adult's verification. Italy expects checks at each access. Choose a period you can justify and record your reasoning.
Do I need to verify users who are already logged in?
Members verified once can usually stay verified on their account, provided the account is protected and the original check met the standard. Treat logged-out visitors as unverified.
Next steps
If you are still choosing a vendor, compare certified options in our compliance and verification services directory. For the wider picture, start at our age verification hub.