How to Handle Age Gates Without Hurting Cannabis SEO

The redirect gate is the one that kills rankings

There are two ways to build an age gate, and they are not close. The bad one intercepts every request and redirects it to something like /age-check until a cookie is set. Googlebot does not accept cookies or click "Yes, I'm 21," so every URL on the site resolves to the same verification page. Products, guides, the homepage, all of it collapses into one thin page in Google's index.

Sites do this by accident all the time, usually through a compliance plugin installed with default settings. The rankings loss shows up two to six weeks later, long enough that nobody connects it to the plugin.

Build it as an overlay instead

The safe pattern: the server returns the complete page HTML, and a JavaScript overlay covers the viewport asking the visitor to confirm their age. A click sets a cookie or localStorage flag and the overlay never appears again. Crawlers, which do not run the confirmation, still receive and render the full content underneath.

This is not a trick. Users and bots get the same HTML; humans just answer a question before they interact with it. Keep the overlay markup light, load it after the main content, and make sure it does not set noindex or block rendering of anything beneath it.

What Google's interstitial rules actually say

Google's guidance on intrusive interstitials penalizes pop-ups that block content on mobile, with a specific carve-out for interstitials that exist because of a legal obligation, and age verification is the example everyone cites. A compliant overlay gate costs you nothing under that policy. What the exemption does not cover is a gate built so badly the content behind it is never served at all; that is not an interstitial problem, it is a crawling problem, and no exemption saves you from it.

One note on the legal side: verification requirements differ by state and product type, and this is SEO guidance, not legal advice. Confirm your obligations, then implement them with the overlay pattern.

Test it, then re-test after every plugin update

A dispensary client came to us after organic traffic slid for a month. Their theme update had quietly switched the age gate from overlay mode to redirect mode. The diagnosis took five minutes: we opened Search Console, ran URL Inspection on a product page, clicked "Test live URL," and read the rendered HTML. It contained the words "Are you 21 or older?" and nothing else. Switched the gate back to overlay mode, requested reindexing on the key pages, and the pages returned over the following weeks.

Make that check routine. Inspect one product page and one blog post after any change to the gate, the theme, or the compliance plugin. The rendered-HTML view is the ground truth for what Google can see; if your content is in it, the gate is doing no harm.

When the catalog is the product, this is core cannabis ecommerce SEO work.

Frequently asked questions

Is an age gate overlay cloaking?

No. Cloaking means serving different content to crawlers than to people. An overlay serves the identical HTML to everyone; it just asks humans to confirm their age before interacting. Google's own guidance treats legally required interstitials as acceptable.

Does the gate need to appear on every page?

Yes, on every entry point. Search traffic lands deep on product and article pages, not just the homepage, so the overlay has to fire wherever a first-time visitor arrives and then stay out of the way once the cookie is set.

How do I confirm the age gate caused a ranking drop?

Run a live test in Search Console's URL Inspection tool on an affected page and read the rendered HTML. If all Googlebot sees is the age prompt, the gate is the problem. If the full page is there, look elsewhere before blaming the gate.