I have been called in to fix three redesigns that lost most of their organic traffic overnight. In all three cases the new site was better looking, faster and more modern, and in all three cases nobody had mapped the old URLs to the new ones.
A redesign is a migration whether you call it one or not. This is the checklist I work through, in order, from four weeks before launch to four weeks after.
Quick Info
Biggest risk
Old URLs returning 404 instead of redirecting
Second biggest
Content removed because it looked untidy
When to benchmark
Four weeks before launch, minimum
Typical recovery time if it goes wrong
Two to six months, sometimes never fully
Launch day essential
The redirect map, tested
What to watch after
Crawl errors, impressions, and top-page rankings
Four weeks out: benchmark everything
You cannot tell whether a redesign hurt you if you did not record what you had. Export and save all of this before anything changes.
01A full list of your existing URLs, from a crawl and from your sitemap.
02Your top 100 pages by organic traffic and by impressions.
03Your top 200 queries with their positions and click-through rates.
04Your backlink profile, so you know which pages have earned links.
05Current Core Web Vitals figures.
06Screenshots of your key pages, because you will forget what was on them.
Save it somewhere outside the site. I have seen a benchmark exported to a folder on the old server and lost with it.
Three weeks out: decide the URL structure
The safest redesign keeps every URL exactly as it is. If you can do that, most of the risk on this list disappears.
If URLs must change, and sometimes they must, then every single old URL needs a decision: does it map to a new equivalent, or does it go? Build a spreadsheet with two columns, old and new, and do not leave a blank.
—Map like to like. A service page goes to the equivalent service page, not to the homepage.
—Never redirect everything to the homepage. Search engines treat that as a soft 404 and you lose the value entirely.
—Where a page is being merged into another, redirect it to the merged page and make sure the content actually arrived there.
—Keep the URL for anything with backlinks unless you have no choice.
A redirect to the homepage is a polite way of throwing away a page's history.
Two weeks out: content parity
The second most common cause of traffic loss is content quietly disappearing because the new design had no place for it.
01Compare the old and new page by page. Is every substantive section still present somewhere?
02Check the word count on your top twenty pages. A page that went from 1,400 words to 300 will drop.
03Confirm every H1 and H2 survived, or changed deliberately rather than by accident.
04Check the internal links. New designs often lose the contextual links inside body copy.
05Confirm image alt text carried across. Rebuilt galleries usually lose it.
06Confirm structured data is present on the new templates.
Designers reasonably want cleaner pages. The compromise is to keep the content and improve its arrangement rather than deleting it, because those paragraphs are why the page ranks.
One week out: check the staging site properly
—Confirm staging is blocked from indexing, and confirm the block will be removed at launch. Both halves of that go wrong.
—Titles and meta descriptions present on every page, not the theme defaults.
—Canonical tags pointing at the live domain, not staging.
—Forms tested end to end, with the notification arriving at a mailbox somebody reads.
—Analytics and conversion tracking installed on the new templates.
—404 page exists and offers a route back into the site.
—Speed tested on the staging build, on mobile.
The staging noindex tag left in place after launch is the single most common self-inflicted disaster in this business, and it takes four weeks of confusion to notice.
Launch day, in order
01Take a full backup of the old site, files and database, and keep it for six months.
02Deploy the new site.
03Implement the redirects. All of them, from the map, as permanent 301s.
04Remove the staging noindex and confirm robots.txt allows crawling.
05Submit the new sitemap in Search Console.
06Crawl the live site immediately and check for 404s, redirect chains and broken internal links.
07Test the top twenty old URLs by hand. Not a sample: those twenty specifically.
08Confirm analytics is recording.
Launch on a Tuesday morning, not a Friday afternoon. The problems appear in the first six hours and you want to be at a desk.
Week one after launch
—Check Search Console coverage daily for new crawl errors and a spike in 404s.
—Watch impressions rather than sessions. A dip of 10% to 20% for a fortnight is normal; a fall of 60% is a redirect problem.
—Fix redirect chains, where A points to B which points to C. Collapse them to point straight at C.
—Re-test forms. They break in ways staging does not reveal.
—Ask two customers to complete a real task on the new site.
Weeks two to six
Rankings wobble after a migration while search engines re-crawl and re-evaluate. Give it time before making changes, but watch for the patterns that mean something is genuinely wrong.
—A specific page that lost its position while the rest held: check its content parity and its redirect.
—Site-wide impression loss that keeps falling after three weeks: check indexing, canonicals and robots.txt.
—Traffic steady but enquiries down: the site is fine and the conversion path is worse. Compare the old and new call to action placement.
—Everything recovering by week six: normal. Stop worrying.
Expect a dip. Do not accept a cliff.
The redesigns that go badly wrong
For completeness, the five causes I have actually seen, in order of frequency.
01No redirect map. Old URLs 404, link equity lost, rankings gone.
02Staging noindex left live, so the new site was never indexed.
03Content halved for design reasons, so the pages no longer answered the queries they ranked for.
04Everything redirected to the homepage, treated as a soft 404 and discarded.
05Domain changed at the same time as the redesign, which doubles the risk. Do one or the other.
None of these are subtle and all of them are preventable by a spreadsheet and an afternoon of checking.
Frequently Asked Questions
Will I lose rankings when I redesign?
A short dip of one to three weeks is normal while search engines re-crawl. A sustained loss means something on this list was missed, most often the redirects.
Do I need to redirect every old URL?
Every URL that had traffic, links or is likely to be linked from elsewhere. Genuinely orphaned pages with no history can be allowed to 404.
Can I keep the same URLs?
Usually yes, and it is the single best decision available. Keep them unless the existing structure is actively harmful.
How long should redirects stay in place?
Permanently, or at minimum a year. Search engines eventually consolidate the signals, but old links and bookmarks persist far longer.
Should I change domain and redesign at the same time?
No. Do one, wait until it has settled, then do the other. Combining them makes diagnosing any problem much harder.
What if I have already launched and lost traffic?
Crawl the old sitemap against the live site to find 404s, check whether the noindex tag is still present, and compare content on the pages that fell. Those three checks find most cases.
Before You Go
A redesign is a technical project wearing a creative brief. The design work is the visible half; the URL map, content parity and redirect testing are what decide whether the new site keeps what the old one earned.
Do the benchmark before you approve a single mockup. If you want the platform question settled first, the comparison is here, and the technical audit checklist covers the post-launch crawl in more detail.
Map the URLs first. Everything else is design.
WRITTEN BY TARIQ SALLAM
Marketing Consultant. Entrepreneur. Content Creator.
I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.
More About Tariq →
Keep reading