Most website redesigns fail not because the design was bad, but because the launch was rushed. We've audited dozens of sites where businesses lost 40–60% of their organic traffic within weeks of going live — not because of algorithm changes, but because of preventable technical errors made during the migration. A solid website redesign checklist pre-launch is the difference between a successful launch and a very expensive cleanup job.
This post covers 20 specific things to audit, test, and confirm before your redesigned site goes live. Whether you're doing this in-house or working with an agency, use this as your final gate before flipping the switch.
Why Pre-Launch Discipline Matters More Than the Design Itself
The design is the exciting part. The pre-launch checklist is the part nobody wants to do — and that's precisely why so many relaunches cause problems. A visually polished site that bleeds organic rankings, breaks on mobile, or loads in 6 seconds is worse than the old site it replaced.
At Workflow AI Advisors, every website project follows a structured pre-launch protocol before a single DNS record changes. The cost of fixing issues post-launch — in traffic loss, dev time, and client trust — is always higher than catching them before.
The Complete Website Redesign Pre-Launch Checklist
1. Crawl Your Old Site Before You Touch Anything
Before migrating or launching anything, run a full crawl of your existing site using Screaming Frog or Sitebulb. Export every indexed URL, title tag, meta description, H1, and inbound link. This is your baseline. Without it, you're migrating blind.
2. Map Every URL to Its New Destination
If any URLs are changing — and in most redesigns, they do — you need a complete redirect map before launch. Every old URL must point to the most relevant new URL via a 301 redirect. Missing redirects are the single biggest cause of post-relaunch traffic loss.
3. Implement and Test All 301 Redirects
Building the redirect map isn't enough. You need to test every redirect on the staging environment. Use Screaming Frog's "Redirect Chains" report or a tool like Redirect Path to confirm each one resolves correctly, without chains or loops. A redirect chain (old URL → intermediate URL → new URL) passes less link equity and slows page load.
4. Preserve Title Tags and Meta Descriptions for Key Pages
Every page that currently ranks for a keyword needs its title tag and meta description either preserved or deliberately improved. Redesigns frequently wipe metadata because it lives in a CMS field that doesn't carry over automatically. Audit your top 20 organic pages and confirm the metadata is intact on staging.
5. Audit Internal Linking Structure
Your old site's internal links carry contextual authority. When URLs change, internal links pointing to old paths create soft 404s or redirect hops. Go through your new site's key pages and ensure all internal links point directly to their final URL destination — no redirects, no dead ends.
6. Verify Your XML Sitemap is Accurate and Submitted
Your new sitemap should include every page you want Google to index and nothing else. No staging URLs, no noindexed pages, no redirect destinations that shouldn't be there. Generate the sitemap fresh from your new CMS, review it manually, and have it ready to submit to Google Search Console the moment the new site goes live.
7. Check Robots.txt Is Not Blocking Search Engines
This one sounds obvious. It isn't. During development, most sites have a Disallow: / line in robots.txt to block crawlers from indexing the staging environment. That line must be removed before launch. We've seen this left in place on live sites — the result is complete deindexation within days.
8. Confirm Canonical Tags Are Correct
Every page should have a self-referencing canonical tag pointing to its correct live URL. If your staging domain has leaked into any canonical tags, you'll be telling Google the authoritative version of your content lives on a password-protected dev environment. Check this across your most important templates: homepage, service pages, blog posts, product pages.
9. Run Core Web Vitals on Staging
Performance is a ranking signal and a conversion factor. Use Google PageSpeed Insights and Chrome's CrUX data to benchmark LCP, CLS, and INP on your new site before launch. If your LCP is above 4 seconds, resolve it before you go live — not after. Common culprits: uncompressed hero images, render-blocking scripts, third-party tag overload.
10. Test on Real Devices, Not Just Browser Emulators
Browser DevTools mobile simulation is useful but not sufficient. Test your new site on at least three real physical devices across iOS and Android, covering different screen sizes and browsers. Navigation behaviour, tap target sizes, font rendering, and form usability frequently break on real devices in ways emulators miss.
11. Audit All Forms and Conversion Paths
Every lead form, booking widget, checkout flow, and CTA button needs to be tested end-to-end on the staging environment. Submit test entries and confirm they route to the correct email, CRM, or automation trigger. A redesign that breaks your lead capture is a redesign that costs you money from day one.
12. Set Up Google Analytics 4 and Verify Data Is Flowing
Confirm your GA4 tag is firing on every page — not just the homepage — and that events like form submissions, clicks, and scroll depth are tracking correctly. If you're migrating from Universal Analytics, this is also the time to configure GA4 conversions properly. Don't go live with unverified tracking.
13. Migrate and Test Google Tag Manager
If your previous site used GTM, export the container and verify all tags, triggers, and variables are functioning on the new site. Pixel fires for paid media — Meta, Google Ads, LinkedIn — need particular attention. A broken conversion pixel on your new site will immediately degrade your paid media performance as smart bidding algorithms lose conversion signal.
14. Check All Third-Party Integrations
CRM integrations, live chat widgets, booking systems, payment gateways, email marketing sign-ups — list every third-party tool connected to your current site and verify each one is connected and functional on the new site. These integrations frequently break during CMS migrations and rarely make it onto anyone's launch checklist.
15. Test Site Search (If Applicable)
If your site has an internal search function, test it. Run searches for your core products, services, and content topics and confirm results are relevant and rendering correctly. Broken site search frustrates users and inflates bounce rates — particularly damaging for e-commerce and content-heavy sites.
16. Confirm SSL Certificate Is Installed and Active
HTTPS is non-negotiable. Confirm your SSL certificate is valid, covers all subdomains you're using, and that your site is not serving any mixed content (HTTP assets loaded on an HTTPS page). Mixed content warnings damage user trust and can cause browsers to block certain page elements.
17. Set Up 404 Monitoring and a Custom 404 Page
No redirect map is perfect. Create a custom 404 page that keeps users on your site, points them to useful navigation, and ideally captures the broken URL in your analytics so you can fix it quickly. Set up Google Search Console alerts for 404 errors — they'll surface within days of launch.
18. Back Up the Old Site
Before anything goes live, take a full backup of the old site — files, database, and all. Store it somewhere accessible. If a critical issue emerges post-launch and you need to roll back, a backup gives you that option. This is basic but frequently skipped when launch deadlines are tight.
19. Do a Final Staging-to-Live Comparison
Immediately after launch, compare key pages between your staging environment and the live site. Check that fonts, images, spacing, and content match exactly. CMS deployment processes occasionally strip assets or misconfigure environments. Catch these visually within the first hour.
20. Submit Sitemap and Request Indexing in Google Search Console
Once live, submit your XML sitemap in Google Search Console and use the URL Inspection tool to request indexing on your most important pages. Don't wait for Google to discover your new site organically — prompt it. Monitor the Coverage report daily for the first two weeks to catch any crawl or indexing issues quickly.
The Broader Picture: Redesigns and SEO Are Inseparable
A website redesign is not a separate workstream from SEO and GEO strategy — it's one of the highest-risk events in your organic visibility calendar. Every structural change you make to URLs, content architecture, or technical infrastructure has direct implications for how search engines understand and rank your site.
The businesses that come to us post-relaunch having lost 50% of their traffic all share the same story: the redesign was treated as a brand and UX project, not a technical SEO event. The agencies that built their sites either weren't thinking about search at all, or assumed the CMS would "handle it."
It never does.
At Workflow AI Advisors, we build pre-launch SEO audits into every web project from the start — not as an afterthought. The result is launches that preserve or improve organic rankings from day one, rather than spending months recovering lost ground.
A Note on Timing
Don't launch on a Friday. Don't launch the day before a bank holiday. Don't launch during your busiest trading period. Launch when your technical team has full capacity to monitor and respond to issues in real time. The first 24–48 hours after a redesign go-live are the highest-risk window — be available for them.
Frequently Asked Questions About Website Redesign Pre-Launch Checklists
The most common and costly mistake is failing to implement 301 redirects for changed URLs. When URLs change without redirects, every inbound link and indexed page that points to the old URL becomes a dead end — resulting in lost link equity and significant drops in organic search rankings. This is closely followed by forgetting to remove the robots.txt disallow rule from the staging environment, which can cause full deindexation of the new site.
The pre-launch checklist should begin at least two to four weeks before your target launch date for a small to mid-size site, and four to eight weeks for larger or more complex sites. This gives enough time to crawl the old site, build redirect maps, test redirects on staging, verify tracking, and fix performance issues without rushing. Starting the checklist the week of launch is too late to address anything meaningful.
Not necessarily. A well-managed redesign that preserves URL structure, maintains or improves metadata, implements correct redirects, and improves Core Web Vitals can maintain or even grow organic visibility from day one. Traffic drops after redesigns are common but not inevitable — they're almost always the result of skipped technical steps, not an unavoidable consequence of the redesign itself.
If your domain name stays the same, your existing Search Console property remains valid and you don't need to re-verify. However, if you're moving from HTTP to HTTPS, or from a subdomain to a root domain (or vice versa), you will need to add and verify new properties for those variants. You should also submit your new XML sitemap fresh and use the URL Inspection tool to prompt recrawling of key pages after launch.
Carry over your Google Tag Manager container to the new site first and test all conversion tags — Google Ads, Meta Pixel, LinkedIn Insight Tag — on staging before going live. Verify that the conversion events tied to smart bidding strategies (Target CPA, Target ROAS) are firing correctly post-launch. Even a 48-hour gap in conversion data can destabilise automated bidding algorithms, leading to inflated CPAs while the system recalibrates. This is a critical step that many redesigns overlook entirely.
Workflow AI Advisors engineers AI automation, paid media, SEO/GEO, and web infrastructure for global businesses. Based in London and New Delhi, we serve clients across the US, UK, Australia, Singapore, UAE, and Canada.
BOOK A FREE AUDIT