A redesign should not reset your search visibility. This checklist covers redirects, tracking, schema, speed and content parity before and after launch.
Website relaunch checklist in short
A website relaunch keeps its rankings when every old URL that earns traffic either survives unchanged or redirects to its closest new equivalent, when the content search engines already rely on is carried across, and when tracking works from the first hour. Everything else on a relaunch checklist serves those three goals.
Rankings fall after a relaunch for ordinary reasons rather than mysterious ones: URLs change without redirects, copy is thinned out to look cleaner, a staging noindex tag goes live, or analytics silently stops. According to Google's documentation, moving content to new URLs calls for permanent server-side redirects, so the old address passes its signals to the new one. A redesign is a visual decision. A relaunch is an infrastructure decision, and it deserves the same care.
Before you build: inventory and baseline
Start with a spreadsheet of every URL on the current site. Export it from your CMS or a crawler, then add three columns from Google Search Console and analytics: clicks over the last twelve months, the pages that earn backlinks, and the pages that produce enquiries. This list decides what you must protect.
Then record a baseline. Save your top queries, average positions, organic sessions and conversion counts, plus a Core Web Vitals snapshot. Without a before, you cannot prove an after, and you cannot tell a normal post-launch wobble from a real loss. For a multilingual site, repeat the inventory for every language version, because each one is a separate set of URLs to protect.
Redirects, content parity, tracking and schema
Build a redirect map from the inventory: each old URL on the left, its closest new equivalent on the right, using 301 permanent redirects. Send a page to a genuinely related page rather than the homepage, because a mass redirect to the homepage is often treated as a soft 404. If you keep a URL the same, you need no redirect, and that is the best outcome.
Content parity means the new page says at least what the old page said. Keep the headings, body copy, internal links, image alt text and FAQs that already earn visibility. Shorter, prettier pages often lose the long-tail queries the old copy quietly won. Reuse your title tags and meta descriptions unless you are deliberately improving them.
Then check the machinery. Confirm that the analytics tag, conversion events and Search Console verification are on the new build. Carry over structured data such as Organization, Article and FAQPage markup, and make sure canonical tags and hreflang annotations point at the new addresses. Finally, test speed on a real phone connection, because heavy sliders and unoptimised images are the usual price of a beautiful redesign.
A practical website relaunch checklist for launch day and the first 30 days
Run the work in three passes: on staging, at launch and afterwards. The aim is to catch each class of error while it is still cheap to fix.
On staging, crawl the new site and compare it with the inventory. Every old URL should return a 200 or a single 301 hop, with no redirect chains and no 404s. Confirm that the site is blocked from indexing while it is on staging, and write down the exact step that removes that block at launch, because a leftover noindex tag or robots.txt disallow is the most expensive single mistake a relaunch can make.
On launch day, remove the block, switch the redirects on, submit the new sitemap in Search Console and open the key pages on a phone. Check that a test enquiry reaches your inbox or CRM and that analytics shows a live visit. If the domain itself changes, the Change of Address tool in Search Console exists for exactly that situation.
In the first 30 days, watch Search Console daily for the first week: crawl errors, newly excluded pages and the indexing report. Compare clicks and positions with your baseline. Some movement is normal while search engines reprocess the site, but a sharp drop on a page you meant to protect points to a missing redirect or a dropped block of content. Fix those first, then improve.
The five-point relaunch framework
- Protect: list every URL that earns traffic, links or enquiries, and decide for each one whether it stays, moves or is retired on purpose rather than by accident.
- Map: write the one-to-one redirect map before the design is signed off, so the new structure is shaped by what you must preserve instead of discovering it afterwards.
- Match: carry across headings, copy, internal links, alt text and structured data, and only improve them once the baseline is secured and you can measure the effect.
- Measure: confirm tracking, conversions and Search Console on the new build before the old one goes offline, and keep your baseline numbers beside the results.
- Monitor: review crawl errors, indexing and rankings daily for a week and weekly for a month, with one named person responsible for fixing whatever appears.
Website relaunch checklist: common questions
- Will a redesign hurt my SEO? — Not if URLs, content and tracking are carried across properly. Rankings usually fall because of avoidable technical errors such as missing redirects or a leftover noindex tag, not because the design is new.
- How long do rankings take to recover after a relaunch? — It varies with the size of the site and how well the move was handled. Search engines need time to recrawl and reprocess pages, so expect some fluctuation, and treat a sustained drop beyond that as a technical fault to investigate.
- Should I use 301 or 302 redirects for a relaunch? — Use 301 for a permanent move, as Google's documentation recommends. A 302 signals a temporary change and can leave the old URL in the index.
- Do I need to redirect pages I am deleting? — Redirect them to the closest relevant page if one exists. If nothing is relevant, let them return a 404 or 410 rather than redirecting everything to the homepage.
Keep reading
Build something
worth trusting.
Tell us what's slowing your business down. We'll show you the system that fixes it — and how fast.