The Website Relaunch Checklist I Actually Use With Clients (20 Steps)

I've done enough website relaunches to know exactly how they go wrong. The client is excited, the new design looks great in Figma, everyone's ready to push the button. Then three weeks later, organic traffic is down 40% and nobody knows why.

It's almost always the same mistakes. No redirect map. No baseline data. Staging site leaked into Google's index. Someone changed the URL structure "to make it cleaner" without telling anyone.

Here's the checklist I actually use. Not a theoretical framework. The 20 things I check on every single relaunch because I've been burned by each one at least once.

Before You Touch Anything (Steps 1-7)

The prep work is where most relaunches are won or lost. Skip this and you're flying blind.

1. Export your baseline data

Before anything changes, document what you have. Pull your current organic traffic, top landing pages, conversion rates, and bounce rates from Google Analytics. Export your keyword rankings for your top 50-100 terms. Screenshot your Search Console performance dashboard.

You need this to measure whether the relaunch helped or hurt. Without it, you're guessing.

2. Crawl your existing site

Run a full site crawl with Screaming Frog or Sitebulb. Export every URL, meta title, meta description, canonical tag, and structured data markup. This becomes your source of truth for redirects and content migration.

3. Map your high-value URLs

Pull your backlink data from Ahrefs or SEMrush. Find every URL that has external links pointing to it. These are your priority pages. If these break during the relaunch, you lose the most link equity. Mark them separately.

4. Build your redirect map

This is the single most important document in any relaunch. Create a spreadsheet: old URL in column A, new URL in column B. Every single page.

Rules: use 301 redirects (permanent), never 302. Never redirect everything to the homepage. Each old URL maps to its closest equivalent. No redirect chains (A to B to C). Single hop only.

If you do nothing else on this list, do this one. I've seen relaunches lose 60% of traffic because of lazy redirects.

5. Run a content audit

Go through every page and decide: keep, update, merge, or kill. Content that hasn't had traffic in a year? Probably kill it. Two pages covering the same topic? Merge them. Outdated stats from 2022? Update before launch.

A relaunch is the perfect excuse to clean house. Don't migrate garbage to a new platform.

6. Audit your SEO elements

Check every meta title (under 60 characters, primary keyword first), meta description (under 160 characters, include a call-to-action), image alt text, and structured data. Migrate all of these to the new site. Losing meta titles during a platform change is one of the most common ranking drops I see. For a deeper dive, check our technical SEO guide.

7. Plan your internal linking

Draft your new site architecture before writing a single line of code. Limit primary navigation to 6-7 items. Map out which pages link to which. A good internal linking structure helps Google understand your site hierarchy and distributes link equity across your pages.

If your current internal linking is a mess, a relaunch is the time to fix it. Our competitor analysis guide covers how to see what your competitors do differently with their site structure.

Download the complete checklist: Grab all 20 steps as a printable PDF so you can check them off as you go. Download checklist (PDF)

The Build Phase (Steps 8-14)

Now you're building. Keep performance and SEO front of mind from day one, not as an afterthought.

8. Hit your Core Web Vitals targets

Google cares about three metrics:

• LCP (Largest Contentful Paint): under 2.5 seconds
• CLS (Cumulative Layout Shift): under 0.1
• INP (Interaction to Next Paint): under 200 milliseconds

INP replaced First Input Delay in 2024 and is now the key interactivity metric. In 2026, mobile Core Web Vitals scores carry more weight than desktop. Optimize accordingly.

Preload your LCP images. Use WebP or AVIF formats. Set explicit width and height on every image and video to prevent layout shifts. Use font-display: swap for custom fonts. Break long JavaScript tasks into chunks under 50ms.

For more on page speed impact, see our website optimization guide.

9. Build mobile-first

Not "responsive." Mobile-first. Design for the phone screen first, then scale up. Lazy-load offscreen images. Test on actual mobile devices, not just browser emulation. The gap between Chrome DevTools and a real phone on 4G is bigger than you think.

10. Preserve your structured data

If your current site has schema markup (product, FAQ, article, breadcrumb), make sure it migrates to the new site. Use JSON-LD format. Validate with Google's Rich Results Test before and after launch. Losing structured data means losing rich snippets in search results.

11. Lock down your staging environment

