What Happens To Your Rankings When You Rebuild Your Website

Most traffic collapses after a redesign are entirely predictable, and almost all of them were preventable in the two weeks before launch.

The pattern is consistent. New site goes live, everyone is pleased with how it looks, and six weeks later organic traffic is down forty per cent with nobody able to say exactly when it started.

Here is what actually causes that, and what any competent SEO Agency should be doing alongside the build rather than after it.

Redirects Are The Single Biggest Cause Of Post Launch Traffic Loss

If your URLs change and nothing maps the old ones to the new ones, you have thrown away every link and every ranking signal those pages accumulated.

This sounds obvious and it is still the most common failure, usually because the redirect map gets treated as a launch day task rather than a pre launch deliverable. Someone exports a list at the last minute, misses the pages nobody remembered existed, and those pages return errors to both users and search engines.

The map should be built from a full crawl of the existing site, not from the sitemap and not from memory. Old blog posts, discontinued service pages, PDF downloads, and pages linked from external sites you forgot about all need destinations.

One redirect rule worth insisting on: every old URL points to the closest equivalent page, not to the homepage. Bulk redirecting everything to the homepage is treated as a soft error and passes almost nothing.

Content Removed During A Redesign Takes Its Rankings With It

Redesigns tend to shorten pages, because shorter pages look cleaner.

The problem is that the text being cut is frequently the text that ranked. A service page rewritten from 900 words to 200 for visual reasons loses the depth that made it competitive, and the ranking follows within a couple of months.

Before any rewrite, identify which pages currently produce organic traffic and enquiries. Those pages get treated as fixed assets. You can redesign around them, restructure them, improve them, but you do not casually delete two thirds of the content on your best performing page because the new layout prefers whitespace.

If a page must be shortened, the information belongs somewhere else on the site rather than deleted outright.

Technical Signals Get Rebuilt From Scratch And Often Get Rebuilt Wrong

Everything invisible has to be recreated on the new site, and this is where things silently break.

The recurring casualties: schema markup that existed on the old templates and was never rebuilt, meta titles and descriptions replaced with template defaults, canonical tags pointing at staging URLs, and a robots file that carried over the staging environment's block on everything.

That last one is not rare. A site launched with a disallow directive still in place is invisible to search engines, and the symptoms take weeks to appear because indexing decays gradually rather than instantly.

Check the robots file on launch day. Then check it again a week later, because deployments overwrite things.

Speed Gains Are The Main Ranking Upside Of A Rebuild

The reason to do this at all, from a search perspective, is that a rebuild is your one opportunity to fix performance properly at code level.

Core Web Vitals affect ranking and conversion simultaneously, which makes them the highest return work in any rebuild. Big Hunt's stated benchmarks for Web Development Services are 1.4 second average load times and 90+ Core Web Vitals scores, achieved through performance budgets enforced at build time rather than optimisation attempted afterwards.

That distinction matters more than the numbers. Performance decided during the build is cheap. Performance retrofitted onto a finished site is expensive and usually partial, because the causes are architectural rather than cosmetic.

Platform Choice Decides What Is Possible Later

Choose for what you will need in three years rather than what looks easiest now.

WordPress gives full control over technical implementation and full opportunity to accumulate plugin bloat. Webflow and Squarespace are faster to launch with real ceilings on schema and performance control. Shopify handles commerce well and constrains URL structure. Custom stacks like Next.js offer the most control and the highest dependency on whoever built it.

None of these is wrong. The mistake is choosing one without knowing which constraints you are accepting, then discovering the ceiling eighteen months later when you need something the platform will not do.

Ask directly what the platform will prevent you from doing. A partner who names three limitations is being straight with you.

Benchmarks Set Before Launch Are The Only Way To Know What Happened

Record the numbers before the old site disappears, because afterwards you cannot.

The list is short. Organic sessions by month for the last year, ranking positions for your main terms, conversion rate, load time, Core Web Vitals scores, and which pages produced enquiries. Screenshot the lot.

Without that baseline, every post launch conversation becomes an argument about whether things got worse, and nobody can settle it. With it, success becomes a number rather than an opinion, and a genuine problem shows up in week two rather than month three.

Expect A Dip, Then Judge At Ninety Days

Some fluctuation after launch is normal. Search engines need to recrawl the new structure, reassess the pages, and reconcile the redirects, and that takes weeks rather than days.

A modest dip for two to four weeks followed by recovery is the healthy pattern. A steep drop that continues into week six is a problem, usually redirects or an indexation block, and it needs investigating immediately rather than waited out.

The full picture arrives at around ninety days. That is also roughly when the performance improvements start showing up as ranking gains, which is why a rebuild done properly tends to end above where it started rather than merely recovering.

NotionMind's sequence illustrates it: 34 per cent organic keyword growth and a first confirmed Gemini citation following a full technical rebuild. The visibility gains came after the rebuild, not despite it.

Timeline And Ownership Questions To Settle Before Signing

Marketing sites typically take six to ten weeks. Larger commerce or product platforms run twelve to twenty. Anyone promising a full custom build in three weeks is using a template and describing it differently.

Then the question people forget until it is too late: who owns the code, the CMS and the hosting when this finishes. You should leave with all three and the ability to make your own changes without raising a ticket.

Agency lock in costs more over five years than the rebuild did.

The One Thing To Do Before Your Next Redesign Starts

Crawl your current site and export every URL, before anyone touches anything.

That single file is what makes the redirect map possible, and it is the cheapest insurance available in this entire process. Do it this week if a rebuild is even being discussed.