A website redesign changes URLs, page structure, content and often the platform, and every one of those changes can cost rankings if it is not planned. The pattern is familiar: the new site launches, everyone is happy with the design, and three weeks later organic traffic is down 40%. Almost always, the cause is avoidable.
Step 1: Know what you have before you change it
Before any design work starts, we crawl the existing site and export from Google Search Console and analytics:
- Every URL, its indexation status and its inbound links
- Which pages bring traffic, conversions and rankings, and for which queries
- Existing redirects, canonical tags and structured data
- Page speed and Core Web Vitals per template
This gives us a list of pages that must survive, pages that can be merged, and pages that can go. Deleting a page that has 20 quality backlinks is a mistake we see far too often.
Step 2: Map every old URL to a new one
The redirect map is the core document of a safe redesign. Every old URL that has traffic, links or rankings gets a 301 redirect to the most relevant new URL. Not to the homepage: to the page that actually replaces it. Where possible, we keep URLs identical, which removes the risk entirely for those pages.
Step 3: Keep what works in the content
Designers often want a clean slate. Search engines reward continuity. If a page ranks because of a specific heading, paragraph or FAQ, that content moves to the new design, improved but not rewritten from scratch. New content is added where the intent mapping shows gaps.
Step 4: Build the new site on a staging environment that is not indexed
The staging site is blocked with noindex and, where the platform allows, password protection. This prevents Google from indexing duplicate content during the build. Before launch, we run a full technical check on staging: titles, headings, internal links, schema, image alt text, mobile rendering and speed.
Step 5: Launch with a checklist, not a hope
- Remove noindex and password protection
- Activate the redirect map and test a sample of old URLs
- Submit the new XML sitemap in Search Console
- Verify robots.txt, canonicals and hreflang for multilingual sites
- Check that analytics, tag manager and conversion tracking fire correctly
- Update the Google Business Profile and other listings if the URL structure changed
Step 6: Monitor for six weeks
Rankings fluctuate after a launch even when everything is done right. We watch Search Console daily for the first two weeks: crawl errors, 404s, coverage changes and ranking movement on the key pages. Small issues fixed in the first days do not become large ones.
What "usually grow" looks like
When the redesign also fixes structural problems, meaning proper service pages, faster templates, better internal linking and structured data, most sites we relaunch are above their previous organic traffic within three months. The redesign becomes an SEO project with a nicer front end, which is exactly what it should be.
Frequently asked questions
Typically two to six weeks for the bulk of the movement, with smaller adjustments for up to three months. A well-executed migration shows little or no dip.


