Dispensary menu visibility checker

01The problem, in one paragraph

Almost every dispensary runs its menu through a third party platform, because building and maintaining compliant inventory software is not a reasonable use of a retailer's time. Dutchie, Jane, Meadow, Tymber, Blaze, and the rest all solve a real problem well. The issue is not the platform. The issue is how that menu gets onto your website, because the standard installation drops it in as an iframe or a JavaScript widget, and both of those hide it from Google.

That means every product name, every brand you carry, every category a customer might search for, sits on your page invisible to the one system deciding whether anyone finds you. You are paying for the menu and receiving none of its search value.

The most valuable content on a dispensary website is usually the content Google cannot see at all.

02Why an iframe costs you everything

An iframe is a window into another website. When your menu loads inside one, the content within it belongs to the provider's domain, not yours. Google understands this perfectly well and attributes that content where it lives, which is somewhere else entirely.

From the crawler's point of view, your menu page contains a heading, some navigation, a footer, and an empty frame. That is a thin page. And thin pages across a multi location site is exactly the pattern that triggers a scaled content manual action, which is how a menu integration decision quietly becomes a penalty six months later.

03The JavaScript version of the same problem

The newer integrations avoid iframes and inject the menu with JavaScript instead. This looks better, and it is better, but it is not solved. Google can render JavaScript, though it does so in a delayed second pass that is slower and less reliable than reading HTML directly.

On a single page site that delay rarely matters. Across a chain with dozens of location and menu pages, it compounds into content that gets indexed late, indexed partially, or missed entirely when crawl budget is under pressure. The check above measures this by looking for product terminology and prices in the raw HTML: if the platform is present but the products are not, the menu is arriving after the crawler has already formed its impression of the page.

04What this actually costs you

Three things, and they compound. First, you rank for almost none of the product and brand searches that drive dispensary traffic. Somebody searching for a specific brand in your city is close to buying, and if your menu is invisible you are not in that result even though you stock it.

Second, your pages look thin, which is the direct precursor to a scaled content penalty across the whole chain. Third, and this is the one that stings, competitors who solved this rank for your inventory. The same products, the same brands, the same city, and their page is the one Google can read.

Fix how the content is delivered before you invest in writing more of it. Rewriting a page Google cannot fully read is how agencies burn a quarter of budget with nothing to show.

05The three ways to fix it

This is the fastest and it requires no developer. Write genuine content into the page HTML around the menu: category descriptions explaining what each product type is and who it suits, brand explainers for the lines you carry, buying guidance for people new to the category, and FAQs answering what local customers actually ask. This does not make the menu visible, but it stops the page being thin, which removes the immediate penalty risk and gives the page something to rank on.

Several menu platforms now offer an SEO friendly hosted version with its own sitemap and server rendered pages. If yours does, enabling it is a support ticket rather than a project. The detail that gets missed is what happens afterwards: the canonical tags, internal linking, and sitemap all need to be set up deliberately so the indexed version sits under your brand rather than ranking separately or not at all.

This is the version that genuinely wins product and brand searches. Pull the product data through the provider's API and render it into your own pages on the server, so the content is in the HTML on first response and belongs entirely to you. It needs a developer and it needs maintaining as the API changes, but for a chain of any size the return justifies it comfortably.

06Verifying 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 Live Test, and read the rendered HTML. If your product and brand names are absent there, or appear only inside an iframe pointing at another domain, the finding is confirmed from the source that matters.

There is a faster version for a quick sanity check: disable JavaScript in your browser and reload the page. Whatever disappears is roughly what the crawler struggles with on its first pass. If the entire menu vanishes and you are left with a heading and a footer, you have your answer in about ten seconds.

This checks the page you submit. Menu integration is usually consistent across a site, so one page is generally representative, but it is worth checking a location page and a category page separately if they are built differently.

Scans a page the way a search engine sees it. Finds embedded menus Google cannot read, age gates blocking the crawler, and…

Reads your sitemap, finds every location page, and measures how similar they are to each other. This is the scaled content risk…

Paste any marketing copy and see the medical claims, potency language, and youth appeal that get dispensary marketing pulled. Runs entirely in…