Inspect the dispensary's own URLs rather than assuming a menu technology is automatically crawlable or uncrawlable.
Menu rendering and URL ownership. Evidence required: rendered HTML, page source, crawl output, product links, category links, canonical behavior, and inventory synchronization. Pass/fail: pass when important menu information is reliably available on stable first-party pages or through another implementation that search systems can process; fail when essential information exists only in an external interface and the store has no useful owned landing pages.
Severity: critical. Owner: e-commerce engineering or menu-platform owner. Corrective action: change the integration only when the audit proves the current implementation prevents useful first-party coverage.
Validation: recrawl representative products and categories and compare them with the source inventory. See the dispensary SEO overview for broader context. Tools: Dutchie Plus API, Jane Roots, Alpine IQ
Product and LocalBusiness structured data. Evidence required: visible product or store facts, rendered markup, supported properties, and validation output. Pass/fail: pass when markup reflects visible information and validates against current documentation; fail when it is stale, unsupported, misleading, or inconsistent with the page.
Severity: high. Owner: engineering, with merchandising and store operations supplying authoritative data. Corrective action: correct the visible page first, then align markup to the same facts. The source reports a 20-30 percent click-through increase associated with rich snippets, but no supporting URL or method is supplied, so do not use that figure as an expected result. Validation: test live pages and compare parsed values with visible content. Tools: Schema Pro, Google Search Console
Mobile performance. Evidence required: representative PageSpeed Insights results, field data where available, real-device tasks, image payloads, scripts, and interaction traces. Pass/fail: pass when priority menu, store, directions, and ordering tasks remain usable without avoidable technical bottlenecks; fail when measured problems materially obstruct those tasks.
Severity: high. Owner: front-end engineering. Corrective action: reduce avoidable media and script cost, improve caching and delivery, and preserve required compliance behavior. The source's 90+ score is a target example rather than a documented ranking threshold. Validation: repeat the same tests after release. Tools: WP Rocket, Cloudflare, PageSpeed Insights
Age-gate behavior. Evidence required: first-visit customer flow, crawler rendering, session behavior, underlying page access, and applicable legal or compliance requirements. Pass/fail: pass when the gate satisfies the applicable requirement without unnecessarily blocking permitted crawlable content; fail when it prevents access to essential content or provides a noncompliant user experience.
Severity: critical. Owner: engineering with appropriate legal or compliance review. Corrective action: implement the gate around the actual jurisdictional requirement and site architecture. Validation: test both customer and crawler-facing behavior after deployment. Tools: Custom JS Age Gate