Back to Journal
7 min readDigital Horizon

Switching Web Providers Without Losing Your Google Rankings: A 2026 Migration Playbook for Northern Nevada Service Businesses

The average website migration loses 20–60% of organic traffic and takes 2–12 months to recover. Here is the exact playbook Digital Horizon uses to move Northern Nevada service sites without losing a single ranking.

Two glowing thresholds connected by an arc of light — the visual metaphor for moving a website from one provider to another without losing the value already accumulated.

Every service business owner eventually asks the same question: is it time to leave the person who built our website?

The site loads slow, the copy is a decade old, edits take three weeks, and the phone has been quieter than it used to be. Somewhere in the same conversation, someone floats the word "redesign." That is where the trouble usually starts.

Here is the part almost nobody warns you about: the average website migration loses 20–60% of its organic traffic within the first two weeks, and industry data from 2026 puts full recovery at 2–12 months — with a meaningful share of sites that never fully recover at all. For a Carson City plumber or a Reno flooring installer, that is not a rounding error. That is a full quarter of missed jobs before the "new" site starts paying for itself.

The good news: almost every catastrophic migration we see in Northern Nevada is caused by the same handful of avoidable mistakes. This is the playbook we use at Digital Horizon to move a site from an old provider to a new one and keep the ranking, keep the phone ringing, and keep the calendar full.

Why "just redesigning the site" is quietly one of the riskiest things a service business can do

The reason migrations tank rankings has nothing to do with the look of the new site. Google does not care about your color palette. What Google cares about are the signals attached to every URL you already have — the backlinks, the internal link equity, the crawl history, the schema markup, the Core Web Vitals scores, and the dozens of small "this business is real" verifications built up over years.

When a new provider spins up a fresh site, one or more of the following happens:

  • URLs change (e.g., /carson-city-water-heater-repair becomes /services/water-heater), and the old URLs 404 instead of redirecting.
  • Redirects are set up, but they redirect to the homepage instead of the closest matching page — a signal Google reads as "this content is gone."
  • Schema markup — LocalBusiness, Service, Review, FAQ — is not carried over. In 2026 that also means the AI Overviews stop citing you.

The Google Business Profile still points to the old URL for weeks after launch.

  • The new site loads slower than the old one, and Core Web Vitals degrade at the exact moment Google is re-evaluating you.

Any one of those causes a temporary slump. Combine three of them and you have a 60% traffic collapse that takes half a year to climb out of.

The five checks that separate a clean migration from a disaster

1. Build a 1:1 URL map before you touch anything

Every page on the old site gets a row in a spreadsheet. Old URL, new URL, page title, target keyword, number of backlinks, and top three internal links pointing at it. If a new URL does not exist for an old page, that page either gets rebuilt or gets a 301 redirect to the closest topical match — never to the homepage, and never to a category page that does not answer the same question.

This is the single most valuable document in a migration. It is also the one most agencies skip.

2. Preserve the schema — including the location data

If your current site has LocalBusiness, Service, and Review schema, the new site must have the same schema on the same pages, with the same NAP (name, address, phone) formatting. In 2026 this is not just an SEO signal; it is what AI search engines read to decide whether to cite you in an AI Overview. Miss it and you disappear from both classic search results and the AI summaries above them.

3. Match or beat the old site's Core Web Vitals

Do not launch until the new site scores at or above the old one on Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. If the old site loaded in 1.4 seconds and the new one loads in 3.2, Google will re-rank you the moment it crawls the new pages. A pretty site that is slower than what it replaced is a downgrade, not an upgrade — the Core Web Vitals thresholds we wrote about earlier this month still apply.

4. Keep everything else stable during the migration window

The two weeks before launch and the four weeks after are the wrong time to also change your Google Business Profile primary category, run a big Google Ads test, rename service pages, restructure your navigation, or change your business phone number. Every one of those is a signal in isolation. Fired together, they look to Google like a business that just changed identity.

5. Test the migration on a staging URL that Google cannot crawl

The new site should live on staging.yoursite.com or a similar URL, protected by a password and blocked by robots.txt and a noindex tag, until launch day. We have seen more than one migration fail because Google indexed the staging site first, then treated the production launch as duplicate content.

The launch-day checklist that fits on one page

Print this out. Tape it to the wall. Do not skip a line.

  1. Deploy the redirect map at the DNS or server level. Every old URL must return a 301 to its mapped new URL.
  2. Remove noindex tags on the production site. This is the #1 self-inflicted wound in migrations — a forgotten staging-site directive that quietly de-indexes the whole domain.
  3. Update the sitemap and submit the new sitemap to Google Search Console.
  4. File a Change of Address in Search Console if the domain is also changing.
  5. Update the Google Business Profile website field and every citation you can reach — Yelp, Nextdoor, BBB, industry directories.
  6. Verify SSL and confirm no mixed-content warnings.
  7. Recrawl the old URL list with a tool like Screaming Frog to confirm every redirect resolves in one hop and returns a 200 on the new URL. Redirect chains bleed link equity.
  8. Load the site on a phone, on cellular, in Carson City — not on office Wi-Fi. Local performance is what matters.

What to watch for the four weeks after launch

Rankings will wobble. That is normal. What is not normal, and what should trigger an immediate audit:

  • Impressions in Search Console drop by more than 30% for more than 7 days.
  • The number of indexed pages drops instead of rising.
  • Core Web Vitals move from "Good" to "Needs Improvement" or "Poor."
  • Any indexed pages start showing 404s in the coverage report.

Most sites we migrate cleanly are back to their pre-migration organic traffic within 3–5 weeks, and above it within 8–10 — because the new site is faster, better-structured, and easier for Google to crawl than the one it replaced. That is the whole point of switching. But the "faster and better" only pays off if the migration itself did not throw away three years of accumulated ranking signal on the way there.

The bottom line for Northern Nevada service businesses

A well-run migration is not free traffic, but it is close. A badly run migration is one of the fastest ways a healthy local business goes from booked out to sitting quiet — and by the time you notice, the damage takes months to reverse.

If you are thinking about leaving your current provider, do not sign a contract with the next one until they show you their redirect map template, their schema migration process, and the specific Core Web Vitals target they are shooting for on your new build. If they cannot answer those three questions in the first meeting, read this before you sign anything.

If you would rather we handle it, that is what our web design and SEO teams do every week in Carson City, Reno, and across Northern Nevada. Book a free 30-minute discovery call and we will walk your current site with you and tell you honestly whether a migration is worth doing this year — or whether the site you have can be salvaged for a lot less money.

Either way: do not let a shiny new site cost you the phone calls the old one was already earning.

Work with us locally

Web design, SEO, and growth in Northern Nevada

We work with clients across Carson City, Reno, Lake Tahoe, and the surrounding region. Pick the closest market to see scope, timelines, and pricing.