Moving a business is a local SEO event on the scale of a website migration — and it’s almost never treated like one. The physical move gets project-managed to the hour: movers booked, utilities transferred, signage ordered. The digital move gets a Google Business Profile address edit and a shrug — while the old address lives on across two hundred citations, the map re-anchors your proximity to a location your rankings weren’t built around, review platforms and data aggregators keep republishing the stale identity, and for the next six months some fraction of customers navigates to a building you no longer occupy.
The stakes are structural, not cosmetic. Local rankings rest on relevance, distance, and prominence — and a move rewrites the distance term overnight (you now compete in different proximity contests, winning some neighborhoods and losing others by geography alone) while putting the prominence term at risk (NAP inconsistency across the citation ecosystem is exactly the entity-confusion signal that suppresses pack visibility). Businesses that manage the transition deliberately typically stabilize within a quarter, often stronger than before if the new location is better positioned. Businesses that just edit the profile spend a year haunted by their own old address — duplicate ghost listings, misrouted customers, and rankings that never quite recover because half the web still disagrees about where they are.
This is the 90-day plan: the pre-move preparations that make everything easier (start two weeks out), the move-week sequence on the Business Profile itself (update, never close-and-recreate — the review-destroying mistake), the tiered citation cleanup that fixes the ecosystem in priority order, the website and schema updates that corroborate the new identity, the monitoring that catches ghosts early, and the honest expectations about what ranking recovery looks like when your proximity anchor moves.
A move rewrites your distance signal overnight and puts prominence at risk through NAP chaos — manage it like a migration. Pre-move (2 weeks out): inventory every citation (search your name, address, every phone number), baseline your rankings and review count, prepare the new NAP identity. Move week: update the address on the existing Google Business Profile — never mark the old one closed and create a new one (that’s how reviews and history get destroyed); expect possible re-verification at the new address; update the website (contact page, footer, LocalBusiness schema, location pages) the same day. Days 1–30: fix the tier-1 citations — the major data aggregators, top directories, and industry platforms that feed everything else. Days 30–90: work the long tail, hunt and merge old-address ghost listings, and refresh local signals (new-location photos, reviews mentioning the area, updated local links). Expect geographic ranking redistribution — stronger near the new address, weaker near the old — and judge recovery on the new location’s market, not the old baseline.
Pre-Move: The Two-Week Head Start
- Inventory the citation ecosystem. Search for your business name, current address (in every format it appears), and every phone number you’ve used — log each site that publishes your NAP: the majors (Google, Apple Maps/Apple Business Connect, Bing Places, Yelp, Facebook), the data aggregators that feed hundreds of downstream directories, industry platforms (Angi, Houzz, Healthgrades, Avvo — whatever your vertical’s are), local chambers and associations, and the long tail. A citation-tracking tool accelerates this; a spreadsheet suffices. This inventory is the project plan.
- Baseline everything. Screenshot pack positions for your money queries (from both old-area and new-area vantage points — you’ll want both comparisons later), record review counts, export analytics for profile actions (calls, direction requests). Post-move panic is mostly baseline-less panic.
- Prepare the new identity. Exact new address format (match USPS standardization — consistency starts with you), whether the phone number changes (strong recommendation: keep it if at all possible — a simultaneous address+phone change doubles the entity-matching difficulty), and the announcement assets: website banner, email/SMS to the customer base, social posts.
- Time the digital move to the physical one. Update the profile when you’re actually operating at the new address (or within the immediate transition window) — premature updates strand customers at an address you haven’t reached; late ones strand them at one you’ve left.
Move Week: The Profile Itself
- Update the address on your existing profile. One profile, one continuous history — the address is a field, not an identity. The alternative floating around small-business folklore — mark the old listing “permanently closed,” create a fresh one at the new address — is the single most destructive move available: it publishes a death notice to the map, orphans your reviews on a closed listing, and restarts your prominence from zero. (If you’ve already done this: reopen and correct the original, then merge properly.)
- Expect re-verification. Address changes commonly trigger it — postcard, phone, or increasingly video verification showing signage and operation at the new location. Prepare the evidence (signage up, branded presence visible) so verification is a formality; a profile stuck in verification limbo is the avoidable version of a suspension-grade outage. Make only the address change in this window — bundling name or category edits with a move multiplies review risk.
- Refresh the location-dependent fields: service area (for hybrid/SAB configurations — re-center it on the new base per SAB rules), parking/access attributes, and a first batch of new-location photos (exterior with signage, interior, team in situ) — both for customers and as verification-supporting evidence.
- Announce through the profile: a Google post about the move, updated description mentioning the new area — small signals, cheap to send.
Entity-matching across the citation ecosystem works on the NAP triad, and the phone number is its most stable leg — addresses change format across directories and names get abbreviated, but the number matches exactly or not at all. A move that keeps the number gives every algorithm and aggregator a persistent thread connecting old records to new; a move that changes both address and number presents the web with what looks like a different business, multiplying ghost listings and slowing consolidation for months. Port the number to the new location, forward it if you must operate dual lines temporarily — treat changing it as a separate project for a calmer year.
Same Week: The Website Must Corroborate
The profile claims a new address; the systems check your site for agreement — make the corroboration same-day:
- Every NAP instance on the site: contact page, footer (site-wide — one template edit), location/service-area pages, embedded map updated to the new pin, driving directions rewritten.
- LocalBusiness schema updated everywhere it appears — address, geo coordinates, and
areaServedif the service footprint shifts. Stale schema is a machine-readable contradiction of your own move. - Location-page content: if the move changes your neighborhood story (new landmarks, new “near X” relevance, different suburbs now closest), the location and city pages should reflect the new geography — this is also your chance to build relevance for the areas the new address makes winnable.
- A visible move notice for the transition quarter: banner or contact-page note (“We’ve moved to [address] as of [date]”) — it serves customers and dates the change for anyone verifying.
Days 1–90: The Tiered Citation Cleanup
| Tier | Targets | Window |
|---|---|---|
| Tier 1 — the feeders | Data aggregators (the handful that syndicate to hundreds of directories), Apple Business Connect, Bing Places, Yelp, Facebook/Instagram, your top industry platforms | Days 1–14 — these propagate downstream, so fixing them first means the long tail partially fixes itself |
| Tier 2 — the direct traffic | Directories that actually send you customers or links: chamber, BBB, association memberships, local media mentions you can request updates on, supplier/partner pages listing you | Days 14–30 |
| Tier 3 — the long tail | Everything else in the inventory, worked in batches; plus the ghost hunt (below) | Days 30–90, then quarterly maintenance |
The ghost hunt: from day 30, re-run the audit searches (old address, business name, phone) monthly — you’re looking for auto-generated listings at the old address, directory records that reverted from a stale feed, and the old-location profile someone “helpfully” recreated. Each ghost gets the standard treatment: claim, align, merge (or report if it was never yours). Expect the ecosystem to fight you for a quarter — aggregator caches and directory refresh cycles mean corrected records occasionally revert; the monthly sweep catches reversions while they’re young.
Post-move, the distance term of local ranking re-anchors to the new address: packs near the new location strengthen over weeks; packs near the old one fade — that’s physics, not failure, and no citation cleanup reverses it. The panic pattern to avoid: interpreting the old-neighborhood fade as ‘the move broke our SEO’ and responding with rapid profile edits (category changes, name tweaks, service-area inflation) that pile re-review risk onto an already-sensitive profile. Judge the transition against the right baseline — the new location’s market opportunity, which you screenshot-baselined pre-move — and give the redistribution its 4–8 weeks. If you must keep serving the old neighborhood competitively, the honest tools are the website (a strong area page), paid coverage (Search geo-targeting, LSA service area), and eventually the review corpus mentioning that area — not settings archaeology on the profile.
The Signal Rebuild: Making the New Address Rank
- Review velocity, immediately and geo-flavored: the post-move months are exactly when the systematic review engine earns most — fresh reviews signal a thriving relocated business, and customers naturally mentioning the new area/neighborhood build relevance the address alone doesn’t. (“Great to have them in [new area] now” is a ranking asset.)
- Photo stream from the new location: ongoing uploads — jobs, team, premises — date-stamped evidence of operation that also feeds the profile’s freshness.
- Local links for the new geography: new chamber, neighborhood association, local sponsorships, “new to the area” local-media angles — the prominence layer that tells the wider web, not just directories, where you now live.
- Paid bridge: Search and LSA geo-settings updated day one, with a temporary budget lean toward the new area while organic re-anchors — the same bridging logic as any local visibility gap.
5 Common Post-Move Mistakes
- Close-and-recreate. The review-destroying, history-orphaning cardinal error — the address is a field on your existing profile.
- Profile-only thinking. One edit on Google, two hundred stale citations everywhere else — the ecosystem, not the profile, is the project.
- Changing the phone number simultaneously. Severing the NAP triad’s most stable thread exactly when entity-matching needs it most.
- Bundling edits with the move. Address + name + category in one week reads as instability to review systems that were already watching the address change.
- Judging recovery against the old map. The old neighborhood’s packs were the old address’s assets; the scoreboard is the new market, on the baseline you captured for it.
Frequently Asked Questions
How long until my rankings recover after a move?
Split the question in two, because two different things are happening. Entity stabilization — the systems agreeing on your new identity — typically takes 4–8 weeks when the cleanup is run properly: profile updated and re-verified quickly, website corroborating same-day, tier-1 citations fixed in the first fortnight. During that window expect some volatility as conflicting signals reconcile. Geographic redistribution — where you rank — is permanent and starts immediately: proximity re-anchors to the new address, so packs near it strengthen over the following weeks while old-neighborhood packs fade regardless of how perfect your cleanup is. A well-executed move usually shows the new-area packs consolidating within one to two months and the overall profile (calls, direction requests) matching or beating baseline within a quarter — often beating it, since businesses usually move to better locations. The moves that take a year to ‘recover’ are almost always the ones fighting self-inflicted wounds: close-and-recreate resets, phone changes, or citation ecosystems never actually cleaned.
Do I really need to fix every citation, or just the big ones?
Work the tiers, and let honesty about effort guide the tail. Tier 1 is non-negotiable: the data aggregators and major platforms feed the rest of the ecosystem — correcting them fixes hundreds of downstream records passively and prevents the re-pollution cycle where stale feeds overwrite your manual fixes. Tier 2 — directories with real traffic, links, or industry weight — earns manual attention because those records affect customers and rankings directly. The long tail is where proportion applies: a directory nobody visits with a slightly off address format is a low-grade inconsistency, not an emergency; batch-fix what you reasonably can in the 30–90 window, prioritize any long-tail record that (a) ranks for your brand searches, (b) feeds other sites, or (c) keeps spawning ghost listings, and accept that a spotless long tail is asymptotic. The functional target isn’t perfection — it’s that the sources algorithms and customers actually consult agree on one identity, and that the monthly ghost-hunt finds nothing new. Most businesses reach that state without ever touching the bottom hundred directories.
We're moving only two miles away. Does all this still apply?
The process, yes; the redistribution drama, much less. A short move within the same city keeps most of your proximity contests intact — you’re still ‘the plumber near’ largely the same searchers — so expect ranking continuity rather than a geographic reshuffle, with modest edge effects (slightly stronger toward the new address, slightly weaker at the old margin). What doesn’t shrink with distance is the consistency work: NAP inconsistency harms entity trust identically whether the addresses are two miles or two hundred apart, so the profile update, same-day website/schema corroboration, tiered citation cleanup, and ghost monitoring all run at full strength. Short moves do earn two simplifications: re-verification tends to be smoother (same market, same operation, often same everything-but-street), and you can skip the new-market strategy work — no new city pages or area repositioning needed, just the address mechanics done thoroughly. The trap in short moves is complacency: ‘it’s basically the same location’ is how two-mile moves end up with the same 200 stale citations as cross-town ones.
Should I keep the old address on my website for a while 'for SEO'?
No — keeping the old address live as structured business data (footer NAP, contact page, schema) is precisely the mixed signal the whole recovery plan exists to eliminate: your own site contradicting your own profile is the worst possible source of entity confusion, because the systems weight your site heavily as corroboration. What’s legitimate and useful is a dated transition notice: a banner or contact-page line — ‘We’ve moved from [old address] to [new address] as of [date]’ — keeps context for customers and crawlers without asserting the old address as current; retire it after a quarter. Handle the machine-readable layers strictly: schema carries only the new address from day one, the embedded map moves to the new pin, and any location page for the old address either updates to the new one or 301-redirects to its replacement — never a live page presenting the old location as operational. If the worry behind the question is losing old-neighborhood rankings: the address on your site was never what earned those packs (proximity was), and no footer archaeology preserves them — serve that area through an honest area page and paid coverage instead.
What do I do about reviews that mention the old location or old area?
Nothing destructive — they’re assets with a patina, not liabilities. Old reviews carry your service quality, your response history, and your prominence; their geographic references fade in relevance naturally as new-location reviews accumulate on top, and review recency weighting means the corpus’s ‘center of gravity’ follows your operations within a few quarters on its own. The productive moves are all additive: run the review engine hard post-move so fresh, new-area-flavored reviews stack quickly (the request nudge — ‘it helps neighbors in [new area] find us’ — earns natural geo-mentions); respond to a few prominent older reviews in ways that gently signal continuity (‘thank you — we’re now serving you from our new [area] location’), which updates context for future readers without touching the reviews themselves; and feature new-location reviews on the website’s location pages. What not to do: attempt to remove or dispute old reviews for geographic staleness (they don’t violate anything, and pruning your own history cuts prominence), or stress about a customer mentioning the old street — a rich multi-year review corpus that visibly spans a move reads, to humans and systems alike, as exactly what it is: an established business that grew.
Moving locations without losing your local visibility?
We’ll inventory your citation ecosystem before the boxes are packed, execute the profile and website transition on move day, and run the 90-day cleanup that keeps the web agreeing on where you are — while paid coverage bridges the re-anchoring.
Get a Move Recovery Plan Explore SEO Services