Local traffic survives a migration when four things are protected that a standard plan never mentions: the website link on your Google Business Profile, your name, address and phone matching exactly across the site and every directory, the URLs of location and service-area pages, and the LocalBusiness structured data that tells search engines what and where you are. WPBuildAI checks all four alongside the redirect map, for one reason that catches people out: a site can recover its organic rankings exactly on schedule while the map pack quietly does not, because the two depend on different things and only one of them is about URLs. Here is what to protect and how to check it.
Why does local behave differently from organic?
Because most of what decides a map pack position is not on your website at all.
Google describes local ranking as relevance, distance and prominence. Distance is fixed. Relevance and prominence draw on your Business Profile, your categories, your reviews, your citations across directories, and your website, in that rough order of weight for many businesses.
A migration touches only the last of those. That is why local usually holds steady through a clean move, and it is also why the failures are different in kind: they are broken connections rather than lost rankings.
The three connections that break are the profile’s link to your site, the consistency between what your profile says and what your site says, and the structured data that ties a page to a physical location. None of those is a redirect problem, and a redirect map that passes every test will not catch any of them.
What actually breaks local during a migration?
Six things, and each one has a different symptom, which is why a single check does not cover them.
| What breaks | Why it happens | Symptom | How to catch it |
|---|---|---|---|
| Profile links to a redirected page | The linked URL changed | Slow drift, no obvious error | Open the profile link and watch for a hop |
| Phone or address format changed | Rewritten during the rebuild | Inconsistency across sources | Compare site against profile, character by character |
| Location page URLs changed | New information architecture | The pages that ranked locally lose position | Treat them as priority rows in the map |
| LocalBusiness markup dropped | The plugin that emitted it is gone | Rich results disappear quietly | Validate three pages after launch |
| Embedded map or hours block lost | Rendered by a plugin | Page looks thinner to visitors and crawlers | Compare against the captured original |
| Directory citations point at old URLs | Nobody updates directories | Slow leak, months later | Redirect must keep working indefinitely |
The first row is the most common and the least visible. The link still works, because your redirect is doing its job, and the connection is now one hop weaker than it was, on the single most important external reference to your site.
What has to be checked on the Business Profile?
Four things, and all of them are visible in the profile editor rather than in any analytics tool.
The website link first. If your profile pointed at a specific location page rather than the homepage, confirm that address still resolves directly. Editing the profile to the new address is a two minute change, and skipping it leaves your strongest external link travelling through a redirect.
The name, address and phone next, compared against what the new site displays. Not approximately: exactly. A phone number that gains or loses a space, an address that switches from Street to St, or a business name that picks up a suffix during a redesign are all mismatches, and consistency across sources is part of what prominence measures.
Then any secondary links: appointment booking, menus, order pages, service pages attached to individual services. These are set separately from the main website field and they are forgotten almost every time.
Then the categories and hours, which the migration should not touch and which are worth confirming while you are in there.
How do you protect location pages specifically?
Treat them as the highest priority rows in the redirect map, above even the homepage.
A business with pages per city, per neighbourhood, or per service area has its local organic visibility concentrated in exactly those URLs. They are frequently not in the main navigation, so a rebuild driven by the menu misses them entirely, and they are exactly the pages that rank for the queries that bring in local customers.
Preserve their addresses if you possibly can. Google’s site move guidance is clear that changed addresses need permanent redirects, and a preserved address needs nothing at all, which is the cheaper position for pages this valuable.
Then check content parity on them specifically. Location pages are often thin to begin with, so a redesign that trims them further removes the small amount of unique content that made them rank. Compare word count, headings and the address block against the captured original.
What about the structured data?
LocalBusiness markup is usually emitted by a plugin, which means it usually disappears when the plugin does.
Google’s local business structured data documentation sets out what a page should declare: name, address, telephone, opening hours, geo coordinates and the type of business. On WordPress that is typically produced by an SEO or local plugin at render time, so a headless or rebuilt site emits nothing unless somebody carries it across deliberately.
Export it before the plugin is switched off. The values are the same values on your profile, which makes this straightforward, and the failure mode is silence rather than an error: the markup simply is not there, and nothing warns you.
Validate three pages after launch, including one location page, and confirm the address and phone in the markup match both the visible page and the profile. Markup describing something the page does not show is worse than no markup at all.
What should you monitor afterwards?
Two things, on different schedules, because local and organic report separately.
Organic local pages in Search Console: filter the performance report to your location page URLs and watch the same coverage pattern as the rest of the site, new URLs indexed and old ones reporting as redirects.
Profile performance in your Business Profile dashboard: views, searches and actions. This is the closest thing to a map pack signal you get directly, and it is worth screenshotting before the migration so there is a baseline to compare against.
Expect local to be steadier than organic through the move. A clean migration usually shows no meaningful change in profile performance at all, because the listing did not move. A drop that appears within days points at the link or the details rather than at recrawl time, and both are fixable that afternoon.
What should you check, and when?
Six checks across three moments, because local failures surface on different schedules and a single pass after launch misses half of them.
| When | Check | Where | Pass looks like |
|---|---|---|---|
| Before the move | Screenshot profile performance | Business Profile dashboard | A baseline you can compare against |
| Before the move | Export LocalBusiness markup values | SEO or local plugin settings | Name, address, phone, hours, coordinates |
| Launch day | Profile website link resolves directly | Click it from the profile | 200, no redirect hop |
| Launch day | Name, address, phone match exactly | Site against profile, character by character | Identical, including formatting |
| Week one | LocalBusiness markup validates | A structured data validator, three pages | Present, and matching the visible page |
| Week four | Profile performance against baseline | Business Profile dashboard | Flat or up, not drifting down |
The two before-the-move rows are the ones that cannot be done later. A baseline you did not take is an argument you cannot win, and markup values you did not export are values you will be reconstructing from a profile screen while wondering whether the old page said something different.
What about directories and citations?
They point at your old URLs, and nobody is going to update them, which is why the redirect rules have to be permanent rather than temporary.
A business that has been listed for years has entries across directories, chambers of commerce, industry bodies, supplier pages and review sites. Many were created once and never touched. Each contains a URL, and a proportion of those URLs are pages that no longer exist under that address.
Two things follow. Keep the redirect rules indefinitely rather than for a year, because a citation created in 2019 is still sending people and signal in 2027. And spend the outreach effort only where it pays: the five or ten highest value listings, updated directly, and the rest left to the redirect.
The exception worth handling by hand is anything showing your name, address or phone. Those are consistency signals rather than links, so a directory displaying an old phone number is a mismatch whether or not its link resolves. Fix the details on the largest handful, and accept the long tail.
When is local not the thing to worry about?
When you have no physical presence and no service area. A national ecommerce store or a remote software business has no map pack to protect, and the checks on this page are effort spent on a ranking surface it does not appear in.
It is also not the priority when the profile is the weak point rather than the site. A business with three reviews and half its categories unset has a local problem that no migration causes and no redirect fixes, and the hours are better spent there.
And it is not worth over-engineering for a single location business with one address on one contact page. Confirm the profile link, check the phone number matches, validate the markup once, and move on. The full four-part programme matters for multi-location businesses and service-area businesses with dozens of local pages.
What does not change either way: the redirect map still has to be right, because location pages are URLs like any other, and the general sequence in how to migrate a website without losing SEO is the foundation this sits on top of. The launch week routine that catches the rest is in what to do in the first week after a migration goes live.
Key takeaways: keeping local visibility through a move
Local and organic depend on different things. Redirects protect what search engines learned about your URLs, and they do nothing about a profile link, a changed phone format, or missing markup.
Four items carry local through a migration: the Business Profile website link, exact name, address and phone consistency, location page URLs, and LocalBusiness structured data.
Location and service-area pages are usually outside the main navigation, so a rebuild driven by the menu misses them. They deserve the highest priority rows in the redirect map.
Local normally holds steady through a clean move. A drop appearing within days is a broken connection rather than recrawl time, and it is fixable the same afternoon.
Before you decide: common questions
How do you migrate without losing local traffic? Protect four things a standard plan misses: the website link on your Google Business Profile, name, address and phone matching exactly everywhere, location and service-area page URLs, and LocalBusiness structured data. WPBuildAI checks those alongside the redirect map, because organic rankings can recover on schedule while the map pack quietly does not.
Does changing my website affect Google Maps rankings? Indirectly and genuinely. The map pack weighs relevance, distance and prominence, and your website supplies part of relevance and prominence through its content, its structured data and its consistency with your profile. A migration that breaks the linked page or changes your listed details damages that without touching the listing itself.
What should I check on my Business Profile after a migration? That the website link still resolves directly rather than through a redirect, that the name, address and phone on the profile match the site exactly, that any appointment or menu links still work, and that the linked page is the specific location page rather than the homepage if that is how it was set.
How long does local recovery take? Usually faster than organic, because the listing itself never moved and much of local ranking is independent of your site. Expect map pack positions to stay broadly stable through a clean migration, with any wobble settling in two to four weeks. A drop that persists past a month points at a broken link or changed details rather than at recrawl time.
When should you not worry about local at all? When you have no physical presence and no service area, since a national store or a remote software business has no map pack to protect. Also when the profile itself is the weak point rather than the site, because three reviews and half the categories unset is a local problem no migration caused and no redirect will fix.
