Dutchie SEO: Make Your Dispensary Menu Rank on Google | Bud Authority

The visible buyer problem is simple. A customer in Brooklyn opens Google and searches for "Runtz cart Williamsburg." Google returns three results: two competitor dispensaries with server-rendered Shopify menus, and a Leafly listing. The customer clicks one of those three. Your dispensary, which has 14 Runtz carts in stock at this exact moment, is not in the result set. You paid for the inventory, you paid the rent on the storefront, and you paid Dutchie's monthly platform fee — and you are functionally absent from the demand pipeline that is searching for your products by name.

Dutchie SEO fixes the structural cause of that absence. It is not link building, content marketing, or keyword density work. It is a pipeline that converts your live Dutchie catalog into server-rendered, schema-marked, sitemap-indexed product URLs on your own domain, and keeps them in sync as your inventory changes throughout the day. The output is:

• Every in-stock product = a server-rendered URL on your domain
• Every product URL = full Product + Offer schema with availability, price, brand, category
• Every product URL = in your sitemap.xml with <lastmod> reflecting last inventory sync
• Every product = surfaceable in Google Map Pack carousels, Shopping, and AI Overview citations

Cart, checkout, and compliance flows continue to run through Dutchie's authenticated session. Only the discovery surface — the part Google reads — gets rebuilt.

The secondary effect of solving the discovery surface is that the entire site's topical authority lifts. A dispensary with 320 indexed product URLs becomes a deeper authority on cannabis products than a dispensary with six indexed pages. Internal linking distributes that authority across category hubs, brand pages, and location landing pages. Strain-level queries that the dispensary could never realistically rank for as a six-page site become reachable as a 350-page site with structured product data and clean internal architecture. The Dutchie SEO fix is not just about menu pages — it is about converting a single-page-application brochure into a structurally significant cannabis information resource that Google treats accordingly.

Your Dutchie menu isn't showing on Google because Dutchie's default integration is a cross-origin iframe that loads product data client-side after the page renders. Googlebot crawls the parent page, sees an empty iframe shell, and indexes the page without any product content. Cross-origin iframes are not attributed to the parent domain, so even when rendered the product names live on dutchie.com, not your domain. The fix requires server-side rendering: a reverse proxy intercepts requests, calls Dutchie's GraphQL API, injects the product HTML into the page before sending it to the browser or to Googlebot, and emits structured data so the menu is both crawlable and machine-readable.

No. Cross-origin iframes are not indexed by Google as part of the parent page's content. Even when Googlebot fully renders a page using its headless Chromium pipeline, content inside a cross-origin iframe is attributed to the iframe's origin (in this case, dutchie.com), not to the parent URL. This means a dispensary at examplecannabis.com that embeds the Dutchie menu via the standard iframe will never rank for the products inside that menu — Google attributes those products to dutchie.com. Solving this requires bypassing the iframe entirely: fetch the Dutchie data server-side and render it into the dispensary's own HTML, then index the dispensary domain as the canonical source for those products.

Apex MenuEdge is Bud Authority's proprietary Cloudflare Worker that solves the iframe indexation problem at the edge layer. When a request hits the dispensary's /shop, /menu, or product detail URL, MenuEdge intercepts the request before it reaches the origin, calls Dutchie's GraphQL endpoint server-side with the dispensary's retailer ID, transforms the product JSON into fully-formed HTML with Product schema, and returns the merged response to the browser or crawler. Googlebot sees a complete HTML document with all products inline. The user sees the same page hydrate normally and inherit the Dutchie cart and checkout flow.

Three properties make MenuEdge structurally different from typical "static menu generators":

