A website redesign is often the right decision when the existing site is slow, difficult to use, technically outdated or no longer supports the business. Problems usually appear when the project is treated as a visual redesign only.
To Google, the old and new website are not automatically the same thing. Changes to URLs, internal links, content, canonicals or indexation can also change organic visibility. A sound redesign should therefore include an SEO migration plan before development begins.
1. Save the baseline before the redesign
Before changing the first URL, record:
- which pages currently receive organic traffic,
- which pages have the most Search Console impressions,
- which URLs Google indexes,
- which pages have external links,
- which pages generate enquiries or sales,
- the current titles, descriptions, H1s and canonicals.
Where possible, crawl the full website and keep the report as a baseline.
The goal is not to copy everything from the old website. The goal is to avoid losing existing value simply because an important URL was forgotten.
2. Map old URLs to new URLs
Every important old URL needs a decision:
- keep it unchanged,
- map it to a new equivalent,
- merge it into another page,
- or intentionally retire it.
If a URL changes, the old address should generally receive a permanent 301 redirect to the most relevant replacement.
Do not redirect every removed page to the homepage. This often fails to preserve the original intent and does not help the visitor.
3. Do not remove useful content just to simplify the design
A common redesign mistake is replacing detailed service pages with a few large slogans and images. A cleaner design is not a reason to remove information that answers a real customer question.
If an existing page serves a useful search intent, preserve that purpose and its most important information. The text can be improved and reorganised, but the new page should still explain the service clearly.
4. Keep staging out of the index
The development version should not compete with the production website. Protect staging with authentication or appropriate noindex controls and make sure the staging domain does not appear in the production sitemap or canonical tags.
Before production launch, verify that temporary blocking rules have been removed from the real domain.
5. Check canonicals, hreflang and language versions
For multilingual sites, verify:
- self-referencing canonicals for each language,
- reciprocal hreflang links,
- correct language URLs,
- that English pages do not canonicalise to Slovenian pages or vice versa.
This is especially important when a redesign changes the routing structure.
6. Update internal links
A 301 redirect is a safety net, not a substitute for clean internal links.
Navigation, footer links, articles and calls to action should point directly to the new canonical URLs, not through redirects.
7. Submit the new sitemap and monitor after launch
After deployment:
- check the production
robots.txt, - check the sitemap,
- inspect key URLs in Search Console,
- monitor 404 and redirect errors,
- monitor indexation,
- compare organic landing pages before and after the migration.
A short-term movement in metrics is not automatically a problem. The priority is catching technical issues that prevent normal crawling or indexation.
8. Do not judge the redesign by appearance alone
A redesign should improve several things at once:
- usability,
- performance,
- mobile experience,
- clarity of the offer,
- technical SEO,
- conversion measurement.
If the website looks better but is harder to use or loses important organic pages, the project has not achieved its full purpose.
Tip: How we handled a redesign while keeping the rankings of a domain registered in 2014: ge-ko.si redesign case study. Service: website redesign.
Pre-launch checklist
- backup,
- crawl the old website,
- list important URLs,
- 301 mapping,
- title/meta/H1 review,
- canonicals,
- hreflang,
- robots,
- sitemap,
- internal links,
- structured data,
- analytics,
- Search Console,
- forms and conversions,
- mobile review,
- 404 testing.
Frequently asked questions
Does a redesign always mean losing Google rankings?
No. Losses mostly happen when URLs change without redirects, when useful content disappears or when the new site technically blocks indexing. With a list of important URLs, 301 redirects and post-launch checks the risk is manageable.
Can I redirect all old URLs to the homepage?
We advise against it. A homepage redirect does not preserve the intent of the old URL and does not help the visitor. Each important old address should point to the most relevant new page.
How long should I monitor Search Console after a redesign?
At least weekly for the first few weeks: indexing errors, 404s, redirects and a comparison of organic landing pages before and after the migration. Short-term fluctuations are not necessarily a problem; technical errors need fixing quickly.
Should old articles be kept in a redesign?
If they answer questions people still search for, yes — update and restructure them rather than deleting them without a redirect to related content.