Build the age gate as a JavaScript overlay on top of the real page, offer a one-tap yes/no instead of a birthdate form, and set a remember-me cookie so nobody verifies twice. Done that way the gate satisfies the requirement, crawlers still see your content, and almost nobody leaves. This is general information, not legal advice.
Use an overlay, never a redirect
There are two ways to build a gate, and one of them quietly damages your whole site. A redirect gate sends every visitor — and every crawler — to a separate verification URL before showing anything. Googlebot does not click "yes, I am 21." If verification stands between the crawler and your pages, what gets indexed is a verification page.
A JavaScript overlay works differently. The real page loads at its real URL with all content in the HTML; the gate is a layer painted on top. Humans tap through it. Crawlers, which do not execute the dismissal, read the full page underneath. Same legal function, none of the SEO damage.
One tap beats a birthdate form
A date-of-birth form asks for three fields of typing on a phone screen to establish exactly what a "Yes, I am 21+" button establishes: an unverified self-certification. The extra typing adds no proof. It adds drop-off.
Unless your jurisdiction specifically calls for date entry, use two big buttons, yes and no, thumb-reachable on mobile. Check the rules where you operate before choosing — some markets are stricter than others.
Remember the visitor
The fastest way to make people hate your site is asking them to confirm their age on every visit, or worse, every page view. Set a cookie when someone passes the gate. Within a session they should never see it again; for returning visitors, a 30-day cookie is a common, reasonable setting. A shopper who verified on Tuesday should not be re-carded on Thursday.
Make the gate load like part of the site
The gate is your first impression, so treat it like one. Brand it, keep the copy to one line, and make sure the overlay appears instantly rather than after a two-second blank stare while a script loads. Skip the extras — newsletter signup, location prompt, cookie banner — stacked into the same moment. One question, one tap, in.
The interstitial question, answered
Site owners sometimes hesitate here because Google penalizes intrusive interstitials on mobile. The concern is misplaced: Google's guidance exempts dialogs required for legal reasons and names age verification as the example. A worked before-and-after makes the stakes concrete. A gate built as a redirect with a birthdate form gives you three typed fields on a phone, a broken back button, and a site Google can barely see past the gate URL. Rebuilt as a branded overlay with yes/no buttons and a 30-day cookie, the same site keeps its indexed pages, direct links work again, and the only people who ever see the gate twice are the ones who cleared their cookies.
Key takeaways
- Overlay, not redirect: crawlers must find the real content in the HTML.
- One-tap yes/no converts better than a birthdate form and proves just as little.
- Set a remember-me cookie so visitors verify once, not every page view.
- Google's interstitial penalty exempts legally required dialogs like age gates.
Frequently asked questions
Does an age gate hurt SEO?
Only if it hides your content from crawlers. A JavaScript overlay leaves the full page in the HTML, so Google indexes everything normally. A gate that redirects every visitor to a verification URL, or renders the page only after approval, can leave Google seeing one thin page for the whole site.
Is an overlay better than a redirect for age verification?
Yes. An overlay sits on top of the real page, keeps the requested URL intact, and disappears on one tap. A redirect sends everyone to a separate gate URL, breaks the direct link the visitor clicked, and hides the real content from crawlers. Overlay wins for both conversions and SEO.
Is a yes/no button enough, or do I need birthdate entry?
In most adult-use markets a self-certification is a self-certification either way, and a birthdate form adds typing without adding proof. One-tap yes/no keeps far more visitors moving. Some jurisdictions do expect date entry, so check the rules where you operate. This is general information, not legal advice.
How long should the remember-me cookie last?
Thirty days is a common, reasonable setting. The gate should never re-challenge a visitor within a session, and returning shoppers should not see it again for weeks. Re-gating people on every page view is the single most conversion-hostile age gate mistake.
Will Google penalize an age gate as an intrusive interstitial?
Google's guidance on intrusive interstitials carves out dialogs shown for legal obligations, and age verification is its named example. A compliant gate is not penalized as an interstitial. The technical implementation still matters, because a gate that blocks rendering can hurt indexing on its own.
Want this done for your brand?
We build cannabis & CBD search visibility with full transparency, for dispensaries, brands, and MSOs.
Get a free cannabis SEO audit ›