Dutchie Plus Migration: Preserve Rankings Through the 2026 Sunset Without Losing Headless Control or Menu Indexation | Bud Authority

If you currently run a custom storefront against Dutchie Plus, three things happen simultaneously at the sunset date: your product pages stop loading inventory, your checkout flow fails, and your search engine traffic begins decaying as Google re-crawls dead pages.

The naive recovery — drop in the standard Dutchie embed — solves the inventory problem but creates a worse one. The standard embed is client-rendered inside an iframe. Googlebot does not crawl iframe contents as native page content. Your product URLs disappear from the index. Internal links that pointed at server-rendered product pages now point at empty containers. Sitemap entries for product URLs return iframe shells with no extractable product data.

The indexation regression is not theoretical. Dispensaries that moved from custom storefronts back to standard iframes in 2024 and 2025 lost between 40 percent and 70 percent of organic menu traffic within two quarters. The recovery curve is slow because Google's index treats the regression as a quality signal, not a temporary technical issue.

Beyond indexation, you lose the operational control Plus gave you. You no longer choose which products to feature on which URL. You cannot run A/B tests on product page layout. You cannot inject schema beyond what the standard embed allows. You give up first-party analytics on product page interactions. The competitive advantage Plus delivered disappears.

We run the same migration playbook for every Plus dispensary. The process is sequenced to preserve indexation across the cutover, not just survive it.

1. 1Audit current Plus implementation. Map every Plus GraphQL query, every product URL pattern, every server-rendered route, every schema injection, every analytics event, every sitemap entry. Output: complete inventory of what Plus is currently doing for your site.

1. 1Document URL inventory and ranking baselines. Pull every indexed product URL from Google Search Console. Capture current ranking positions for top 100 product and category keywords. Capture current organic traffic distribution by URL. This becomes the baseline for measuring migration success and detecting regression.

1. 1Design the redirect map. Every Plus-served URL gets a destination URL in the post-migration architecture. 301 redirects are mapped before any code changes. URL parity is preserved wherever possible — same product, same URL, different upstream provider.

1. 1Deploy the Apex MenuEdge Cloudflare Worker. The Worker is configured for your domain, your product schema, your category taxonomy. Server-rendered HTML is generated at the edge for every product URL Googlebot can request. Edge cache TTLs are tuned to your inventory refresh cadence.

1. 1Migrate schema markup. Product Offer schema, BreadcrumbList, AggregateRating where applicable, every JSON-LD injection that Plus was emitting is reimplemented in the Worker layer. Schema validation runs against the Rich Results Test before cutover.

1. 1Preserve product Offer JSON-LD. Product schema is the highest-value SEO asset Plus delivered. Offer nodes with price, availability, priceCurrency, itemCondition, and seller properties are reconstructed for every product URL. Validation gates require zero schema regressions before cutover proceeds.

1. 1Regenerate the sitemap. Dynamic sitemap.ts emits every product URL with accurate lastmod timestamps pulled from inventory update events. xmlns:image namespace is included for product images. Sitemap submission to Google Search Console is automated.

1. 1Post-migration audit and ranking watch. Two-week ranking watch after cutover. Google Search Console URL Inspection runs against the top 50 product URLs to confirm indexation. Crawl stats are monitored for unexpected error patterns. Any ranking regression triggers immediate redirect or schema review.

The migration runs in a feature-flagged shadow mode for the final week before cutover. Apex MenuEdge serves the new architecture to a small percentage of traffic while Plus continues serving the majority, allowing real-world validation of inventory accuracy, schema correctness, and page performance before full cutover.

Dutchie communicated the Plus sunset to current customers in 2026, with a six-month deprecation runway. The exact cutoff date varies by customer cohort but falls within calendar year 2026. Dispensaries on Plus should confirm their specific deprecation date directly with Dutchie account management and begin migration planning immediately. Six months is the documented runway, but the practical migration window is shorter once you account for staging, redirect mapping, schema reconstruction, and post-migration ranking watch.

Three options replace Dutchie Plus: the standard Dutchie embed (lowest cost, worst SEO outcome), an alternative menu provider like Jane or Weedmaps Listings (60-90 day migration, SEO outcome depends on provider), or a reverse-proxy architecture like Apex MenuEdge that sits in front of any provider and preserves server-rendered product pages for Googlebot. Apex MenuEdge is the only option that preserves the indexation and ranking continuity Plus delivered, regardless of which upstream menu provider the dispensary chooses post-sunset.

One-time migration: $4,500 to $12,000 depending on the size of the product catalog, the complexity of the existing Plus implementation, and the number of category and product page templates that require schema reconstruction. Typical single-location dispensary with 200-400 SKUs lands at $6,500. Multi-location chains with shared product catalogs scale to the upper end of the range.

Ongoing Apex MenuEdge retainer: $1,500 to $3,000 per month per location. Retainer covers Worker deployment costs, schema maintenance as Google updates rich result requirements, ranking watch, sitemap regeneration on inventory changes, and quarterly schema validation passes. Multi-location pricing scales down per location.

Migration timeline: 4-8 weeks from kickoff to cutover for single-location dispensaries. 8-14 weeks for multi-location chains with shared catalogs and cross-location URL structures.

Get a Free Dutchie Plus Migration Plan — we audit your current Plus implementation, document your URL inventory and ranking baselines, and return a written migration plan with timeline and pricing within five business days.

• Apex MenuEdge — the reverse-proxy product behind every BA Dutchie Plus migration
• Dutchie SEO — broader Dutchie indexation playbook including standard embed optimization
• Dutchie Partner Page — partnership context and integration history
• Cannabis SEO — the full BA cannabis SEO discipline