Dispensary Website Migration SEO: One Move at a Time
Dispensary website migration SEO from Google's site-move rules: redirect maps, Change of Address and menu vendor switches. Run the free audit before launch.
Get a Free Audit for This Service// Page Stats
9
Sections
2K
Words
10 min
Read Time
Dispensary website migration SEO rests on two rules from Google's site-move guide, explained here by Bud Authority, a Dutchie Certified Partner: permanently redirect each changed URL server-side to its closest match, and make one change at a time. Name the move first, and file Change of Address only for a domain or subdomain move.
The costly mistake is booking a rebuild, a menu-vendor switch and a domain change for the same weekend. When traffic falls after that launch, nobody can say which of the three caused it, so nobody knows what to roll back. Pull the three moves apart, run them in order, and keep a short list of checks for when the numbers fall anyway. More operator guides sit in the Bud Authority Learn library for dispensary operators.
// On This Page
Classify the move before you touch a redirect
Each kind of move carries its own steps, so name it before you plan anything. A new platform is a rebuild or a new CMS on the same domain. A new menu provider is a switch between Dutchie, Jane, Treez, Sweed or another vendor, or between two setups from the same vendor. A new domain or subdomain changes the address itself. A rebuild plus a menu switch is two moves, and it gets two launch dates.
| Step | New platform, same domain | New menu provider or setup | New domain or subdomain |
|---|---|---|---|
| Map old URLs to new URLs | Every URL that changes | Every menu, category and product URL that changes | Every URL |
| Permanent server-side redirects | Where URLs change | Where menu URLs change | Every URL |
| Submit the new sitemap in Search Console | Yes | Yes, if the menu publishes one | Yes |
| Change of Address in Search Console | No | Possibly, if the old menu had its own subdomain (see the Dutchie example below) | Yes, once redirects are live |
| Clear staging noindex rules and robots.txt blocks | At launch | At launch | At launch |
| Expect rankings to move while Google recrawls | Yes | Yes, on menu pages | Yes |
When only the hosting changes and every URL stays put, most of that table falls away. Google's guide for moves without URL changes calls a brief dip in Googlebot's crawl rate right after launch normal.
Moves that change URLs need permanent server-side redirects
Build the redirect map first, because every later step depends on it. Export every URL the old site has: location pages, menu category and product pages, blog posts, and promotion pages that picked up links. Write the new URL beside each one and point it at the closest matching page. Sending everything to the homepage throws away the match between an old page and its replacement.
Google's guide to site moves with URL changes puts the method in one line: "Use server side permanent redirects if technically possible." Its redirect documentation adds that "The 301 and 308 status codes mean that a page has permanently moved to a new location." JavaScript redirects sit at the bottom of the list: "Only use JavaScript redirects if you can't do server-side or meta refresh redirects." Ask the new host, in writing, which status codes it can return before you book a launch date.
Google says to keep redirects "for as long as possible, generally at least 1 year."
The new pages need the same map. Google asks for a self-referencing canonical tag on each new URL and says to "Change the internal links on the new site from the old URLs to the new URLs." Work through the map for both before launch, so menu, location and footer links point straight at new addresses instead of hopping through a redirect.

