Site Migration for Nashville Local Businesses
On this page
A site migration changes the addresses Google has indexed and the signals attached to them, whether you are moving to a new domain, re-platforming the CMS, restructuring URLs or merging sites. Google says to “Expect temporary fluctuation in site ranking during the move” (Site moves and migrations). What decides the outcome is mostly settled before launch: a complete inventory, a baseline to measure recovery against and a redirect map with no gaps. After launch, the job is patience and diagnosis against that baseline, not improvisation during the expected dip.
Before launch
1. Build the URL inventory
List every page Google currently knows about, pulled from the CMS, the XML sitemap, a full crawl and Search Console, then reconcile them into one master list. URLs missing at this stage become orphaned, unredirected pages after launch, which is how migrations leak rankings.
2. Capture baselines while the old site is live
Record current rankings for the queries that matter, organic traffic by page, the backlinks pointing at key URLs, the technical state (indexed page count, Core Web Vitals, crawl stats) and a snapshot of important content. When rankings move after launch, the baseline tells you whether you are inside the normal transition or losing ground, and which pages slipped. Without it, every later decision is a guess.
3. Map every old URL
Every old URL needs a decision, with none left unmapped:
- One to one: an old URL maps to its direct equivalent.
- Many to one: several thin pages map to a stronger combined page.
- Removed pages: redirect only where a page on the new site replaces what the old one offered, such as the category or section above it when that page covers the same need. Where nothing replaces it, let the old URL return an error; Google’s migration guide says to “make sure those URLs correctly return an HTTP 404 or 410 error response code on the new site.”
- Structural changes: map the old hierarchy onto the new one section by section.
Never default unmapped or removed pages to the homepage. Google’s guide warns: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site. This can confuse users and might be treated as a soft 404 error.” A partial map is a partial safety net.
4. Choose the window
Launch timing is a lever you fully control. You do not want the expected fluctuation landing on your highest-revenue window. Nashville’s calendar makes this concrete: avoid launching into CMA Fest week in June, football weekends if game-day traffic matters to you, or peak tourism stretches when downtown and Broadway businesses are busiest. A wedding venue should migrate in its slow season, not during peak booking months.
5. Separate the changes
Google’s guidance is to “Plan your changes to your site one after the other, not everything at the same time.” If a domain move, a redesign and a content overhaul land together, you cannot tell which change caused a problem. Migrate, stabilize, then iterate.
Launch day
- Launch on a weekday morning, not a Friday afternoon or a weekend, so the team is available to catch and fix problems.
- Have the people who can act, the developer and whoever manages Search Console, standing by.
- Spot-check redirects from the map as soon as they are live: each old URL should land on its mapped destination in one hop.
- If both the old and new domains are verified in Search Console and the redirects are live, use the Change of Address tool, which lets you “forward your old site signals to your new site” (Change of Address tool).
- Update your Google Business Profile website link and the major citations to the new URLs, so local signals are not stranded.
The weeks after
A normal migration shows a visibility dip and ranking fluctuation as Google recrawls the new URLs, processes the redirects and reassigns signals. Google’s rule of thumb: “for medium-sized websites, it can take a few weeks or more for Google to gradually start showing the new URLs instead of the old ones (and for larger sites, even longer).” That is general guidance, not a guaranteed timeline, and it depends on the site’s size, the scale of the change and how cleanly the redirects were done. Do not put a fixed percentage or number of weeks on it.
Keep the redirects in place. The Change of Address help says to “Maintain the redirects for at least 180 days–longer if you still see any traffic to them from Google Search,” and the site-move guidance goes further: “Keep the redirects for as long as possible, generally at least 1 year.” Plan for the year.
| Normal turbulence | Signs that justify action |
|---|---|
| A visibility dip in the first weeks | Pages returning errors instead of redirecting |
| Rankings moving while old and new URLs trade places | Redirects landing on the wrong destinations |
| Old URLs still appearing for a while | The new site not being crawled |
| A dip that stabilizes | A dip that keeps deepening well past the expected window |
If recovery stalls
Diagnose against the baseline rather than thrashing. Check that every old URL that should redirect does, and lands on the right page, that no redirect chains crept in, that the new pages are being crawled and indexed, that the content Google ranked still exists on the new URLs, and that your Business Profile and major citations point to the new URLs. Compare what the baseline said you had with what the live site now does, and find the gap.
Watch for five mistakes:
- An incomplete redirect map leaves pages stranded.
- Changing content during the migration confounds the diagnosis, because you cannot tell whether a drop came from the URL change or the new copy.
- Ignoring local listings strands local-pack signals even when the website redirects are perfect.
- Panicked intervention, reverting redirects or restructuring again day by day in the first weeks, prevents the stabilization it is trying to force.
- No baseline means flying blind through all of it.