Website redesign SEO checklist: protect rankings during a relaunch

In short:

There is no guarantee against ranking loss — temporary fluctuations are normal with any major rebuild.
You lower the risk with a complete URL inventory, precisely matched permanent redirects, and preserved content.
Protect staging with auth, verify canonical, hreflang, sitemap, robots, and noindex — then compare Search Console and analytics.

Why do relaunches so often cost rankings?

A redesign usually changes more than the look: URLs, navigation, headings, copy, loading times, and internal linking. To Google, the new website initially looks like a partly new project — rankings must be reassigned. That is exactly why Google advises planning changes step by step and expecting temporary fluctuations.

Avoidable risks include missing redirects, deleted important content, and accidentally indexed staging environments. Forgotten tracking also makes the outcome harder to assess. This checklist helps you avoid those mistakes. Also worth a look: business website costs, so migration and aftercare are budgeted from the start.

Before the relaunch: inventory and backup

Build a complete URL inventory: crawl with Screaming Frog or a similar tool, plus sitemap, server logs, and Search Console data (clicks, impressions, linked pages). Flag every URL with traffic, backlinks, or conversions.
Assess content instead of copying blindly: which pages drive enquiries, which rank for local searches or get cited by AI answers (GEO)? Keep strong pages in substance — trim only with care.
Keyword and content mapping: decide for each important old URL: does it stay, get merged, or get deliberately deleted (then 404/410 instead of a redirect)? Merged content receives exactly one new target URL.
Save benchmarks: export rankings, clicks, impressions, leads, loading times, and conversion rates before the rebuild — otherwise the comparison is missing later.
Clarify the platform question: anyone switching CMS should also review maintenance effort and legacy issues — for example with the WordPress drawbacks for business websites.

Redirects: 1:1 matches instead of bulk homepage redirects

Give every moved page a matching new target — via a permanent server-side redirect (301 or 308). Unchanged URLs do not need redirects. When content is removed without a replacement, a genuine 404 or 410 response is better than an irrelevant destination.
No bulk redirects to the homepage: pointing many old URLs at the homepage confuses users and may be treated by Google as a soft 404. Only genuine consolidations point to the new combined page.
Avoid redirect chains: redirect old URLs to their final destinations in one step wherever possible, and use the new URLs in internal links.
Carry over images, PDFs, and downloads: also move embedded files and documents when they carry traffic or links.
Keep them for at least a year: Google recommends keeping redirects active for as long as possible — at least one year — and switching your own plus important external links to the new URLs.

Secure staging properly and verify technology

Protect staging consistently: use HTTP authentication or access restrictions. An additional noindex directive can exclude indexing but does not replace access protection.
Lift the blocks deliberately at go-live: remove authentication, noindex, and test robots rules only from production pages intended to be public. Check robots.txt and keep any continuing staging environment protected.
Update canonical and hreflang: canonicals must point to preferred production URLs, not staging or old addresses. Language alternatives must reference one another correctly.
Sitemap and internal links: submit the new sitemap containing indexable canonical URLs and update internal links. During a URL migration, the old sitemap can temporarily remain available to help monitor the move.
Tracking and consent: test analytics, Search Console (verify all variants), conversion events, and the cookie banner before launch.

After launch: measure, test, follow up

Test crawls and redirects: Search Console URL inspection plus spot checks with curl or a crawler; fix 404 clusters immediately.
Classify ranking movements: fluctuations are normal in the first weeks — compare before/after via Search Console (clicks, impressions, indexed pages) and analytics (traffic, leads, calls).
Test contact forms and conversion paths: submit every form once end to end, verify auto-responders, CRM handover, and thank-you pages — relaunches silently lose revenue here.
Update external links and profiles: switch the most important backlinks, Google Business Profile, social profiles, and ad destinations to the new URLs.
Plan aftercare: review rankings, loading times, and error pages 30, 60, and 90 days after launch, add back missing content. Our team supports this as a website relaunch — request a non-binding first assessment via contact.

Frequently asked questions

Can a relaunch without ranking loss be guaranteed?

No, there is no guarantee — Google explicitly confirms that rankings can fluctuate temporarily with any major change. A full URL inventory, precisely matched permanent redirects, and clean monitoring significantly lower the risk.

How long must old redirects stay active?

At least one year, ideally permanently: Google recommends keeping redirects for as long as possible so signals transfer fully and external links keep arriving. Review redirects regularly and update important external links.

Which checks belong on the go-live checklist?

Check redirects, canonicals, hreflang, the sitemap, and robots.txt. Remove accidental noindex directives and access restrictions only from pages intended to be public; staging stays protected. Test contact forms end to end and check Search Console and analytics.

Sources (status / retrieved 22.10.2026)

Google Search Central: Move a site with URL changes — keep redirects for at least a year, plan for temporary ranking fluctuations and patient reindexing.
Google Search Central: Redirects and Google Search — permanent server-side redirects (301/308), no chains, no bulk redirects to irrelevant targets.