Skip to content
Free tool

Dispensary Menu Visibility Checker

Paste a menu or location page. The check names the menu platform, shows how the menu reaches the page, and counts how many products, prices and potency figures are in the HTML a crawler first receives.

Menu Visibility Check

Is Your Menu In The HTML Google Reads?

Use a page where your product menu appears, not the homepage. The check reads the HTML exactly as a crawler first receives it, before any script runs.

6 checks, no scripts run
The full explanation
The Short Version
  • Most dispensary menus load in a frame or a script, so the products are not in the HTML a crawler first receives.
  • Google may still count some of it, but only after extra steps it does not guarantee, and the page itself reads as thin.
  • There are three fixes, and one of them does not need a developer.
Check your menu 20 seconds, free

01 The Problem, In One Paragraph

Most dispensaries run their menu through a third party platform, and for good reason. Building compliant inventory software is not a retailer's job. Dutchie, Jane, Meadow, Tymber and Blaze all solve that problem well, and a Weedmaps or Leafly embed serves the same purpose.

The issue is not the platform. The issue is how the menu reaches your website. The standard installation drops it in as a frame or a script, so the products are not in the HTML your page returns. Google can sometimes still count them, after extra steps it does not guarantee. A crawler that only reads the HTML never will.

Key FactEvery product name, brand and category a customer might search for is missing from the HTML of the page that should rank for it. You are paying for the menu and getting only part of its search value, at best.

02 What An Iframe Does To The Page

An iframe is a window into another website. When your menu loads inside one, the products live at the provider's addresses, not yours. Google says it tries to count a frame's content as part of the page that holds it, but does not guarantee it, and Google's John Mueller has advised putting content you want indexed with a page directly into that page.

InstallationWhat Google Sees
iframe embedA frame pointing at the provider's domain. Maybe counted as part of your page after rendering, with no guarantee. The menu's own pages rank for the provider.
JavaScript widgetDepends on rendering. Google renders scripts, but it is an extra step that can fail, and most other crawlers do not run scripts.
Native or API menuReal HTML on your own domain. Products, brands and categories all indexable.
Worth KnowingBefore anything renders, an iframed menu page holds a heading, some navigation, a footer, and an empty frame. That is a thin page, and a chain of near identical thin pages reads as a template, which is what the similarity checker measures.

03 The JavaScript Version Of The Same Problem

Some integrations avoid frames and draw the menu into your page with JavaScript instead. That is better, and it is still not solved. Google renders JavaScript, usually soon after crawling, but rendering is an extra step that can time out or fail, and ChatGPT's, Claude's and Perplexity's crawlers make no promise to run scripts at all.

On one page that rarely matters. Across a chain with dozens of location and menu pages, anything that has to be rendered before it counts is more likely to be counted late, or partly.

The check above measures this directly. It counts prices, potency figures and weights in the HTML the page returns. If the platform is present but the products are not, the menu depends on a script or a frame to exist at all.

04 What This Actually Costs You

Three costs, and they compound.

The Product Searches You Never Enter

Somebody searching a specific brand in your city is close to buying. If your menu is invisible, you are not in that result even though you stock it.

The Thin Page Risk

A page that holds a heading, a footer and an empty frame gives Google little reason to rank it, and a chain of them reads as one template.

Competitors Rank For Your Inventory

Same products, same brands, same city. Their page is the one Google can read. This is the cost that stings.

Key FactContent around the embed is the quickest win, but it does not put a single product into the HTML. Plan the delivery fix alongside it, or the menu itself stays where it is.

05 The Three Ways To Fix It

1

Build Real Content Around The Embed

The fastest path, no developer needed. Category descriptions, brand explainers, buying guidance and local FAQs written into the page HTML. The menu itself does not change, but the page stops being thin and has something of its own to rank on.

2

Turn On The Platform's SEO Option

Some platforms offer a version that serves the menu as part of your own domain. Dutchie's is E-Commerce Pro with its proxy setup. If yours has one, switching starts with the provider and needs some setup on your side, such as the proxy. The part that gets missed comes afterwards: canonicals, internal links and the sitemap need deliberate setup so the indexed pages sit under your brand. Why a Dutchie menu stays invisible walks through the most common case.

3

Go Native With An API Menu Build

The version with the most control. Product data pulled through the provider's API and rendered into your own pages on the server, so the content is in the HTML on first response and belongs entirely to you. Jane calls its version Roots. It needs a developer, and for a chain it is usually part of a multi location engagement rather than a single fix.

