Key Takeaways
- Google does not crawl iframe menu content as part of your site.
- That hides your entire product catalog from search.
- A reverse proxy serves your menu under your own domain.
- Google then crawls, indexes, and credits those products to you.
- Skipping the proxy hands product rankings to your menu provider.
- Schema markup and 21+ compliance still matter at every step.
Introduction
In a market built on shadowbans and strict rules, an invisible menu quietly kills growth.
Most dispensaries never see it coming. Their menu looks perfect to shoppers. Google sees none of it.
Here is the part that stings. The content already exists, but it lives on the wrong domain, so your own site gets zero credit. The fix is not a full rebuild, and our team uses it inside every dispensary SEO strategy we run.
Quick note before we dig in. This guide covers marketing strategy, not legal advice. Cannabis advertising rules vary by state, and every campaign must respect 21+ age-gating and local regulations.
So why can’t Google see the menu that powers your whole business?
What an Iframe Menu Really Is
An iframe is a window inside your website. It loads content from another company’s server and shows it on your page.
Most dispensaries use one without knowing the cost. Your menu provider hands you a single line of code. You paste it in, and the inventory appears.
Shoppers see products just fine. Prices load, categories show, and orders go through. Everything looks healthy on the surface, which is exactly why the SEO damage stays hidden for so long.
So what is Google actually doing with that menu?
Why Google Does Not Crawl Your Iframe Menu
Google indexes the content that lives in your page’s own HTML. You can see this in Google’s guide to how Search works, which walks through crawling, rendering, and indexing.
An iframe breaks that chain. The menu loads from your provider’s domain, not yours. So that content is not part of your page, and Google does not index it under your site.
This is not a rare edge case. Google warns that embedded loading methods can hide content from search, as it explains in its guidance on lazy-loaded content.
Even the menu platforms admit it. The provider Dutchie notes in its own SEO documentation that a basic embedded iframe menu is only partially indexed by Google.
Partial is not enough. Every strain, edible, and pre-roll sits trapped inside that frame. When a shopper searches for a product you carry, your competitor’s domain wins the click.
That is a huge missed opportunity. Good news: there is a clean fix.
The Missed Opportunity: No Reverse Proxy
A reverse proxy changes who gets the credit. It is the difference between hiding your catalog and ranking with it.
Think of a reverse proxy as a smart middle layer. It sits between your visitor and your menu provider, then serves the menu content from your own domain.
To Google, the menu now looks like a normal part of your website. The product pages live at your URLs, such as yourdispensary.com/menu/, rather than on the provider’s domain.
Dutchie offers this exact setup. Its proxy configuration makes the storefront menu appear as part of your root domain to search engines, per its own documentation. That single shift turns hidden inventory into crawlable, rankable pages.
Expert Insight: Your Catalog Is Your Biggest Content Asset
Most agencies treat a dispensary menu as a checkout tool. We treat it as your largest body of keyword-rich content. A single menu can hold hundreds of product pages, and each one is a chance to rank for real buyer searches. Inside an iframe, that content builds authority for your provider, not for you. A reverse proxy flips the credit back to your domain, so the inventory you already stock starts working as an SEO engine.
So how does the proxy actually pull this off? Let’s break it down.
How a Reverse Proxy Works
The process is simple once you see the steps. Here is what happens behind the scenes:
- A visitor or Googlebot requests your menu page at your own domain.
- Your server, acting as the proxy, fetches the live menu from your provider.
- It serves that menu content back under your domain and your URLs.
- Google crawls those pages as first-party content on your site.
- Product names, categories, and schema now build your domain’s authority.
The shopping experience does not change. The transaction still runs through your trusted provider.
What changes is ownership. Your products finally rank for your business, not someone else’s.
Ready to see the gap side by side?
Iframe Embed vs Reverse Proxy
The contrast is stark once you compare them directly.
| Factor | Iframe Embed | Reverse Proxy |
| Crawled as part of your site | No | Yes |
| Keyword credit | Goes to the provider | Stays on your domain |
| Product pages indexed | Rarely | Reliably |
| Schema markup control | Limited | Full |
| Analytics ownership | Provider | You |
One column leaks your growth. The other captures it. Here is how to set the better option up the right way.
Setting It Up the Right Way
A reverse proxy is powerful, but the details decide the results. Treat these as your checklist:
- Confirm your menu provider supports a proxy or root-domain integration. Many already do.
- Work with a developer to route the menu through your domain. This is a website development task, not a plugin toggle.
- Add Product schema markup so Google understands each item. The full property list lives at schema.org/Product.
- Follow Google’s rules for product structured data to stay eligible for rich results.
- Keep 21+ age-gating and state compliance built into every page.
Set up well, and your menu stops hiding and starts ranking. Now, let’s answer the questions operators ask most often.
Frequently Asked Questions
Are iframe menus crawlable by Google? Are iframe menus crawlable? Not as part of your site. The content loads from your provider’s domain, so Google does not index it under your URL. Your products stay invisible in search.
Is a reverse proxy better than an iframe for SEO? Is a reverse proxy stronger? Yes, in almost every case. It serves your menu under your own domain, so Google crawls and credits those product pages to your site. That powers real cannabis search engine marketing.
Is a reverse proxy hard to set up? Is it hard? Not with the right team. Many providers already support a proxy or root-domain option. A developer routes the menu through your domain while the checkout stays with your provider.
Is Schema markup still needed with a reverse proxy? Is schema still useful? Yes. Schema markup tells Google what each product is. When paired with a proxy, it can unlock rich results and greater visibility for your full catalog.
Conclusion
Your menu should work as hard as you do. An iframe hands your best content to a provider, while a reverse proxy keeps that content and its rankings on your own domain. Fix the architecture, and organic growth follows.
One last reminder. This article shares a marketing strategy, not legal guidance. Always confirm cannabis advertising rules in your state, keep 21+ age-gating active, and consult qualified compliance or legal counsel before launching any campaign.
Ready to Reclaim Your Menu?
Seedless Media builds compliant dispensary sites that Google can actually read, with reverse-proxy menus that put your products back on your domain. See how our cannabis dispensary SEO approach turns inventory into organic growth. When you want a real plan, schedule a strategy call, and let’s move the needle together.