A website migration can fix a slow, outdated site, then quietly break the URLs local customers use to find you. That is why local SEO migration work must start with redirects, not after rankings or calls fall.
When old service pages, city pages, or location URLs disappear, Google and users can hit a dead end. A direct 301 redirect keeps the relevant destination available, but it doesn’t update your Google Business Profile, citations, canonicals, or internal links. Use this checklist before launch and during the first weeks after the move.
Why Redirects Matter to Local Search Visibility
A redirect is one part of a migration, but it protects several local search signals at once. It helps customers reach the right page, gives Google a clear replacement URL, and prevents valuable links from pointing to dead pages.
A redirect protects the path to a local page
Local businesses often have more important URLs than their homepage. These include service pages, city landing pages, individual location pages, appointment pages, and pages linked from local directories.
If /plumbing-services/ becomes /services/plumbing/, the old URL should point directly to the new equivalent. The same applies when a location page moves because of a new content structure or domain.
Google’s guidance on 301 redirects states that permanent redirects show the new target in search results and don’t cause a loss in PageRank. A redirect doesn’t guarantee stable rankings, but it gives search engines a clear route to the replacement page.
Redirects don’t repair a weak local page
A redirect only forwards traffic and signals. It doesn’t make the new page relevant, accurate, or useful.
After a migration, you still need to review:
- The business name, address, and phone number
- Service and location content
- LocalBusiness structured data
- Internal links between service and location pages
- Title tags and meta descriptions
- Google Business Profile categories and services
- Conversion paths for calls, forms, bookings, or directions
Keep these tasks separate. Redirects protect URL continuity. Local SEO work improves the destination.
Build the Local SEO Migration Redirect Map Before Launch
Do not wait for the new site to go live before deciding where old URLs should go. Build the map while the old site is still available.
Start with a full crawl and export URLs from Google Search Console, analytics, server logs, XML sitemaps, Google Business Profile, and important directory listings. Include pages with backlinks, even if they receive little current traffic.
Start with pages that carry local demand
Prioritize URLs that support real business activity. A high-value city page may generate calls. A service page may rank for commercial searches. A location page may be linked from your Google Business Profile and local citations.
Sort the URL list by organic visits, leads, backlinks, rankings, and local importance. Review pages with no traffic as well. A page can have low visits but still hold useful links or support a location cluster.
Match each old URL to its closest new page
Map every important old URL to a relevant final destination. Avoid sending every deleted page to the homepage. That creates a poor user experience and gives Google a weak replacement signal.
| Old URL type | Preferred destination | Local purpose |
|---|---|---|
| Service page | Matching service page | Preserve service-specific relevance |
| City landing page | Matching city page | Maintain geographic intent |
| Location page | Same business location page | Keep address and contact access |
| Booking or contact page | New booking or contact page | Protect conversion traffic |
If a page has no suitable replacement, don’t redirect it to an unrelated service. Fix internal links, remove the old sitemap entry, and return an appropriate 404 or 410 response when the content is permanently gone.
A redirect should preserve the most relevant path, not hide a missing page behind the homepage.
Configure and Test Every Redirect
The redirect map only helps when the server implements it correctly. Confirm the rules in staging when possible, then test them again immediately after launch.
Use direct 301 redirects, not chains
The clean path is:
old URL -> final new URL
Avoid this:
old URL -> temporary page -> redesigned page -> final URL
Googlebot can follow up to 10 hops, but Google’s site migration documentation recommends sending users and crawlers directly to the final destination. Chains add latency, create more failure points, and make troubleshooting harder.
Use a 301 when the move is permanent. A 302 is for a temporary change, such as a controlled test. Don’t use a temporary redirect for a permanent domain or URL migration.
Keep permanent redirects active for as long as possible, generally at least one year. Longer is better when old URLs appear in citations, backlinks, printed materials, or customer bookmarks.
Test the failures, not only the homepage
A homepage test proves almost nothing. Test representative URLs across every local template and folder.
Check that:
- Old HTTP, HTTPS, www, and non-www versions reach the correct final URL.
- Old service, city, and location pages return a 301 status.
- The final destination returns a normal 200 response.
- No redirect loops or multi-step chains exist.
- Deleted pages don’t redirect to unrelated content.
- Query parameters don’t create unnecessary duplicate paths.
- Mobile users reach the same relevant destination as desktop users.
Use a crawler, server-header checker, or command-line request tool to test the list in bulk. Review the results by status code, not by appearance alone. A page can look correct in a browser while still returning the wrong response to search crawlers.
Update Canonicals, Internal Links, and Search Console
Redirects handle old URLs. Your new site still needs clean signals that identify the current URLs.
Point every supporting signal to the new URL
Each important new page should have a self-referencing rel="canonical" tag. Canonicals on the new site must use the new URLs, not the old paths.
Update internal links in the navigation, service menus, location hubs, footer, blog posts, image links, and structured data. A migrated site with correct redirects can still waste crawl activity if its own pages keep linking to outdated URLs.
Create a new XML sitemap containing the current canonical URLs. Submit it in Search Console after launch. Google’s site-move process includes new sitemap submission as a post-migration task, not optional cleanup.
Use Change of Address for a domain move
If the business moves from one domain to another, configure the redirects first. Then submit the Change of Address request for the old property in Search Console.
The Change of Address tool helps Google process a move between domains or subdomains. It does not replace server-side redirects.
A redesign that only changes paths on the same domain normally doesn’t require this tool. In either case, keep the old site property accessible and monitor both properties during the transition. Google also cautions that you can’t immediately submit another Change of Address from the new site to a third site, so avoid submitting a chain of moves without planning the final destination.
Reconnect Google Business Profile and Local Citations
Your website migration affects the URL connected to your local presence. Review those connections directly instead of assuming the redirect handles everything.
Update the Google Business Profile website field
Once the new site is live and the final URL has passed testing, update the website field in the existing Google Business Profile. Google requires the full website address, including http:// or https://.
Use Google’s instructions to edit your Business Profile. Enter the current location or contact URL that best supports the profile. Don’t use a shortened URL, tracking redirect, or generic page when a direct location page is available.
A redirect from the old profile URL may keep the link working, but a direct link removes an unnecessary hop. Check every location profile separately when a business has multiple offices, clinics, stores, or service areas.
Audit citations and tracking links
Review the website links on major directories, chamber pages, trade associations, social profiles, partner websites, and local sponsorship pages. Update the highest-value listings first.
Keep your business name, address, and phone number consistent unless the business itself has changed. A URL move doesn’t justify changing established business details.
Review tracking parameters as well. Make sure campaign URLs still land on valid pages, preserve attribution, and don’t become the canonical version of the page. If profile activity matters during the move, Learn More about automating Google Business Profile posts and review responses without adding another manual task to the migration list.
Run Launch-Day and 30-Day Local SEO Checks
A migration isn’t finished when the new homepage loads. Local performance depends on hundreds of paths working together.
Run the launch-day check
Complete these checks as soon as the new site is live:
- Test old high-value URLs from the redirect map.
- Crawl the new site for 404 errors, 5xx errors, broken internal links, and redirect chains.
- Confirm new canonicals, robots directives, and sitemap URLs.
- Open key pages on mobile and test calls, forms, bookings, and directions.
- Check that the Google Business Profile website field uses the correct full URL.
- Review analytics and call tracking to confirm conversions are being recorded.
- Inspect a sample of migrated URLs in Search Console.
Pay close attention to local templates. One faulty rule can break every city page or every location URL at the same time.
Monitor each location after launch
Track organic traffic, indexed pages, calls, form submissions, direction requests, and local rankings by location. Compare equivalent periods instead of reacting to one day’s movement.
A short ranking change doesn’t always mean the migration failed. Search engines need time to recrawl, process redirects, and replace old URLs. A sustained increase in 404 errors, lost indexed pages, or missing local conversions needs attention.
Review redirect errors weekly during the first month. Keep the redirect map as a working document, then add newly discovered old URLs from server logs and Search Console.
If you want to keep profile posts and review responses active while your team handles the technical work, Sign Up to automate those Google Business Profile tasks.
Conclusion
A successful local SEO migration depends on matching old URLs to relevant new pages, using direct 301 redirects, updating canonicals and sitemaps, and reconnecting every important local profile.
Redirects protect access to existing value. They don’t replace accurate business details, useful local content, or an active Google Business Profile. Build the map before launch, test real URLs, and keep monitoring after the new site goes live.