Home/Blog/Design

Choosing a Website Redesign Company Without Losing Your Traffic

Design4 min read
Designer's desk during a website redesign, with layout mockups and a wireframe on screen

Short answer

A website redesign company earns its fee if the site gets better and the traffic survives. Google's guidance is unusually direct about how: change one thing at a time, map every old URL to a new one, and keep the redirects in place for at least a year.

Key takeaways

  • 01Google's advice is explicit — plan changes one after the other, not all at the same time.
  • 02Permanent redirects should stay for at least a year, not until the next sprint.
  • 03A medium-sized site takes a few weeks for most pages to be reindexed.
  • 04Ranking fluctuation during a migration is expected, not proof that something broke.

What a redesign actually puts at risk

The design is rarely the risky part. The risky part is that a redesign usually arrives with new URLs, a new content system and rewritten copy attached, and Google lists site moves alongside algorithmic updates and technical faults as one of the six causes of a search traffic drop. Every page currently earning visits is an asset with an address, and a redesign is the moment those addresses change. Ask a prospective web development partner how they intend to protect them.

This is not an argument against redesigning. It is an argument for knowing which change caused which outcome, which is only possible if the changes are separable.

Change one thing at a time

Google's site-move documentation states it plainly: "Change only one thing at a time. Plan your changes to your site one after the other, not everything at the same time." A single release that swaps the visual design, the URL structure and the CMS produces one outcome and no way to attribute it. Sequenced releases produce four readable results.

ChangeWhat it risksShip separately?
New visual designConversion rate, layout stabilityYes — measure it alone
New URL structureRankings on every existing pageYes — this is the risky one
New CMS or platformRendering, status codes, redirectsYes
New domainAll of the above, togetherYes, and last
Google recommends sequencing these rather than shipping them together.

The URL map is the real deliverable

Before anything moves, Google's guidance is to build a mapping from current URLs to their new form, starting with the important ones and drawing on sitemaps, server logs and analytics. Embedded images and videos count — they have URLs too, and they are the ones teams forget. Redirects are then served from the server as permanent ones, 301 or 308, and for small to medium sites Google recommends moving every URL at once rather than a section at a time.

Old and new website layout mockups side by side during a website redesign URL mapping exercise
Old address to new address, page by page. The unglamorous document that decides whether the redesign holds.

The status codes nobody demos

Google treats a 301 as a strong signal that the target should be processed, drops previously indexed URLs that return 404 or 410, and follows up to ten redirect hops by default — which is what makes chained redirects from two successive redesigns a real problem. The failure mode to watch for is the soft 404: a page whose content reads as an error while the server still answers 200. Retired pages that quietly render an empty template are the usual cause, and they consume crawl budget that should be going to real content.

How to tell whether it worked

After the move, Google's own checklist is Search Console: indexed counts falling on the old sitemap and rising on the new one, crawl errors in the page indexing report, and impressions in the performance report. Expect movement while this settles — Google says a medium-sized site takes a few weeks for most pages, and that ranking fluctuation during a migration is normal.

To judge whether the new site is better, use field thresholds rather than a lab score: LCP under 2.5 seconds, INP of 200ms or less, CLS of 0.1 or less, each measured at the 75th percentile of real page loads. That is also the honest way to judge the SEO side of a redesign. See our work, or tell us what you are planning.

Frequently asked questions

If they are reasonable, yes. Changing URLs is the single riskiest part of a redesign, and cosmetic improvements to a URL rarely repay the migration cost. Change them only when the structure itself is the problem.

Google says a medium-sized site takes a few weeks for most pages to move in its index, and larger sites longer. Submitting the new sitemap speeds up discovery. Watch weekly rather than daily during that window.

You can, but Google advises against combining changes. If the schedule forces it, launch the CMS on the existing URLs first, verify status codes and rendering, then handle URL changes as a separate release.

A URL map covering every indexed page including images and video, the redirect rules implemented server-side, a baseline of current traffic and Core Web Vitals, and a stated plan for who watches Search Console afterwards.

Eventually, but not soon. Google's guidance is at least a year, and indefinitely is better for users following old links. Treat the redirect map as infrastructure to maintain, not launch-day scaffolding.

Sources

  1. Google Search Central — Site moves with URL changes
  2. Google Search Central — HTTP status codes and Google Search
  3. Google Search Central — Debugging search traffic drops
  4. web.dev — Core Web Vitals
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project
Project

Stop thinking about it.
Start building.

Talk with us — free consultation, no commitments.