A dispensary menu can have a clean design and still create a poor search or customer path. A category may not have a direct URL. A product may disappear when inventory changes. A selected store may not carry across the handoff. A crawl directive may block a page the team expects Google to find.
Start with the real setup, not the platform name. Dutchie and Jane support different products and implementation choices. Your website, age gate, menu settings, page templates, and store operations also affect what customers and search engines can reach.
1. Map the real menu setup before you test it
Write down the menu platform, the customer-facing domain, the URL where a customer enters the menu, the selected location, and the people who can change platform settings, website code, and store details. Then collect a sample of pages from the live customer path.
- One store or location page.
- One category page.
- One in-stock product page.
- One sold-out or discontinued product page.
- One brand page, if the menu offers one.
Keep the URLs in the audit record. A screenshot of the menu home page alone does not show where the customer or crawler goes next.
2. Check direct URLs, content, and index signals
Open each sample URL in a normal browser session. Check the response, page title, main heading, visible product or category information, store context, internal links, canonical tag, and whether the page appears in an applicable sitemap. Then compare what the customer sees with the page source and the reports available in Search Console.
Dutchie’s SEO FAQ describes different options, including embedded menus, Pro + Proxy, storefront subdomains, and custom Dutchie+ builds. It says embedded-menu behavior can be partial and provides platform-specific guidance for its SEO setting and sitemap. Do not treat that guidance as proof that every Dutchie implementation will behave the same way.
Jane’s build-your-own menu documentation recommends separate product URLs and suggests separate category and brand pages. That applies to the documented architecture; verify whether your own implementation has those pages before making a plan.
3. Test the path from the website into ordering
Search and indexing checks are not enough. Test the same URLs on a phone. Start on the store page, choose a category or product, enter the menu, and confirm the selected store stays correct. Then test the desired next action, such as pickup, delivery, or viewing live inventory.
- Does the correct store remain selected?
- Does the category or product path lead to live inventory?
- Can a customer get back to the owned website without losing context?
- Do out-of-stock items explain what happened without creating a dead end?
- Do the call, direction, and ordering paths match the store shown on the page?
The cannabis e-commerce SEO guide explains how the owned site, inventory platform, content, and measurement work together. Use it for strategy after this checklist identifies the broken step.
4. Split the work by who can change it
An audit is more useful when it identifies the owner of the fix. Use this matrix to avoid sending a website issue to a store manager or a vendor-only setting to the development team.
| Check | Menu vendor or settings | Owned website | Developer | Store or marketing team |
|---|---|---|---|---|
| Menu SEO feature or sitemap availability | Confirm the current option and platform documentation. | Reference the menu sitemap only where appropriate. | Implement approved technical changes. | Save the setting and recheck date. |
| Location and menu handoff | Confirm platform location behavior. | Link to the matching store and menu path. | Repair routing or selection persistence if assigned. | Test the real customer journey. |
| Page titles, canonicals, robots, and schema | Document what the platform controls. | Document template and page-level signals. | Evaluate and ship the approved change. | Provide accurate store and product facts. |
| Sold-out products and broken links | Confirm inventory behavior. | Find affected internal links. | Fix template or integration issues. | Report the observed customer problem. |
5. Record the gap and choose the next check
For each finding, save the URL, the observed behavior, customer or search impact, accountable owner, proposed fix, and recheck date. Avoid a vague note such as “menu SEO is bad.” A useful finding names the page and the point of failure.
If the issue is unclear, move one layer at a time: the menu setting, the website link, the page response, the crawl directive, the canonical, the sitemap, and the selected-store behavior. Our cannabis technical SEO service and Dutchie troubleshooting guide can help frame the technical questions.
Use the full visibility checklist after the menu audit
Menu behavior is one part of a larger search-to-order path. Use the free Dispensary Search Visibility Checklist to document the local profile, store page, menu, technical, and measurement gaps your team finds. It gives the team one place to decide what it can fix and what needs to go back to the vendor or web provider.
Frequently asked questions
Does every Dutchie or Jane menu behave the same way for SEO?
No. Results depend on the product, implementation, site architecture, settings, age gate, crawl directives, and the customer path. Inspect the live setup before deciding what needs work.
Should a dispensary remove a canonical tag to make a menu rank?
Do not make that change from a generic checklist. Record the current implementation, read the platform documentation, and have the person responsible for the website evaluate the canonical behavior for the specific page.
Are product URLs enough to solve dispensary menu SEO?
No. URLs are only one part of a customer and crawl path. Check page content, store selection, canonicals, crawl directives, internal links, sitemap discovery, and whether the menu still serves the intended action.
Who should own a menu SEO fix?
The answer depends on the finding. A menu vendor may control platform settings, a web team may control page templates and robots files, a developer may control routing and metadata, and the store or marketing team may own facts and testing.
Need a clear SEO plan for your cannabis business?
We can turn these ideas into a practical plan built around your website, market, and goals.
