Will a New Website Cost You Your Google Rankings?

Not if every address that works keeps working. A new website loses rankings when the addresses Google already knows stop working, and that part is in your control.

Google doesn’t rank websites so much as it ranks pages, and every page lives at an address. The platform underneath isn’t what Google filed. It filed /services/roof-repair/ and /blog/how-long-does-a-roof-last/ and a few hundred more, each with the ranking it earned over the years. Move a page without telling Google where it went and that ranking stays behind at the old address, attached to nothing.

So the question to ask before a rebuild isn’t “will this hurt our SEO?” It’s narrower and easier to check: what happens to each address we have today?

Why does a new website lose rankings?

Google’s own site-move guide is short and unglamorous. Map every old address to a new one, redirect each old address to its new one permanently, and “expect temporary fluctuation in site ranking during the move.” It adds that this is normal and that rankings “will settle down over time.” ¹ Source 1 Google Search Central, “How to move a site” (site moves with URL changes), last updated August 20, 2026: “It’s important to map your old site’s URLs to the URLs for the new site”; “Expect temporary fluctuation in site ranking during the move”; “This is normal and a site’s rankings will settle down over time”; “301 and other permanent redirects don’t cause a loss in PageRank.” × A permanent redirect is a forwarding address: anyone, person or crawler, who asks for the old page is sent on to the new one, and the ranking goes with them.

When a move goes badly, it’s usually one of four things.

Pages that disappear

An address that now returns “page not found” gets dropped. Google is blunt about it: pages that return an error in the 400s aren’t indexed, and pages already indexed are removed. ² Source 2 Google, HTTP status codes and Google’s crawlers, last updated February 4, 2026: “Google doesn’t index URLs that return a 4xx status code, and URLs that are already indexed and return a 4xx status code are removed from the index.” ×

Pages forwarded to the wrong place

The shortcut of sending every old page to the new home page looks tidy and fails quietly. Google warns against redirecting many old addresses to one irrelevant page and may treat those redirects as missing pages anyway. ³ Source 3 Google Search Central, “How to move a site”: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site.” Google, Troubleshoot crawling errors, last updated December 18, 2025: soft 404 pages “are excluded from Search.” ×

Launch-day leftovers

Staging sites are hidden from Google on purpose, with a noindex tag or a block in the robots file. If that setting survives the launch, the new site tells Google to stay away, and Google does: a page with noindex is dropped from search results entirely. Google’s checklist has a line for exactly this. ⁴ Source 4 Google Search Central, “How to move a site”: “Don’t forget to remove any noindex or robots.txt blocks that were only needed for the migration.” Google, Block search indexing with noindex: Google “will drop that page entirely from Google Search results.” × The same goes for canonical tags still pointing at the staging address, and for a sitemap that lists it.

Changing everything at once

A new platform, new addresses, new page structure and rewritten content all on one day gives Google a stranger to assess. Google’s advice is to change one thing at a time, and its Search Console help says plainly that combining a move with a redesign of content and URL structure “will probably” cost some traffic while Google relearns the pages. ⁵ Source 5 Google Search Central, “How to move a site,” “Change only one thing at a time.” Search Console Help, Change of Address tool: “If you combine a site move with a redesign of the site’s content and URL structure in the new location, you will probably see some traffic loss as Google might need to relearn and reassess the individual pages.” × That doesn’t mean you can’t improve the site. It means every change should be one you chose, with a reason, and not one that came along with the new platform.

The addresses nobody lists

Any agency will map the pages in the main navigation. The losses come from the rest.

A site that has been running for a few years has addresses its owners have never seen. On a home builder’s site we moved this year, the old sitemap listed more tag archive pages than real pages. Most were thin and deserved to go, but some were still earning impressions, and they needed a decision, not an accident.

The usual suspects:

• page two, three and onward of the blog and of every category and tag
• tag, category and author archive pages
• old campaign and event pages that are no longer linked but still get visits from old emails
• PDFs, brochures and plan sheets linked from other sites
• content on a separate subdomain, like a resource center, a careers site or a product catalog
• the same address with and without a trailing slash, and with tracking codes attached (?utm_source=, ?gclid=)
• redirects the old site already had, which often chain three or four hops deep after years of renamed pages

You won’t find all of them by clicking around. Build the list from every source that knows: the old site’s sitemaps, Google Search Console’s record of every page that appeared in results over the last year, the landing pages in your analytics, the pages other sites link to, and the old platform’s own redirect list. Merge them, remove duplicates, and you have the inventory.

Keep, move or retire: decide for every address

With the inventory in hand, each address gets one of three decisions. Our standard is to keep every address that already works, move a page only when the new address is better for visitors and for Google, and forward every page that moves.

Keep

Keep is the default. If /about-us/ works and ranks, the new site serves the same page at /about-us/. There’s no ranking risk in an address that doesn’t change.

Move