1. 1Edge-cached but inventory-fresh. MenuEdge runs at every Cloudflare PoP. Cache TTL is bound to Dutchie's product mutation events — when inventory changes, the cache invalidates within 60 seconds.
2. 2No origin code changes. MenuEdge sits in front of any origin: WordPress, Webflow, Next.js, Squarespace. The dispensary keeps its existing site and gets indexable menus by DNS pointing.
3. 3Schema is emitted, not bolted on. `Product`, `Offer`, `aggregateRating`, `priceCurrency`, and `availability` schema are generated from the same GraphQL response that drives the visible HTML, so structured data is never out of sync with the menu.

A fourth property worth noting separately: MenuEdge is the only reverse-proxy menu solution in the cannabis market that ships with a documented schema generation pipeline tested against the Google Rich Results Test, Schema.org validator, and Schema Markup Validator on every deploy. Most attempts at indexable Dutchie menus we have audited in competitor work emit schema that fails validation — missing priceCurrency, malformed availability enums, or Product entries without offers blocks. These fail silently in Google Search Console as "Invalid items" and do not surface in Shopping, Map Pack product carousels, or AI Overview citations even though the HTML renders correctly to human visitors.

Full technical specification, deployment timelines, and pricing for MenuEdge as a standalone product are on /apex-menuedge. This page describes MenuEdge as one component inside the Dutchie SEO service; the product page describes MenuEdge as a product.

These are two adjacent but distinct services. Dutchie SEO applies to the standard Dutchie embed — the iframe integration used by the majority of dispensaries on the platform. The work is to bypass the iframe with a reverse proxy and emit indexable HTML. Dutchie Plus Migration applies to the headless Plus API — dispensaries that already pay for Plus and built a custom storefront against the Plus REST endpoints. The work there is to translate the Plus integration to the newer GraphQL pattern, preserve every existing product URL via 301 redirects, and maintain schema continuity through the cutover. If you don't know which integration you're on, the quick check is to view the source of your menu page: if you see an <iframe> element pointing at dutchie.com, you're on standard embed and need Dutchie SEO. If you see custom product card HTML rendered by your own site, you're on Plus and the migration service is the right path. Full migration recipe at /dutchie-plus-migration.

1. 1Menu API audit — We capture every Dutchie GraphQL response for your retailer ID using a Playwright session against your live menu. This produces a snapshot of every product, every variant, every price tier, every category, every brand, and every image URL currently in your catalog. The audit also flags products with missing descriptions, missing strain attributes, or missing brand associations — all of which weaken downstream schema quality. Average BA client catalog at audit time in Q2 2026: 320-680 active SKUs.
2. 2Schema mapping — Each product type (flower, edibles, concentrates, vapes, pre-rolls, accessories) is mapped to a normalized `Product` schema shape with the correct `category`, `brand`, `offers.price`, `offers.priceCurrency`, `offers.availability`, and where applicable `additionalProperty` entries for THC%, CBD%, strain type, and weight. Edibles get `nutrition` extensions. Concentrates get extraction-method attributes. This is the schema substrate every downstream surface reads from.
3. 3Server-side rendering — We deploy the Apex MenuEdge Cloudflare Worker in front of your domain. The Worker handles `/shop`, `/menu`, `/products/[slug]`, and category routes. On every request, it fetches the current GraphQL state, merges product HTML and schema into the response, and serves the result with edge cache headers tuned to inventory freshness. Time-to-first-byte target: under 200ms. Hydration is transparent — the cart layer continues to use Dutchie's authenticated session.
4. 4Sitemap injection — Every server-rendered product URL gets injected into your dynamic `sitemap.xml` with `<lastmod>` reflecting the last inventory change for that SKU, plus `<image:image>` entries for each product photograph. The sitemap is regenerated on inventory mutation events, not on a fixed schedule, so Google sees fresh `lastmod` timestamps that correspond to real catalog changes. We submit the updated sitemap to Google Search Console and Bing Webmaster Tools via API on every regeneration.
5. 5Internal linking — Product URLs are wired into the broader site information architecture. Category hubs link to all in-stock products in that category. Brand pages link to all in-stock SKUs from that brand. Location pages link to top-selling products at that location. Strain-specific landing pages link to in-stock products of that strain. Every product page links back to its category, brand, and location hubs. This converts a flat product catalog into a hub-and-spoke topology that distributes PageRank across the entire menu and signals topical authority around cannabis products, brands, and strains.
6. 6Local pack validation — We track Map Pack and Local Finder rankings for "[product] near me," "[strain] near me," "[brand] [city]," and "weed delivery [neighborhood]" queries using geo-gridded rank tracking at 25-point grids around each store. After 30 days, we validate that the product URLs are surfacing in Map Pack carousels and AI Overview citations. The grid telemetry feeds back into the schema, content, and linking layers — products that aren't surfacing get diagnostic review and schema or content remediation.

