Website Redesign Checklist: Relaunch Without Losing Traffic

A new website should make more money than the old one. Yet many relaunches start with a traffic dip that takes months to recover from, and the cause is rarely the design itself. It is usually a handful of technical details nobody owned: URLs that changed without redirects, pages quietly dropped, or a staging setting that told Google to ignore the whole site.

This checklist is organised by phase, from the first audit to the weeks after launch. Each phase has a short list you can hand to whoever owns that part of the project, whether that is your marketing lead, your developer or your agency.

Why Do Websites Lose Traffic After a Redesign?

Traffic drops after a redesign because search engines lose track of pages they had already ranked. When a URL changes without a permanent redirect, Google treats the new page as unknown and the old one as gone, so the rankings and links it had earned do not carry over automatically.

The usual culprits are predictable:

• Changed URLs with no redirect, or redirects that all point to the homepage.
• Deleted or merged content that was quietly ranking for long-tail searches.
• Lost on-page signals: rewritten title tags, removed headings, thinner copy, missing structured data.
• Broken internal linking, where important pages fall out of the navigation and become harder to crawl.
• Staging settings leaking to production, such as a sitewide noindex tag or a Disallow: / rule in robots.txt.
• Slower or less usable mobile pages. Google uses the mobile version of a site for indexing and ranking, so content hidden or removed on mobile effectively disappears.

Every item on that list is preventable. The rest of this checklist exists to prevent them.

Phase 1: What Should You Audit Before a Redesign Starts?

Audit what currently works before deciding what to change. The goal is a written list of pages, keywords and journeys that the new site must protect, agreed before a single wireframe is drawn.