This one bites people constantly. Your staging site must be blocked from indexing via both robots.txt AND noindex meta tags. Belt and suspenders.

Verify that hreflang tags on staging don't point to staging URLs. Confirm no staging domain references leak into production configs. On launch day, audit your robots.txt and meta robots directives. I've seen an entire site disappear from Google because someone forgot to remove the noindex tag from staging.

12. Set up tracking before launch

Don't wait until after launch to configure analytics. Set up Google Analytics 4 with your key events (form submissions, button clicks, scroll depth). Verify Google Search Console ownership. Consider heatmaps (Hotjar or Microsoft Clarity) for the first month to see how users interact with the new design.

13. Design for accessibility

Target WCAG AA compliance. Verify keyboard navigation works on all interactive elements. Check color contrast ratios (4.5:1 for normal text). Run an automated scan with WAVE or Axe DevTools. This isn't just ethics. It's also reach. An accessible site serves more users and avoids potential legal issues.

14. Coordinate your content freeze

Decide on a date after which no content changes happen on the old site. If your team keeps publishing to the old CMS while you're migrating, you'll launch with stale content. Communicate the freeze date to everyone who touches the site.

Launch Day (Steps 15-17)

The actual switch. Keep it calm, keep it methodical.

15. Deploy and verify redirects

Push the new site live. Immediately test your redirect map. Spot-check at least 20-30 URLs manually. Use a tool to bulk-verify the rest. Every redirect should return a 301 status code and land on the correct destination.

16. Remove all staging blocks

Remove noindex tags. Update robots.txt to allow crawling. Double-check that your XML sitemap is generating correctly and points to the new URLs. Submit the sitemap to Google Search Console.

17. Run a post-launch crawl

Crawl the new site immediately. Compare against your pre-launch crawl from Step 2. Look for: missing pages, broken links, missing meta titles, missing structured data, unexpected redirects, pages returning 404 or 500 errors.

Fix anything critical on day one. It makes a difference.

The First 30 Days After (Steps 18-20)

The relaunch isn't done when the site goes live. This is where the real work starts.

18. Monitor daily for the first two weeks

Check every day: traffic levels, 404 errors in Search Console, form submissions still working, page speed scores. Compare against your baseline from Step 1. Some fluctuation is normal. A 30%+ drop that doesn't recover after a week means something is wrong.

Pay special attention to your high-value URLs from Step 3. If those pages lost rankings, investigate immediately.

19. Expect a recovery timeline

SEO recovery after a relaunch typically takes 2 weeks to 3 months. Sites that follow a structured checklist (like this one) recover faster. Sites that wing it can take 6+ months or never fully recover.

Don't panic at initial dips. Do panic if you see no recovery after 30 days.

20. Iterate based on real data

After 30 days, you'll have enough data to see what's working and what isn't. Which new pages are performing? Where are users dropping off? Are your bounce rates better or worse than before?

Use this data to make targeted improvements. A relaunch is a starting point, not a finish line.

The Mistakes That Actually Cost Rankings

After doing this enough times, the same mistakes keep showing up:

Mistake	What Happens	Fix
302 redirects instead of 301	Link equity doesn't transfer	Always use 301 for permanent moves
Everything redirects to homepage	Page-level rankings destroyed	Map each old URL to its closest match
Redirect chains (A to B to C)	Link equity diluted, slow crawling	Single-hop redirects only
Lost meta titles/descriptions	Rankings drop for those pages	Verify priority pages manually
Staging noindex on production	Entire site gets deindexed	Audit meta robots on launch day
No baseline data	Can't diagnose problems	Export everything before you start
Lost structured data	Rich snippets disappear	Validate with Rich Results Test
Content freeze gap	Launches with stale content	Coordinate editorial freeze

Every single one of these has happened to a client of mine or someone I know. They're all preventable.

Use This Checklist

I've been through enough relaunches to know that the difference between a smooth one and a disaster is almost always preparation. The technical execution is the easy part. The boring spreadsheet work beforehand is what saves you.

If you're planning a relaunch and want someone to make sure nothing falls through the cracks, or if you're mid-relaunch and things are already going sideways, reach out. I've seen most of the ways this can go wrong, which means I also know how to keep it on track.

For a broader look at improving your Google rankings beyond just the relaunch, we've got that covered too.