This process is documented per-client in a shared deliverables doc. The audit phase typically completes in 5-7 business days. Server-side rendering and schema deployment complete in 10-14 business days. Initial indexation usually shows in Google Search Console within 14-21 days of deploy, with full Map Pack lift visible by day 45-60.

Two operational details matter at handoff. First, the schema generation pipeline is configured to silently degrade when individual products have incomplete metadata — a product missing a brand association will still render and emit schema, just with the brand field omitted rather than the entire schema block failing validation. This prevents one bad SKU from contaminating the entire menu's indexation. Second, the MenuEdge cache invalidation hooks listen for Dutchie's product mutation webhooks where available, and fall back to a 60-second pull-based freshness check where webhooks are not configured. Inventory stay accurate within one minute of changes in Dutchie's admin, regardless of webhook configuration on the dispensary's account.

Hii Williamsburg is a New York licensed adult-use dispensary running on Dutchie. Pre-MenuEdge baseline, captured March 2026: Google Search Console reported 6 indexed pages for the entire domain — homepage, about, contact, two location pages, and the menu shell. Zero individual products indexed. Organic clicks for product-level queries: zero. Map Pack visibility for strain-level queries: zero appearances in the top 20 for "Runtz Williamsburg," "Cherry Pie Brooklyn," "live rosin Brooklyn," and 18 other tracked strain-near-me variants.

Post-MenuEdge deploy, captured Q2 2026: 341 indexed pages, of which 312 are individual SKU URLs at /stores/hii-williamsburg/products/[slug]. Organic clicks for product-level queries: 1,840 in the first 30 days post-launch, growing at roughly 22% week-over-week. Map Pack carousel appearances for strain-level queries: 14 of 21 tracked queries now surface Hii Williamsburg in the top 3 carousel positions, including "Runtz cart Williamsburg" (position 2), "live rosin Brooklyn" (position 1), and "infused pre-rolls Williamsburg" (position 1). AI Overview citations: confirmed extraction of Hii Williamsburg product data in Google's AI Overview for "best edibles in Williamsburg" and Perplexity's web pane for "where to buy Cherry Pie in Brooklyn." Cart conversion rate from organic product landing pages: 4.1%, above the 2.8% client average for category-page landings.

The MenuEdge Worker for Hii has served 2.3 million edge requests in 60 days at a P95 TTFB of 142ms with zero origin downtime events. The cache hit ratio on the GraphQL passthrough is 91%, meaning 9% of requests trigger a fresh Dutchie API call — sufficient to keep inventory accuracy inside the 60-second freshness target while keeping cost-per-request below $0.0001.

• /apex-menuedge — the standalone Cloudflare Worker product page with deployment specs, edge architecture, and pricing
• /dutchie-plus-migration — for dispensaries on the Dutchie Plus headless API moving to the GraphQL integration pattern
• /cannabis-seo — the parent service hub covering the full cannabis-specific SEO methodology
• /local-seo-gbp-management — Map Pack, Google Business Profile, and local pack optimization that runs alongside Dutchie SEO
• /schema-markup-optimization — the schema layer that powers product, location, and review surfaces across the dispensary site
• /partners/dutchie — Bud Authority's partner relationship with Dutchie, including integration support and roadmap visibility