A redesign is a good moment to fix design, speed and structure. It is also the moment when many websites lose a large part of their Google traffic, sometimes for months. The reason is rarely the design itself. It is changed URLs without redirects, removed content that used to rank, lost titles and descriptions, or a staging setting left switched on. Here is the process we follow to keep rankings through a redesign.
1. Make a full URL inventory
Before anything changes, list every URL the current site has. Combine three sources: a crawl of the site, the pages report in Google Search Console and the landing pages in Google Analytics. Add URLs of images and PDFs that get traffic or links. For each URL, record organic clicks, main queries and whether other sites link to it. This list tells you which pages carry your rankings and must be protected, and which can be merged or removed.
2. Build a 301 redirect map
Every old URL that changes needs a permanent 301 redirect to the most relevant new page. Not to the home page, which Google may treat like a missing page, but to the page that answers the same question. Keep it as a simple two-column table: old URL, new URL. Rules to follow:
- Redirect one to one wherever possible, and merged pages to the page that absorbed their content.
- Avoid redirect chains (A to B to C). Point old URLs straight to the final address.
- Cover variants: with and without trailing slash, www and non-www, http and https, old language prefixes.
- Pages that are truly gone with no replacement can return 404 or 410, but only when nothing useful exists.
If URLs can stay the same, keep them. The safest redirect is the one you do not need.
3. Keep the content that ranks
A new design often comes with shorter, "cleaner" texts. If a page ranks for a query, the content answering that query has to survive the redesign. Shorten what does not help, but keep the headings, sections and answers that match what people search for. When merging two pages, move the useful parts of both. The same applies to internal links: pages that were well linked in the old navigation should stay well linked.
4. Carry over the metadata
Titles and meta descriptions, H1 headings, image alt texts, canonical tags and structured data (schema markup) are easy to lose when templates are rebuilt. Export them from the old site and transfer them, improving where needed but without losing the keywords that brought traffic. Check that every page has a unique title and that canonical tags point to the new URLs, not to the staging domain.
5. Hreflang for multilingual sites
In the Baltics, most business sites run in two to four languages. If language versions move, for example from a subdomain to a folder, every hreflang tag must point to the new URLs, each version must reference all others and itself, and the redirect map must cover every language. A mistake here can make Google show the Russian page to Estonian searchers or drop one language version altogether.
6. Prepare Search Console and launch
- Make sure the staging site was blocked from indexing, and that the block (noindex, password or robots.txt rule) is removed at launch.
- Upload a fresh XML sitemap with the new URLs and submit it in Search Console.
- If the domain changes, use the change of address tool in Search Console.
- Keep GA4 and conversion tracking working from the first minute, so you can compare before and after.
7. Speed and Core Web Vitals
A redesign should make the site faster, not slower. Heavy animations, large images and many scripts often arrive with a new design. Test the main templates on a phone before launch and fix what slows them down. A faster site helps both rankings and conversions.
Post-launch monitoring checklist
| When | Check |
|---|---|
| Launch day | Indexing allowed, sitemap submitted, redirects from the map tested in bulk, no redirect chains, analytics and conversions firing |
| First week | Search Console coverage and 404 reports, new URLs being indexed, top pages return 200, hreflang errors |
| Weeks 2-4 | Clicks and positions for top queries compared with before, pages that lost traffic reviewed one by one |
| Months 1-3 | Trend back to or above previous level, backlinks pointing to old URLs still redirect, Core Web Vitals in the green |
| Ongoing | Keep redirects in place long term, do not delete the redirect map |
Some movement in positions for a few weeks after a large change is normal while Google processes the new site. A steady drop on specific pages is not normal and usually points to a missing redirect, lost content or a technical block.
How we handle redesigns
At BoostLab, migration is part of the project scope, not an extra: URL inventory, redirect map, content and metadata transfer, hreflang, sitemap and Search Console checks after launch. A business website starts at €1,700 and takes 2-3 weeks, and every site comes with SEO structure, schema markup, GA4 and conversion tracking. See web development, pricing and our SEO checklist before launch.