Moving needs a reason. Good ones: bringing content home from a separate subdomain, grouping articles that were scattered at the top level of the site under /blog/, fixing an address so wrong it confuses people. Each move gets a permanent redirect (a 301 or 308) straight to its final destination. Google asks for the final destination directly and, if chains can’t be avoided, ideally no more than three hops; its crawlers give up after ten. ⁶ Source 6 Google Search Central, “How to move a site”: redirect “to the final destination directly”; if chains can’t be avoided, “ideally no more than 3 and fewer than 5.” Google, HTTP status codes: “By default, Google’s crawlers follow up to 10 redirect hops.” × When the old site already had chains, flatten them, so a page renamed four times forwards in one step.

Retire

Retiring is for pages that shouldn’t exist anymore. Retired pages still get a forwarding address, to the closest page that answers the same need, never to the home page by default.

How long to keep redirects

Keep them. Google’s guidance is “as long as possible, generally at least 1 year”, and it suggests considering keeping them indefinitely for people’s sake. ⁷ Source 7 Google Search Central, “How to move a site”: “Keep the redirects for as long as possible, generally at least 1 year”; “From users’ perspective, consider keeping redirects indefinitely.” Google, Redirects and Google Search: “The 301 and 308 status codes mean that a page has permanently moved to a new location.” × Old links live on in emails, bookmarks, directories and other people’s websites. We keep them permanently, because a redirect costs nothing to keep and a broken link costs a visitor every time.

Launch day

The order matters less than not skipping any of it.

1. Remove every staging block: the noindex tags, the robots-file rule, the password.
2. Check that each page’s canonical tag points to itself on the live domain.
3. Replay the whole inventory against the live site. Every old address should land on a working page in one hop. Spot-checking twenty is how the other two hundred get missed.
4. Submit the new sitemap in Search Console. Google calls it helpful right after a launch or a move, and notes that crawling can take anywhere from a few days to a few weeks. ⁸ Source 8 Google Search Central, “How to move a site”: the Change of Address tool is needed only “when moving from one domain or subdomain to another,” not for “moving paths within the same domain.” Google, Ask Google to recrawl your URLs: a sitemap “can be very helpful if you just launched your site or recently performed a site move”; “Crawling can take anywhere from a few days to a few weeks.” ×
5. If the domain itself changed, use Search Console’s Change of Address tool. If you stayed on the same domain, you don’t need it.
6. Submit every form on the site once and confirm the lead arrives where your team expects it. Rankings get the attention, but a broken inquiry form costs more.

The first 30 days: what normal looks like

Google says a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer. ⁹ Source 9 Google Search Central, “How to move a site”: “a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer”; “Search Console is your friend, especially during a site move.” × In that window you’ll see old addresses still showing up in results. That’s expected, as long as each one forwards to its new page. You’ll see some pages wobble up and down. Also expected.

What isn’t normal is a growing list of “not found” errors in Search Console, or a key page that drops out and stays out. That’s a missed address, and it’s fixable the same day if someone is looking. So someone should be looking, every few days for the first month.

Be careful with launch-week numbers in both directions. A new site often gets a burst of attention in its first week, and a dip in the first few days doesn’t mean much either. Judge the move on a full 30 days against the 30 before it.

When we moved Travars Built Homes, a custom home builder in North Carolina, the first week after launch was the busiest, as launch weeks usually are, and then traffic settled. Over the first 30 days, clicks from Google rose from 371 to 408 against the old site’s last 30, and their average position in Google results improved from 18.5 to 15.6. ¹⁰ Source 10 Lynton, Travars Built Homes case study, lyntonweb.com/case-studies/travars-built-homes: first 30 days on the new site against the last 30 days on the old one. × That was with hundreds of addresses moving, including a whole floor plan catalog brought home from a separate subdomain.

What a careful move buys you

Most of this guide is defense, because that’s where the fear is. The better reason to do it carefully is that a move is the one time you get to fix the structure of a site without starting over.

A blog scattered across the top level of the site can be grouped under one folder, which gives Google a clearer picture of what the site is about. Content split off onto a subdomain or a second platform can come back onto the main site, so every visit to it counts toward the site you’re trying to grow. Pages that were slow because of a decade of plugins can be rebuilt light, and the pages Google and AI assistants struggled to read can be rebuilt so their words are in the page itself. We wrote about that last part in AEO is an architecture problem.

None of those gains requires giving up what the old site earned. In Travars’ case the floor plans moved off their separate subdomain, for reasons we lay out in What a Home Builder’s Website Needs, every old plan address forwarded to its new page, and within the first month the plan library was one of the four pages bringing in the most search traffic. Bringing the plans home is what put that traffic on the main site, and the forwarding addresses are what kept the ranking the plans had already built.

What to ask before anyone builds

You don’t need to read redirect files to hold a migration to this standard. Ask your agency or your team for four things, in writing, before design starts:

• the full inventory of current addresses, and which sources it was built from
• the decision for each address: keep, move or retire, with the destination for every one that changes
• who removes the staging blocks on launch day, and how they’ll prove it
• who watches Search Console for the first 30 days, and how often

If the answer to the first one is a list of the pages in the navigation, the move isn’t ready to start. If you’re still weighing whether to move at all, our six-factor WordPress evaluation and the guide to what happens to your content when you leave HubSpot cover the decision before this one.