Moving Your Cafe Website Without Losing Google Traffic
You are about to change platforms, move to a new domain, or restructure your cafe's page addresses, and somewhere in the back of your mind is a fear that your Google traffic and your Maps clicks are going to vanish the day it happens. That fear is a reasonable one to have. It is also, with the right preparation, almost entirely avoidable.
Short answer: a site move by itself rarely causes the traffic loss owners worry about. What actually causes it is a short list of avoidable mistakes, missing redirects from old URLs to new ones, pages that quietly disappear in the move, crawling accidentally blocked on the new site, and a Search Console setup that never gets updated to reflect the change. Google's own Search Central documentation on site moves lays out what it expects to see when URLs change, and almost every real loss traces back to one of those documented steps being skipped, not to the move itself.
This post gives you the checklist in four stages, before, during, after and verify, grouped around Google's own site move guidance, so you know exactly what to hand to whoever builds the new site and exactly how to check the work when it is done. It covers only the how of moving safely, not the separate question of whether you need a new website at all, or whether site speed is worth fixing first, both of which have their own dedicated coverage.
Before
Before anything moves, build a complete map of your current URLs and where each one needs to point on the new site. This is the single most important document in the whole process. Google Search Central's site moves documentation is explicit that when URLs change, whether from a platform switch, a domain change, or a restructuring of page paths, each old URL needs a corresponding new URL and a redirect connecting the two.
A simple redirect map looks like a table with three columns: the old URL, the new URL, and the redirect type. For a fictional five page cafe site, that might mean the homepage staying the same, an about page moving from /aboutus to /story, a menu page moving from /menu.pdf to /menu, a contact page changing address entirely, and a blog post keeping its same slug under a new domain. Every single page that currently exists needs a row in this table, even pages you think nobody visits, because a page that simply disappears with no redirect is a page Google eventually drops from its index, along with whatever traffic it was sending you.
Decide on your redirect type before the move, not during it. A permanent 301 redirect is what Google's documentation on redirects describes as the correct choice when a page has permanently moved to a new URL, telling both browsers and search engines that the change is not temporary. Confirm with whoever builds your new site that they are using a true 301, not a temporary redirect, a JavaScript based redirect, or a simple link on a landing page, since each of those behaves differently for search engines than a proper server level redirect does.
Also confirm before the move which Search Console property you will need. A platform change that keeps the same domain is a smaller event than a domain change, and Google's Change of Address tool, documented within Search Console Help, applies specifically to a full domain move, where you tell Google directly that one verified property has moved to another. If you are only changing platforms but keeping your domain, this step does not apply the same way, but your sitemap and your redirect map absolutely still do.
Assign someone the clear job of owning this checklist before the move begins. A site move often involves a developer, a designer and the owner all touching different pieces at once, and a redirect map that lives in one person's head rather than a shared document is exactly how a handful of URLs quietly get missed. Write the map down somewhere everyone involved can see it, and treat it as the single source of truth for what needs to happen.
During
On the day of the move, work through the redirect map methodically rather than trusting that the new platform handled everything automatically. Every common platform, Wix, Squarespace and Shopify each offer their own version of a redirect manager, sometimes labeled as a URL Redirect Manager, URL Mappings, or simply URL Redirects depending on the platform, and each requires you to manually enter the old path and the new path for every URL on your map. Nothing about this step happens by magic; it happens by someone going through the list.
Set every redirect as a permanent, 301 style redirect where the platform offers that choice, matching the decision made before the move. Do not skip a URL just because it seems minor. A blog post with a handful of monthly visitors still represents real, indexed traffic that a missing redirect will simply drop.
As you finish each redirect, test it immediately rather than waiting until the whole move is done. A simple status check, requesting the old URL directly and confirming it returns the correct response code and lands on the intended new page, catches typos and mismatched paths on the spot instead of days later when a customer or Google's own crawler hits a dead end instead.
Update your sitemap to reflect the new URL structure and submit it through Search Console as part of the same session, not as an afterthought later in the week. Search Console Help's guidance on sitemaps describes the sitemap as a way to help Google find and understand your site's current pages, and an outdated sitemap pointing to URLs that no longer exist works directly against the redirect map you just built.
If the move happens outside normal business hours to limit disruption, resist the temptation to skip the testing step until the next morning. A redirect that is wrong is far easier to fix in the same working session, while the context and the redirect map are both fresh, than it is to diagnose days later once traffic has already started responding to whatever mistake slipped through.
After
Once the new site is live and every redirect is set, the work is not finished. If you moved to a new domain, complete the Change of Address process in Search Console so Google has an explicit signal connecting the old verified property to the new one, rather than relying only on the redirects themselves to communicate the change over time.
Check your Page Indexing report in Search Console over the days and weeks following the move. Search Console Help describes this report as showing which of a site's pages are indexed and which are not, along with the reasons a given page might be excluded, which makes it the clearest place to watch for pages from the new site failing to get indexed, or old pages lingering in a way that suggests a redirect issue.
Update every external reference you control. Your Google Business Profile, any directory listings, and any social media bio links pointing to the old domain or old URL structure should all be updated to point directly at the new address rather than relying on a redirect to carry that traffic indefinitely. A redirect is a safety net for links you do not control, not a permanent substitute for updating the ones you do.
Resist the urge to make additional structural changes during this same window. A site move already introduces enough change for Google to process at once; layering a full content rewrite, a new page structure, or a wholesale design overhaul on top of the same move makes it much harder to tell later which change, if any, caused which result.
Keep a short written log of exactly what changed and when, including the launch date, the domain or platform involved, and any redirect that needed a correction after launch. If a question ever comes up later about why a particular page's performance shifted, having a dated record of the actual move removes the guesswork of trying to reconstruct the timeline from memory.
Verify
Verification is its own stage, not a quick glance at the homepage on launch day. Start by testing a meaningful sample of old URLs directly, checking that each one redirects to the correct new page and returns the right response code, rather than a broken link, an error page, or a redirect that lands somewhere unrelated to where the content actually moved.
Watch the Page Indexing report weekly rather than daily in the first stretch after the move. Google's documentation does not promise a specific recovery timeline, and treating any single day's numbers as a verdict tends to cause more anxiety than the data supports. A steady trend across several weeks tells you far more than one day's snapshot.
Cross check your Maps presence separately from your website's organic performance. A site move affects your website's search visibility directly, but your Google Business Profile and Maps pack presence run on their own separate systems, so a dip or a steady state in one does not automatically mean the same thing is happening in the other. Watch them as two related but distinct signals, not one combined number.
Call this stage done once your redirect map has been fully tested with no broken links, your sitemap reflects the current site and has been resubmitted, your Change of Address process is complete for any domain change, and the Page Indexing report shows the new site's pages getting indexed without an unusual spike in excluded pages. That is a genuinely safe move, checked rather than assumed.
It is worth building this verification stage into your calendar rather than trusting you will remember to circle back. Set a reminder for one week after launch and another for a month after, each time a short repeat of the same checks: a handful of old URLs tested directly, a look at the Page Indexing report, and a glance at whether your Maps presence looks stable. Two or three short check ins spread across the first month catch far more than one long look on launch day ever will, because indexing and crawling changes take time to settle rather than appearing instantly.
If something does look off during verification, such as a redirect landing on the wrong page or a batch of pages showing as excluded in the Page Indexing report, fix it as soon as you spot it rather than waiting to see if it resolves on its own. A wrong redirect does not fix itself with time, and the sooner a mistake is corrected, the shorter the window during which Google, and your customers, are being sent to the wrong place.
Related Reading
More from Hillcane on this topic, plus the pages on the site that sit next to the work.
Frequently Asked Questions
How do I migrate a cafe website without losing Google traffic?
Build a complete redirect map from every old URL to its new equivalent before the move, use permanent 301 redirects, update your sitemap and resubmit it in Search Console, complete the Change of Address tool if you changed domains, and verify every redirect and your Page Indexing report after launch. Most traffic loss comes from skipping one of these steps, not from the move itself.
What redirect type should I use when moving a cafe website?
Use a permanent 301 redirect. Google Search Central's documentation on redirects describes the 301 as the correct choice when a page has moved for good, because it tells browsers and search engines the change is not temporary. Confirm your builder applies a true server level 301, not a temporary redirect, a JavaScript redirect, or a link on a landing page. Set the type before the move and record it in your redirect map.
Do I need the Change of Address tool if I only changed website platforms?
No. Google's Change of Address tool, documented in Search Console Help, applies only to a full domain move, where you tell Google that one verified property has moved to another. A platform switch from Wix to Squarespace or Shopify on the same domain is a smaller event. You still need every old URL mapped to its new one with a 301 redirect, and an updated sitemap submitted in Search Console.
How do I check that my redirects are working?
Test each redirect as soon as you set it. Request the old URL directly, confirm it returns a 301 response code, and confirm it lands on the intended new page rather than an error or an unrelated page. After launch, test a meaningful sample of old URLs again, then repeat that test one week later and one month later. Fix a wrong redirect in the same session you find it.
How long should I watch Search Console after a site move?
Plan on at least the first month, checking weekly rather than daily. Google's site move documentation does not promise a recovery timeline, so a steady trend across several weeks in the Page Indexing report means more than any single day. Set reminders for one week and one month after launch, and each time test a few old URLs, review excluded pages and their reasons, and glance at your Maps presence.
Will a site move affect my Google Maps ranking too?
Your website's organic search visibility and your Google Business Profile or Maps pack presence run on separate systems, so a site move mainly affects the website side. Watch them as two related but distinct signals rather than one combined number. Do update the website link on your Business Profile to the new address directly, along with directory listings and social bios, instead of leaving a 301 redirect to carry that traffic indefinitely.
Should I redesign my cafe site at the same time as moving it?
Avoid it if you can. A site move already gives Google plenty to process, and layering a redesign, new page structure, or full content rewrite onto the same launch makes it much harder to tell which change caused which result. Move first, verify it through the Page Indexing report over several weeks, then redesign as a separate step. Keep a dated log of the launch and any redirect corrections either way.
What happens if I forget to update my sitemap after a move?
An outdated sitemap points Google at URLs that no longer exist, which works directly against the redirect map you built. Search Console Help describes the sitemap as a way to help Google find and understand your site's current pages, so a stale one can slow how quickly the new structure is understood. Update it to the new URLs and resubmit it in Search Console during the same session as the move.
Do I need to update my Google Business Profile link after a domain change?
Yes. Change the website link on your Google Business Profile, plus directory listings and social media bio links, to point straight at the new address. A 301 redirect is a safety net for links you do not control, not a permanent substitute for updating the ones you do. If the domain itself changed, also complete the Change of Address process in Search Console so Google connects the old and new properties.
How can Hillcane help with a cafe website move?
Hillcane can help build the redirect map, one row per old URL with its new URL and a 301 type, and check that your platform's tool, whether Wix URL Redirect Manager, Squarespace URL Mappings, or Shopify URL redirects, is set correctly. It can also verify URLs after launch and confirm your sitemap and Search Console setup. Reach out at hillcane.co/contact or call (256) 384-2449 before the move happens.
Work with Hillcane
You are about to move your cafe's website and you are worried Google traffic will vanish overnight. It usually does not, unless one specific step gets skipped.
If you are planning a platform or domain change for your cafe site and want a second set of eyes on the redirect plan, reach Hillcane at hillcane.co/contact or call (256) 384-2449.
Comments