A cannabis retailer has to verify age before showing products. That is not negotiable and this article does not suggest otherwise. But the way a gate is built decides whether it stands between a visitor and your products for three seconds, or between a search engine and your entire website permanently.
Plenty of sites are in the second situation without knowing it. The gate looks fine to a person. It is opaque to a crawler.
How the trouble shows up
The signature is a site that seems to exist and seems to be invisible. Pages you know are published cannot be found by searching for their exact text. The homepage might appear with a description that does not match its content, or with no description at all. Nothing errors. There is simply nothing there.
The gate patterns that cause it
The redirect gate
A first-time visitor asking for any page is sent to a separate verification address instead. Only after confirming are they returned. A crawler arrives with no history, so it is treated as a first-time visitor every single time. It asks for a product page and is answered with the gate. Do that across a site and every address resolves to the same short document.
The blocking overlay
The page address stays correct, but the content underneath is not written into the page until the visitor confirms. The document that gets delivered contains a gate and an empty shell. The products are added afterwards, by script, in response to a click that never happens.
The gate that hides content behind a stored flag
A subtler version. The page renders fully, but only when a previously stored confirmation is present. No stored confirmation, no content. A crawler stores nothing between visits, so it never qualifies.
The common thread is not the gate itself. It is making the delivery of the page conditional on an interaction.
What Google actually recommends
Google’s SafeSearch documentation addresses this directly. For content behind a mandatory age gate, it recommends that site owners allow Googlebot to crawl the content without triggering the gate.
That is the resolution to the apparent conflict, and it is worth being precise about what it is and is not. This is guidance on crawling, not a claim that anything here is a ranking factor, and nothing in it suggests relaxing verification for people. Human visitors still get the gate. The recommendation is that the crawler is not what the gate is for.
What a crawlable gate looks like
The principle is simple to state: the page arrives complete, and the gate sits on top of it.
In practice that means the address never changes. Asking for a product page returns that product page, with a successful response, containing the real product content in the delivered document. The verification prompt is layered over that content rather than substituted for it. A person sees the prompt and must answer it before interacting. The document underneath was already sent.
It also means the confirmation is remembered in a way that does not gate delivery. Storing the answer so a returning shopper is not asked again on every page is good for the shopper. What matters is that the absence of a stored answer changes what is layered on top, not whether the content was sent at all.
Buddy ships a branded age gate by default, so this is handled at the platform level rather than being something each retailer has to get right on their own. The rest of what sits alongside it is on the compliance page.
How to test yours
Three checks, none of which need a developer.
View the delivered source. Open a product page in a fresh private browsing window, clear the gate, then use your browser’s “view page source” option, which shows the document as it was delivered rather than as it now appears. Search that source for the product name. If the name is not in it, the content is being added after delivery, and a crawler may not see it.
Watch the address. In a fresh private window, paste the address of a deep page, not the homepage, and press enter. If the address bar changes to a verification address, you have a redirect gate.
Search for exact text. Take an unusual sentence from a product or category page and search for it in quotes. If a page has been published for a while and nothing comes back, something is preventing the page from being read.
If a check fails, the fix is a build question rather than a policy question. Nobody has to choose between verifying age and being findable. The pages just have to be delivered whole, with the gate placed over them rather than in front of them. What that unlocks is covered in how Buddy handles cannabis SEO, and the retailer overview shows where the storefront fits around it.
Age verification requirements are set by state regulators and vary. This article is informational and is not legal advice; confirm your obligations with your state regulator or your own counsel.