Site Redesign Without Losing Positions: A Step-by-Step Plan

A 60–70% traffic collapse after a redesign is not a rarity but the typical outcome when the project was run by a designer and a front-end developer alone. Recovery takes three to eight months. And almost all of those losses are prevented by a week of preparation.

Step 1. Take inventory before changing anything

Export the full list of URLs: from the sitemap, from the server logs, from Webmaster and from Metrica for the last 12 months. Mark separately the pages that bring traffic and leads — usually 15–20% of the total. Record current positions on 100–200 key queries and current speed metrics: without a baseline you will not know whether things got better or worse.

Step 2. The redirect map

• Every old URL either gets a new address or is marked as staying unchanged
• Only 301s, no 302s and no chains longer than one hop
• Bulk-redirecting all the old pages to the home page is the most expensive mistake of a redesign
• If a page is gone and there is nothing to replace it with, return 410 deliberately rather than by accident

Step 3. Migrate what earns the positions

Title, description, H1, texts, microdata, image alt attributes, breadcrumbs. Designers regularly "clean" a page of text for the sake of white space — and the rankings leave with the text. If the content really is overloaded, rewrite it while preserving the key meanings rather than deleting it. The result is easy to verify against the technical audit checklist.

Step 4. Checks on staging

The test version must be closed to indexing — by password or by IP, not only through robots.txt, because robots does not prevent a page from getting into the index via links. And most importantly: remove the block before you go live. A forgotten noindex in production is the number one cause of a site suddenly vanishing from search. How this works technically is explained in the MDN documentation on the robots meta tag.

Step 5. Launch and the first 72 hours

• Deploy on a weekday morning, not on a Friday evening
• Immediately check 30–40 old URLs from your traffic list — all of them should lead to relevant new pages
• Update the sitemap and submit it for recrawling
• Check that the Metrica counters and goals work on the new templates
• Take speed measurements: a new design is often heavier than the old one

Step 6. The first month of observation

A 10–20% dip in the first 2–4 weeks is a normal reaction to reindexing. A drop of 50% or deeper means an error you need to hunt down immediately: most often redirects, blocked indexing or lost content. Positions usually recover by week 4–8, after which growth begins thanks to improved behavioral signals and speed — the effect of which is described in the article on load speed.

When a redesign is genuinely needed

If the site is not responsive, runs on an unsupported CMS, or converts at half the market rate — then yes. If it has simply "gone stale", first work out what the same sum would deliver if it went into speed, the mobile version and content. We tell clients honestly when a rebuild will not pay for itself; examples of projects where it was justified are in the portfolio.

A redesign is first of all a data migration project and only second a design one. If you are planning an update, it is worth budgeting a week for preparation and putting someone responsible for search on the team: how we organize this is described in the web development section.