A domain or subdomain move adds a Change of Address step
A new domain, or a jump from one subdomain to another, needs one more step once the redirects are live. Google's site-move guide says to "submit a Change of Address in Search Console for the old site." The Change of Address help page lists what has to be true first:
- "Implement a 301 redirect from your old homepage to your new homepage."
- "You must be an owner of both the old and new properties in Search Console."
- "Maintain the redirects for at least 180 days"
The same page rules out three moves dispensaries make often. It excludes "Changing address from http to https," and states "You cannot move properties at the path level." For a www to non-www switch it says to "use canonical tagging and/or redirects without using the change of address tool." An https switch, a www switch, or a section moving into a folder on the same domain runs on redirects, canonical tags and an updated sitemap.
Swapping menu providers changes where the menu lives
The vendor's setup decides where product pages sit: inside an iframe, on a subdomain, or in a folder on your own domain. That location decides how many URLs you have to redirect. Crawl and save every current menu URL before the switch and start the map from that list.
Dutchie Plus support window.
Dutchie's blog says the company is "committed to supporting our legacy Dutchie Plus customers through the end of 2026," and its E-Commerce Pro article describes a migration path from Plus to Pro. A store moving from Plus to Pro should treat it as a menu-provider move and finish the URL map before it books a launch date.
Dutchie setups.
Dutchie's E-Commerce SEO FAQ lists four options. It describes the embedded menu as partially indexed by Google, the subdomain menu as fully indexed but treated as a separate site, and E-Commerce Pro + Proxy as making the storefront appear as part of your root domain to search engines. Dutchie's Cloudflare guide loads that storefront as a sub-path such as yourdomain.com/store and requires a Cloudflare Workers Paid plan, a domain on Cloudflare and access granted to Dutchie.
Who serves the redirects when a Dutchie subdomain moves into a folder
Take a store moving from a storefront at menu.yourdispensary.com to Pro + Proxy at yourdispensary.com/store. Every menu URL changes, so the move needs the full redirect map, and it raises a question most launch plans skip. Dutchie's custom-domain setup points the subdomain at a Dutchie host with a CNAME record, so requests for the old menu URLs reach Dutchie, not your web host. Your developer cannot add redirects to a server they do not control. Get written confirmation from Dutchie of who will answer those old subdomain paths with permanent redirects, and for how long.
Change of Address is less clear-cut here. Google's help page covers moving a website from one domain or subdomain to another, and the old menu is a subdomain, but its new home is a folder on your own root domain. Plan the move on redirects and a new sitemap, and file Change of Address only if Search Console accepts it for the subdomain property.
Treez, Jane and Sweed
Treez
documents a reverse proxy that makes the online menu appear as if it is hosted on your own domain. Its setup guide has the dispensary pick a menu path such as /menu or /shop and requires Cloudflare as the DNS provider. Treez also documents a legacy iframe embed of its online menu, so the Treez move to plan for is leaving that embed for the reverse proxy. Its help center lists an article on SEO when migrating your website; read it before you set a date.
Jane
depends on the setup you are leaving. Jane's developer documentation says the traditional embed script runs the whole customer flow, menu and checkout included, inside an iframe, and that in an iframe the URL stays the same. A shop leaving the iframe has no per-product addresses on its own domain to redirect, so the work is publishing and submitting new menu URLs. Boost is different: Jane describes it as a single-page app whose URL changes and ties Boost's SEO benefit to that change. A shop leaving Boost has menu URLs to map, and so does one leaving Roots, Jane's headless option for a fully custom menu.
Sweed
says it can run standalone or be integrated into an existing site by subdomain or URL path, so the same domain, subdomain and folder logic applies. Ask Sweed for its own move steps before you set a date. For what each vendor documents about search outside a move, see the dispensary menu platforms comparison.
Check what Googlebot gets from the new menu
A new menu address does not change what the page sends before JavaScript runs. Google's JavaScript documentation says "If the content isn't visible in the rendered HTML, Google won't be able to index it." After any menu move, run the URL Inspection live test on a sample of new menu pages and read what Googlebot actually received.
Move one thing at a time and launch every URL together
Across a project, Google's site-move guide is direct: "Plan your changes to your site one after the other, not everything at the same time." That is the fix for the same-weekend launch: run the rebuild, let it settle, then run the menu switch as its own move.
Within a single move the advice flips: "Small or medium sites: We recommend moving all URLs on your site simultaneously instead of moving one section at a time." A rebuild should launch with every URL redirected on day one, not page group by page group. That line is addressed to small or medium sites, so a large multi-store menu should not assume it applies.
Google also says "Time your move to coincide with lower traffic, if possible," so keep launches away from your heaviest sales weeks; it warns of ranking fluctuations while it recrawls and reindexes a moved site. Submit the new sitemap in Search Console on launch day, since "Submitting a sitemap can help make the discovery process quicker." After that, "you can remove your old sitemap, since Google will use the new sitemap going forward."
Before launch, list every page carrying a staging noindex rule and every robots.txt block, and clear them on launch day. A forgotten noindex is expensive: Google "will drop that page entirely from Google Search results, regardless of whether other sites link to it."
What to check if traffic dropped after the move
Work through these in order. Each step rules out a cause before you spend time on the next.
- 1Robots and noindex. Open the live robots.txt and a sample of new pages. Google documents two ways to set noindex, a meta tag and an HTTP response header, so read the response headers as well as the HTML. For noindex to work, the page "must not be blocked by a robots.txt file," so check the two together.
- 2Redirect status codes. Request a sample of old URLs, menu and location pages included. Each should return a 301 or 308 to its matching new page. Chains, temporary redirects and homepage catch-alls are the first things to fix.
- 3Canonicals and internal links. On a sample of new pages, check that the rel="canonical" tag names the new URL, since the site-move guide says to "ensure that the rel="canonical" link annotations on the new site are using the new URLs." Then check that menu and location links point at new URLs, not old ones.
- 4URL Inspection, read correctly. Google says the URL Inspection tool reports on "Google's indexed version of a specific page," not a live view. Run the live test to see what Googlebot gets from the new URL today.
- 5Page indexing report. Filter to the new URLs and look for the statuses Soft 404 and Duplicate without user-selected canonical.
- 6Sitemap. Confirm the submitted sitemap lists the new URLs, not the old ones.
- 7Change of Address, for domain or subdomain moves only. Confirm it was filed for the old property and that the homepage redirect and both ownerships still hold.
If the drop started without a move, the guide to a dispensary not showing on Google walks the wider diagnosis.
Checks after a traffic drop
Step 01
Robots and noindex
Open the live robots.txt and a sample of new pages, and read the response headers as well as the HTML.
Step 02
Redirect status codes
Each old URL should return a 301 or 308 to its matching new page. Fix chains, temporary redirects and homepage catch-alls first.
Step 03
Canonicals and internal links
The rel="canonical" tag names the new URL, and menu and location links point at new URLs.
Step 04
URL Inspection live test
The default result is Google's indexed version, not a live view.
Step 05
Page indexing report and sitemap
Look for Soft 404 and Duplicate without user-selected canonical, and confirm the sitemap lists the new URLs.
Step 06
Change of Address
For domain or subdomain moves only, confirm it was filed for the old property.
What a post-migration redirect map recovered for one Queens dispensary
Terp Bros is an adult-use dispensary with stores in Astoria and Ozone Park, Queens. After its site migration, we shipped a per-URL 301 redirect map and live-verified it on June 10, 2026. The case file records about 3,500 monthly clicks recovered through that post-migration 301 map.
Elevate Cannabis in Mount Vernon recorded 4,238 Google Search clicks in July 2026, against 4,192 the prior period, across a platform migration. More dated results sit in the public case files.
Migration results, dated
3,500
Monthly clicks recovered through the post-migration 301 map, shipped and live-verified on June 10, 2026
Terp Bros
4,238
Google Search clicks in July 2026, against 4,192 the prior period, across a platform migration
Elevate Cannabis
What the free audit checks, and what it does not
The free Bud Authority audit runs an automated scan of more than 40 signals on the site you enter and shows the report card on screen. It is not a migration checker: it does not take your old URL list or access your Search Console, so the redirect, Change of Address and sitemap checks above stay with you or your developer. Engagements are quoted after an audit.
If the move is a rebuild, the dispensary web design and CRO service covers the new site itself. For Dutchie stores, our Dutchie SEO service covers the menu side. For Dutchie menus behind a reverse proxy, our Apex MenuEdge runs on Cloudflare in front of the menu and rewrites each page as it is served, so crawlers receive a server-rendered page while shoppers keep the same live Dutchie menu and checkout. Guides on menus, indexing and local search sit in the Learn library.
Frequently asked questions
Why did our dispensary's traffic drop after a website migration?
Usually a launch check failed: a leftover staging noindex, a robots.txt block, temporary or broken redirects, canonicals still naming old URLs, or a stale sitemap. If every check passes, the dip may be the move itself. Google notes that "the visibility of your content in Search may fluctuate temporarily during the move."
How long does Google take to settle after a dispensary site move?
Google says "a small to medium-sized website can take a few weeks for most pages to move," and it can take a few weeks or more before the new URLs start showing in results. Asking Google to recrawl the same URL again and again will not get it crawled any faster, so request it once and wait.
Continue Exploring
Dispensary Google Business Profile Suspended: The Appeal Runbook
Dispensary Google Business Profile suspended? Match it to the rule Google ties to suspension, fix the listing, and file the one appeal Google allows.
How Perplexity Cites Sources, and How to Check What It Links
How Perplexity cites sources: a link in its answer to the page it drew on. How to check that source, and what PerplexityBot and Perplexity-User each do.
Cannabis Content Brief Template: Fill These Fields First
Cannabis content brief template: copy the fields a dispensary fills in before drafting, from query and sources to state compliance. Request the free audit.
Cannabis Marketing Statistics: Dispensary Search and AI Visibility
Cannabis marketing statistics, 2026: home pages drew a median 77.5% of client Google clicks, menus 10.5%, and AI assistants named clients in 54.1% of runs.
Multi-state cannabis marketing: which state rules repeat
Multi-state cannabis marketing: content bans that repeat across seven states, and the audience tests, warnings and Ohio pre-approval that change. Free audit.
Cannabis SEO FAQ: what owners ask first
Cannabis SEO FAQ: what cannabis SEO covers, why Google Ads refuses marijuana, what GPTBot found on Dutchie storefronts and why no agency can promise rankings.
// reference desk
Have a question this guide did not answer?
Get a free audit and we will map your dispensary's exact opportunity from the same playbook.
> [ INITIATE AUDIT ]Want more Bud Authority in your Google results?
Pick Bud Authority as a preferred source and our cannabis search research is more likely to appear in your Top Stories, and our links can carry a Preferred badge in AI Overviews and AI Mode.





