Here is a statistic we cannot prove but would bet on: website redesigns destroy more small business rankings than Google updates do. A site ranks for years, the owner launches a beautiful new version, and traffic falls off a cliff, because the redesign silently deleted the pages, URLs, and signals the rankings were attached to. Every one of those losses is preventable. This is the checklist.
Why redesigns break rankings
Your rankings are not attached to your business; they are attached to specific URLs with specific content and a history of links pointing at them. A redesign typically changes URLs, rewrites or removes content, and re-platforms the site, any of which can orphan those signals. Google then has to re-evaluate what is effectively a new site, and it does not always reach the same conclusion.
Before the redesign: inventory what you have to lose
- Crawl the current site and export every URL. This list is your insurance policy.
- Record what performs. From analytics and Search Console, list your top pages by traffic, your ranking keywords per page, and the pages other sites link to. These pages are load-bearing; mark them.
- Benchmark everything. Screenshot rankings, note monthly organic traffic, run a speed test. Without a baseline you cannot prove (or notice) what the redesign changed.
- Decide URL fate page by page. Keep the URL (best), change it (needs a redirect), or retire the page (needs a deliberate decision, not an accident). If a URL can stay the same, let it. Every changed URL spends a little trust.
During the build
- Build the redirect map first, not last. Every old URL that changes gets a 301 redirect to its closest new equivalent. One to one, not everything to the homepage; bulk homepage redirects throw away page-level rankings.
- Preserve the content that ranks. Designers cut copy for aesthetics; that copy is often why the page ranks. Rewrite for clarity if needed, but keep the substance, the headings, and the questions it answers.
- Keep titles and metas. Carry over your title tags and meta descriptions, or improve them deliberately using our on-page checklist. Letting a new CMS regenerate them all as "Home | Sitename" is a classic silent loss.
- Block search engines from the staging site. Password-protect it or noindex it. Staging sites that get indexed create duplicate-content confusion at exactly the wrong moment.
- Watch the weight. New designs love big images and animation libraries. Test speed on the staging site before launch, not after; going backwards on Core Web Vitals undermines the whole exercise.
- Rebuild internal links deliberately. New navigation and new pages mean the internal link structure changes. Make sure money pages keep their prominence.
Launch day
- Deploy redirects with the site, in the same release. A gap of days between launch and redirects is a gap Google notices.
- Remove the noindex. The most infamous redesign mistake: shipping the staging block to production. Check the homepage source and robots.txt within the hour.
- Submit the new sitemap in Search Console.
- Click through the top pages list yourself. Every load-bearing page from your inventory should resolve, on the right URL or through one clean redirect.
The month after
- Watch Search Console weekly: coverage errors, spiking 404s, and the performance report against your benchmark.
- Crawl the new site for broken links and redirect chains.
- Expect some turbulence, but bounded. A dip of a few weeks while Google re-crawls is normal on large changes. A drop that deepens past a month means something specific broke; go find it in the checklist above rather than waiting it out.
Changing platforms too? Extra care required
A redesign that also moves platforms (to or from WordPress, Shopify, Wix, a custom build) multiplies the risk, because URL patterns, templates, and technical behavior all change at once. Three platform-specific notes from painful experience:
- URL structures rarely match between platforms. Shopify forces /pages/ and /blogs/ prefixes; WordPress permalinks are configurable; site builders generate their own patterns. Map this before choosing a launch date, because it decides the size of your redirect job.
- Check what the new platform does to titles and schema. Some builders inject their own title formats or strip custom markup. Verify on staging with a crawl, not by assumption.
- Watch template weight. Theme marketplaces optimize for demo prettiness, not speed. Test your shortlisted theme's demo through PageSpeed before committing; retrofitting speed into a heavy theme costs more than choosing a light one.
None of this argues against migrating; platforms genuinely outgrow businesses. It argues for treating a platform move as an SEO project with a design component, not a design project with an SEO afterthought.
If the damage is already done
Redesigned six months ago and never recovered? The fix is forensic rather than magic: rebuild the old URL list from analytics history and archived crawls, find what got no redirect, check what content and titles were lost, and restore or redirect deliberately. This is one of the most common jobs inside our technical SEO service, and recovery is usually possible, because the history that made you rank is recoverable evidence.
Planning a redesign now? Send us the current site for a free audit first. Knowing exactly what your rankings depend on before you rebuild is the cheapest insurance available.