Age verification and age gates for escort websites

Declaration or verification?

A declaration asks the visitor to confirm they are eighteen or over and takes their word for it. One click, no personal data, no cost. Verification, which regulators call age assurance, checks the claim: a photo ID matched to a face, facial age estimation, a credit card check, a mobile network operator check, open banking, or a reusable digital identity. Each has a different cost, a different amount of friction and a different privacy profile, and the data involved should be held by the verification provider, not by the website.

Where UK law now sits.

The Online Safety Act 2023 made Ofcom the regulator of online safety in the United Kingdom. In 2025 Ofcom began enforcing duties that require services which allow pornographic content to use highly effective age assurance; a tick box is no longer enough for them. A non-explicit escort or companion website is a different question, and whether a particular site falls within those duties depends on what it shows, where it operates and how the regulator classifies it. The person to answer that is a lawyer with Ofcom’s current guidance in hand. We design the gate; we do not decide which one the law requires of you.

Online Safety Act 2023 (legislation.gov.uk) · Ofcom: online safety

Designing the gate itself.

Make the decision explicit: a clear statement of what the visitor is confirming, a short explanation of what the site is, and two real choices, including a way to leave that works. Remember the answer for the browser session so a returning visitor is not asked twice in an hour. Build it as a proper dialog, with focus held inside it, labels a screen reader can announce and a keyboard path through it. Offer the same entrance to a visitor who prefers less motion. Never hide the content behind the gate from the visitor who has already accepted, and never dress the gate up as something it is not.

What the gate does to search.

Google treats an age gate required by law as an exception to its rule against intrusive interstitials, so the gate itself does not cost you visibility. What costs visibility is a gate that hides the page. The text of each page should be present in the HTML the crawler receives, with the gate on top of it rather than instead of it, and each page should remain distinct behind the gate rather than all showing the same words. Do not mark a non-explicit page with an adult content rating; SafeSearch can filter a whole site on that signal.

What MUMEI builds.

Our default is a declaration designed to the standard above, because for many of our clients that is what applies. When verification is required, we integrate a provider the client selects and design the flow around it, so the check feels like part of the site and the personal data stays with the provider. Either way the entrance is part of the design, not a plugin dropped in front of it.