Updated October 2026
A customer asks a budtender about one of your products, and she isn't sure of the answer, so between transactions she types your brand name into her phone. The only page of yours that comes up asks "Are you 21?" and nothing else. The line is moving, and she points the customer to another jar. You'll never see that moment from your desk, but you can see the age gate your developer built, which is sitting in your inbox waiting for you to sign off.
Whether that gate costs you moments like this one comes down to how it's built, and most of it you can check yourself before you say yes.
The good news is that Google knows a cannabis site has to ask. Its guidance on pop-ups treats an age check as a screen you're required to show, so it doesn't count against you the way an ad covering the page would. What matters is how the gate is put together. If it sits over the product page, Google can still read what's underneath. If every product URL redirects to one /age-check page, Google warns that this "will remove all but that one page from search results." That second kind is what the budtender ran into: as far as Google knows, your site is a single page, and that page says nothing about what you make.
So when you write back, start with one question: how does Google get past the gate? "It clicks yes" isn't a good enough answer, because Google forgets the click. Its renderer clears cookies and storage between page loads, so the cookie that says "this visitor is 21" is gone by the time Google opens your next product page, and it lands on the gate again. For adult sites, Google's own suggestion is simpler: when a visit really comes from Google, show it the page without the gate. The checking part is your developer's job, and Google has a guide for it. All you need to make sure of is that they do check, because anyone can call themselves Google.
Somebody on your team will ask whether that counts as cheating. Google's spam policies call it cloaking when a site shows search engines different content from what people see, to game the rankings. Here Google gets exactly the page an adult sees after clicking yes, so the rule to hand your developer is a short one: same copy, same images, same page.
Before you reply to that email, it's worth an afternoon with your developer running four checks together:
A gate Google can see past only helps if there's something worth finding behind it. Think about what the budtender was looking for with the line moving: the answer to her customer's question, in words she could repeat across the counter. So put the questions customers actually ask about your product on the product page, near the top, and answer them plainly enough that Google can read them and she can say them out loud.
Get both parts right, and the next time she types your name between customers she lands on that product's page, finds the answer in the first few lines and gives it before the line moves on. If you'd like to hear those questions straight from the budtenders who get them, that's what Budtender XP is for.
Does an age gate hurt SEO? Not when it sits over the page, though as of October 2026 Google warns that a gate redirecting every URL to one verification page can leave only that page in its results.
Can Googlebot get past an age gate? For mandatory adult age gates, Google recommends verifying Googlebot requests and serving them the content without the gate.
Is letting Googlebot skip the gate cloaking? No, as long as Google gets the same page an adult visitor sees after confirming their age.
What about ChatGPT, Claude and Perplexity? Each runs its own search crawler, OAI-SearchBot, Claude-SearchBot and PerplexityBot, and a redirect gate shows every one of them nothing but the age check.
Source: Google Search Central. For persons 21 and older. General marketing information, not legal advice.