Not sure which installation you have? The checker names it from one URL.Run the check

06 Verifying This Yourself

You do not have to take this tool's word for it, and you should not. Open Search Console, run URL Inspection on a menu page, choose Test Live URL, then View Tested Page and read the HTML. If your product and brand names are absent there, or there is only a frame pointing at another domain, the finding is confirmed with Google's own tool.

There is a ten second version. Disable JavaScript in your browser and reload the page. Whatever disappears is what a crawler that does not run scripts never sees. If the whole menu vanishes, you have your answer.

Worth KnowingThis checks the page you submit. Menu pages and location pages are often built differently, so check one of each, and the site check reads the rest of the page while you are at it.

07 Where Menu Visibility Fits In Dispensary SEO

Menu visibility is where dispensary menu SEO starts, and the first thing an audit checks, because nothing downstream matters until it is fixed. Content, links and profiles all assume Google can read the page they point at.

Cannabis SEO for dispensaries usually starts here, and the dispensary SEO service plans the menu fix from the start, alongside the content.

If the check flagged your menu and you want the full picture, the free audit reads the whole site and puts the menu finding in order against everything else.

From the accounts

On a fifty store chain we audited, the menu had been embedded the same way on every location page for three years. Search Console showed the pages indexed and the team assumed that meant fine. Not one product or brand name appeared in the rendered HTML, so the site ranked for the brand and for nothing else. The fix was scoped in a week; the three years of missed product searches were not recoverable.

Questions

Questions About Menu Visibility

The standard Dutchie embed is a script that opens the menu in a frame, so the HTML your page returns holds a heading, some text and an empty container, and the products load afterwards. Google says it tries to count a frame's content as part of the page that holds it, but does not guarantee it, and Dutchie itself describes its embedded menu as partially indexed. For the products to be reliably yours, they have to be in your own HTML: Dutchie's E-Commerce Pro with its proxy setup, or an API build.
Built in often refers to a separate option, such as Dutchie's E-Commerce Pro with a proxy, rather than the standard embed. If you run the standard embed, you still have the frame. Run the check above, then use URL Inspection in Search Console on the same page to see whether the products are in the HTML Google tested.
In Search Console, open Indexing, then Pages, and look for your menu addresses. With Dutchie's embed, product views on your site carry dtche in the address, which makes them easy to spot. Search Console only shows addresses on your own domain, so a menu hosted on the provider's domain never appears there. To see which domain ranks, search Google for a product you stock with your store name.
Sometimes. Google says its systems try to count a frame's content as part of the page that embeds it, but that it is not guaranteed, and Google's John Mueller has advised putting content you want indexed with a page directly into that page rather than relying on a frame. The framed menu's own addresses also sit on the provider's domain, so the pages that rank for a product there are theirs.
Neither platform is better or worse by itself. What matters is which installation you chose. Both have a standard embed that opens the menu in a frame, and both have a route to a menu on your own domain: E-Commerce Pro with a proxy for Dutchie, and Roots, a headless build, for Jane. Two stores on the same platform can get opposite results because of that one choice.
Usually not, and it is an expensive way to find out. Dutchie's and Jane's standard installs are both framed embeds, so you can change vendors and keep exactly the same problem. Fix the installation you have first. Switch platforms for business reasons, not for this.
Not on its own. Menu rendering is usually the ceiling rather than the whole problem. Once Google can read the products, the pages still need real content, working local signals, and links. The difference is that after the fix, that work finally counts.
If you use a platform's SEO menu option, ask whether it provides one. Dutchie, for one, hosts that sitemap on its own domain and has you reference it from your robots.txt file. It covers menu URLs only, so keep your regular sitemap as well.
Run URL Inspection on a menu page, choose Test Live URL, then View Tested Page and open the HTML. Search it for a brand you stock. If it is missing, or there is only a frame pointing at another domain, you have confirmed the finding with Google's own tool.
It is workable, but it needs deliberate setup. Google can treat a subdomain as a site of its own, so its rankings do not automatically strengthen your main domain. Internal linking, canonicals and consistent branding decide whether the subdomain helps you or just competes with you. Run this check on the storefront page itself as well.

A menu rendering fix is usually a development project rather than a setting. How the technical work is scoped →

Found Something And Not Sure How Serious It Is?

Send the domain and what the check flagged. You will get a written read on what it is costing you and what to fix first.

Get Your Free Audit