Dispensary site checker: see your site the way Google does
Ten checks against the HTML a crawler actually receives, not the page your browser draws. It finds the menu Google cannot read, the age gate blocking the crawler, and the compliance language nobody has reviewed since it was written.
Check what Google can actually see
Enter a page from your dispensary site and choose what to check. The scan runs live against the page a search engine receives.
No signup required. The scan reads one public page and stores nothing beyond the report.
01What each of the ten checks is looking for
Each one exists because it has cost a real dispensary real visibility. They are ordered by how much damage they do rather than by how technical they sound.
Whether your products reach the HTML at all. It detects the major menu platforms, works out whether the embed is an iframe or JavaScript, and counts how many product terms, brand names, and prices survive into the source.
Whether the 21 plus check is an overlay drawn on top of a loaded page, or a server side redirect that sends the crawler somewhere different from your customers.
Reads the visible copy for medical claims, potency promotion, price inducements, and language that could be read as appealing to under 21s.
How much of the page exists before scripts run. It compares the raw HTML against what a rendered page would contain and reports the proportion that is genuinely there.
Looks for the address, phone number, and opening hours in the source, and for LocalBusiness structured data describing the store.
Robots directives, canonical tags, and whether the page allows itself to be indexed at all.
Title, meta description, heading structure, and image coverage. The unglamorous layer everything else sits on.
Page size, script count, and the third party payload that drags Core Web Vitals down.
02Reading the result without panicking
A scan will usually return several flags, and they are not equally urgent. Working through them in the order they appear on screen is the wrong approach, because the list is grouped by check rather than by cost.
Anything red under menu visibility, age gate, or indexability. These three block search entirely rather than reducing performance, and none of the other work pays off until they are cleared.
Compliance flags and heavy JavaScript dependency. Neither stops you ranking today, and both carry a cost that compounds: one is regulatory exposure, the other is content Google may never fully read.
On page basics, local signals, and page weight. Real improvements, genuinely worth doing, and none of them will change your quarter on their own.
A page that fails on menu visibility does not need better content. It needs the menu fixed, and then the content will finally count for something.
03Why what Google sees is not what you see
When you open your own site, your browser requests the HTML, then runs every script, waits for the menu platform to return its data, applies your age gate, and draws a finished page. That takes a second or two and you never think about it.
A crawler takes the HTML and reads it immediately. Rendering happens later, on a separate pass, and is not guaranteed. Content inside an iframe is never credited to your page at all, because it belongs to whichever domain served it.
On most websites the gap between those two views is small. On a dispensary site, where the menu is the product and the menu is usually embedded, the gap is often the whole business.
Open Search Console, run URL Inspection on a menu page, choose Live Test, and read the rendered HTML. Search it for a brand you carry. That is the same view this tool uses, taken from the source that decides your rankings.
04What to do with what you find
Take the first red flag and nothing else. Fix it, scan again, and confirm it cleared before you look at anything below it, because these faults stack: an unreadable menu makes the on page findings meaningless, and a page that cannot be indexed makes everything else theoretical.
If a finding needs a developer, the report is written so you can forward it as it stands. It names the fault rather than describing a symptom, which is the difference between a ticket that gets actioned and one that comes back asking what you mean.
If you run several stores, scan one location page from each. Chains almost always share a template, so a fault on one is usually a fault on all of them, and the fix is one change rather than forty.
Detects which menu platform you run and whether its products actually reach the HTML Google reads. If your menu loads in an…
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…
Questions about the site check
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