1. Export the last 12 to 16 months of Search Console performance data by page and by query, so you see which URLs earn clicks and for what.
2. Export landing-page data from Google Analytics 4 (GA4), including sessions and key events (GA4's term for important actions such as form submissions or purchases).
3. Pull your backlink profile from a tool such as Ahrefs, Semrush or Search Console's Links report, and flag every URL with external links pointing at it.
4. Crawl the live site with a crawler such as Screaming Frog or Sitebulb to capture titles, meta descriptions, headings, canonicals, status codes and internal link counts.
5. Record Core Web Vitals from the Search Console report or PageSpeed Insights for your main templates.
6. List every form, integration, tracking tag and third-party script, including who owns each account.
7. Interview sales or customer service about which pages they actually send people to. These often do not show up as high-traffic but matter commercially.

Phase 2: How Do You Build a Content Inventory?

A content inventory is a spreadsheet listing every indexable URL on the current site with its performance data and a decision about its future. It is the single document that connects the SEO audit to the new information architecture.

Combine URLs from four sources, because each one misses something: your CMS export, the crawler output, the Search Console pages report and the XML sitemap. Orphaned pages, old campaign landing pages and PDFs often appear in only one of them.

For each URL, add columns for organic clicks, key events, backlinks, primary query and a decision. Keep the decision vocabulary short:

• Keep: content moves across, refreshed but substantively the same.
• Merge: two or more thin pages combine into one stronger page; all of them redirect to it.
• Rewrite: same topic and intent, new copy; keep the URL if you can.
• Retire: no traffic, no links, no business value; redirect to the closest relevant page, or return a 410 or 404 if nothing relevant exists.

This is also the moment to plan new content. Pages built to answer specific buyer questions tend to perform better in both Google and AI assistants than generic brochure pages, which is the thinking behind our guide on getting your business recommended by ChatGPT, Gemini and Claude.

Phase 3: How Do You Map Old URLs to New Ones with 301 Redirects?

Map every old URL that has traffic, links or business value to the single most relevant new URL, then implement those mappings as server-side permanent redirects. Google recommends server-side 301 or 308 redirects where possible and advises redirecting straight to the final destination rather than through a chain.

Google's documentation notes that Googlebot can follow up to 10 hops in a redirect chain, but recommends avoiding chains anyway. Chains slow users down and multiply the places a redirect can break. If your old site already has redirects, update them so they point to the new final URLs rather than to URLs that now redirect again.

Practical mapping rules that save rework:

• Map one-to-one wherever a close equivalent exists. A page about a specific service should land on the new page about that service, not on a general services hub.
• Do not redirect everything to the homepage. Users arrive somewhere irrelevant, and search engines get no equivalent page to pass the old page's relevance to.
• Preserve query-string and trailing-slash behaviour deliberately, and decide whether uppercase and lowercase URLs resolve to one version.
• Test the full map with a crawler in list mode before launch: every old URL should return a single 301 to a page that returns 200.

Platform changes add their own wrinkles. Shopify, for example, uses fixed URL prefixes such as /products/ and /collections/, so almost every URL changes when you move to it; our Shopify migration checklist covers that case in detail.

Phase 4: What Analytics Baseline Should You Record Before Launch?

Record a dated snapshot of the metrics you will judge the redesign on, taken before launch and stored somewhere that will not change. Without it, any post-launch debate about whether traffic "dropped" becomes guesswork.

A useful baseline includes organic clicks and impressions by page and query, rankings for 20 to 50 priority keywords, key event counts and conversion rates by landing page, Core Web Vitals per template, and the number of indexed pages. Note anything seasonal: comparing a December launch to November traffic tells you little.

Check the tracking itself, too. Redesigns often break tags silently. List each GA4 key event, ad platform conversion and consent setting, and plan to re-test every one on staging. If you serve UK visitors, note that the Information Commissioner's Office (ICO) confirms all data protection provisions of the Data (Use and Access) Act 2025 were in force by June 2026, including changes allowing some cookies, such as those used for statistical purposes, without consent. Review your consent banner against the current guidance rather than copying the old configuration across.

Phase 5: How Should You Set Up Staging and Pre-Launch QA?

Build the new site on a staging environment that search engines cannot index, ideally protected by a password rather than only a noindex tag. Password protection keeps staging out of search results and makes it impossible for the setting to be forgotten in the content itself.

Run QA against the content inventory, not just against the design files. Before sign-off, check:

1. Every "keep", "merge" and "rewrite" page exists, with title tag, meta description, H1 and structured data agreed.
2. Primary content matches on mobile and desktop. Google's mobile-first indexing guidance is explicit that the mobile site should contain the same content, structured data and metadata as the desktop version.
3. Internal links point to final URLs, not to old URLs that will redirect.
4. Canonical tags reference the production domain, not the staging domain.
5. Core templates meet Core Web Vitals targets: Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile.
6. Forms submit, notifications arrive and CRM records are created, with real test entries.
7. Accessibility basics pass: keyboard navigation, focus states, alt text, colour contrast and form labels. Our guide to website accessibility for US and UK businesses explains why this matters legally as well as commercially.
8. Analytics, ad pixels and consent mode fire correctly, verified in each platform's debug view.

Phase 6: What Should Happen on Launch Day?

Launch day should be a scripted sequence with named owners, scheduled early in a quiet week, never on a Friday or before a holiday. Most damage happens in the first few hours if nobody is checking.

1. Take a full backup of the old site and database, and keep it accessible.
2. Deploy the new site and the redirect map together.
3. Remove password protection and any noindex directives; check the live robots.txt immediately.
4. Crawl the old URL list and confirm every redirect resolves in one hop to a 200 page.
5. Submit the new XML sitemap in Search Console and inspect a handful of key URLs with the URL Inspection tool.
6. If the domain changed, file the Change of Address request in Search Console. Google states this is not needed for same-domain path changes, HTTPS moves or www changes.
7. Place real test conversions and confirm they appear in GA4, ad platforms and your CRM.
8. Update URLs you control elsewhere: Google Business Profile, social profiles, email signatures and active ad campaigns.

Phase 7: How Long Should You Monitor a Site After Launch?

Monitor daily for the first two weeks and weekly for at least two to three months. Google's own guidance says a small to medium-sized website can take a few weeks for most pages to move, and larger sites take longer, with temporary ranking fluctuation expected along the way.

When a specific page drops, compare its old and new versions side by side: title, headings, word count, internal links pointing to it and whether its redirect works. The cause is usually visible within minutes. Keep redirects in place for at least a year, as Google advises, and indefinitely for URLs with external backlinks.

Should You Change Platform During a Redesign?

Change platform only when the current one genuinely limits you, and accept that combining a platform move with a redesign makes problems harder to diagnose. If you are weighing options, our comparison of WordPress, Webflow and custom code sets out the trade-offs, and our breakdown of what determines website development cost explains why migrations add effort beyond the design itself.

Where a platform change is unavoidable, lower the risk by keeping URL structures as close as the new platform allows and treating the redirect map as a launch blocker rather than a post-launch task.

How VEATEX Helps

VEATEX is a Shopify, web and software development agency that also builds Peppol e-invoicing platforms for the GCC, working with clients in the US, UK and the Gulf for over 11 years. For redesigns, we run the audit, content inventory and redirect map before design starts, build on WordPress, Webflow or custom code, and treat SEO preservation and tracking checks as part of launch rather than an add-on. See our website design and development service or browse recent work.