Website redesign checklist: how to relaunch without losing traffic

A website redesign SEO checklist is the list of steps that protects your search traffic and leads while the site changes. It covers what to record before the redesign, what to decide during it, what to test before launch and what to watch after.

Redesigns lose traffic for predictable reasons. URLs change and nobody sets up redirects. Pages that quietly earned visits get cut because they did not fit the new navigation. Page titles and headings get rewritten for style and lose the words people search. Analytics or call tracking breaks, so the team cannot even see the drop. Each step below closes one of those gaps.

The checklist applies whether you are a law firm replacing a ten-year-old site, a dental group consolidating location sites, a property management company changing platforms or a salon moving from a website builder to a custom build.

Start by recording every page and what it earns, because you cannot protect what you have not measured. Pull this before the design work starts so it shapes the new site map.

Pre-redesign checklist:

• Export every URL from your current sitemap, your CMS and a crawl. Screaming Frog, Sitebulb or the site audit tools in Semrush and Ahrefs can crawl a site; Google's site move guidance also suggests checking server logs and analytics for URLs you might miss.
• In Google Search Console, export the Pages report under Performance for the last 12 months: clicks, impressions and average position for each page.
• In Google Analytics 4, export landing pages with sessions and key events (form submits, calls, bookings) for the same period.
• Export the queries each top page ranks for, so you know which words to keep in titles and headings.
• List pages with external links pointing to them, using Search Console's Links report or a backlink tool.
• Record current page titles, meta descriptions, H1s and structured data for your top pages.
• Save a full copy of the old site (a crawl export plus screenshots of key pages) for reference.
• Note your baseline: total organic clicks, organic leads and top page positions, so you can compare after launch.

Keep every page that earns traffic, leads or links unless you have a clear reason to retire it, and give it a clear home in the new structure. Pages that earn little can be merged into stronger pages or retired with a redirect to the closest match.

Sort the inventory into four groups:

• Keep and improve: service pages, location pages and articles that bring clicks or leads. Keep their topic, keep the words they rank for, and improve the content.
• Merge: thin pages on the same topic (three short pages about 'estate planning', 'wills' and 'trusts' might become one strong page with sections). Redirect each old URL to the merged page.
• Retire with redirect: outdated promotions, old staff pages, discontinued services. Redirect to the closest relevant page, such as the parent service page.
• Retire without redirect: pages with no traffic, no links and no relevant replacement can return a 404 or 410 status.
• Where you can, keep the same URL. The safest redirect is the one you never need.

Map every old URL to its closest new URL in a spreadsheet, then implement those as server-side permanent redirects. Google's documentation on site moves with URL changes recommends 301 or 308 redirects from each old URL to its new one, sending each redirect directly to the final destination and keeping chains short.

Google also warns against redirecting many old pages to an unrelated page such as the homepage. A retired 'kitchen remodeling' page should redirect to the remodeling services page, not the home page. A dental office's old 'Invisalign' page should go to the new clear aligners page.

Redirect mapping checklist:

• One row per old URL, including URLs with and without trailing slashes, old blog paths, PDFs and image URLs that earn traffic.
• Columns: old URL, new URL, redirect type (301), reason, tested (yes/no).
• No redirect chains: if an old page already redirects somewhere, point it straight to the final new URL.
• Update internal links on the new site to point directly at new URLs, not through redirects.
• Update canonical tags so each new page points to itself.
• Plan to keep redirects for at least a year. Google recommends a minimum of one year and suggests keeping them indefinitely if you can.
• Contact the sites that send you the most referral traffic and ask them to update their links.

Redesigns often lose rankings through copy and template changes rather than URLs. Before approving new page copy, compare it against the inventory from Phase 1.

On-page checklist for each important page:

• The page title still includes the main phrase the old page ranked for.
• The H1 and opening paragraph answer what the page is about in plain words.
• The useful content from the old page survived, or was improved. Pricing ranges, process steps and FAQs often get cut for design reasons and take rankings with them.
• Each page has one H1, with logical H2s below it.
• Images have descriptive file names and alt text.
• Structured data (LocalBusiness, Service, FAQ where appropriate) is carried over or added.
• Page speed is at least as good as before. Test key templates with PageSpeed Insights on the staging site.
• The staging site is blocked from search engines (password protection is safest), and that block is removed at launch.

Test every way a customer can contact you on the staging site, because a redesign that ranks well but drops leads is still a failed launch. This step is where service businesses most often lose money quietly.

Pre-launch testing checklist:

• Submit every form and confirm the notification reaches the right inbox and the lead lands in the CRM.
• Click every phone number on a mobile phone; confirm call tracking numbers still swap correctly.
• Open every booking link and complete a test booking.
• Confirm Google Analytics 4, Google Tag Manager and any ad conversion tags fire on the new templates, and that key events still record.
• Check chat widgets, cookie banners and accessibility features on mobile and desktop.
• Run a crawl of the staging site to catch broken links, missing titles and accidental noindex tags.
• Test a sample of redirects from the mapping sheet, then test all of them in bulk right after launch.

Launch early in the week, early in the day, when your team can watch and fix problems. Avoid launching before a holiday or your busiest season.

Launch day checklist:

• Remove the staging password or noindex block from the live site.
• Confirm robots.txt allows crawling of the pages you want indexed.
• Test redirects in bulk using your mapping sheet and a crawler in list mode.
• Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools.
• If the domain itself changed, use Search Console's Change of Address tool for the old domain. Google notes this is not needed for path changes or HTTP to HTTPS moves on the same domain.
• Update your Google Business Profile website link and any booking links if they changed.
• Submit a test form and make a test call from the live site.

Watch Search Console and your lead data closely for the first eight to twelve weeks. Google's site move guidance says rankings may fluctuate temporarily while Google recrawls and reindexes, and that for medium-sized sites the switch can take a few weeks or more, with larger sites taking longer.

What to check each week after launch:

• Search Console Pages report: indexed pages, and any spike in 'Not found (404)' or 'Page with redirect' issues.
• Performance report: clicks and impressions compared with the same weeks before launch.
• Top 20 pages from your inventory: are they indexed at the new URL and holding position?
• Leads: form submissions, calls and bookings from organic search compared with your baseline.
• Crawl errors and 404s from server logs; add redirects for any old URLs you missed.
• If a key page drops and stays down after several weeks, compare its new content and title to the old version first. A lost section or changed heading is the most common cause.

Name one person who owns the inventory, redirect map and launch testing, separate from the person who owns the design. Designers and developers are focused on how the new site looks and works; someone needs to be accountable for what the old site was earning and whether the new one keeps it.

That owner signs off on three things before launch: the redirect map is complete and tested, every top page from the inventory has a home on the new site, and every form, call path and booking link has been tested end to end. After launch, the same person reports organic clicks and leads against the baseline until they recover.

Monvell's Development team builds redesigns with the inventory, redirect map and launch testing written into the project plan, and our Marketing team monitors search performance through the weeks after launch.