Web Development

The Complete Website Redesign Checklist (Without Losing Your Rankings)

A redesign can lift conversions or wipe out years of search visibility. This step-by-step checklist covers planning, SEO protection, QA and launch.

Illustration of a checklist clipboard beside old and new website layouts connected by redirect arrows

A redesign is one of the most visible investments a business makes in its digital presence — and one of the easiest to get wrong. New layouts and messaging can improve conversions, but a careless launch can erase rankings, break lead forms and lose data that took years to build. This website redesign checklist walks you through every phase: planning, protecting SEO, building, testing and launching, plus what to watch in the weeks afterward. Use it as a working document with your team or agency.

Phase 1: Define why you are redesigning

Before anyone opens a design tool, write down what must improve. Vague goals ("make it modern") lead to expensive rework.

  • List business goals: more qualified leads, fewer support calls, better product discovery, entering a new market.
  • Identify current problems from analytics, user feedback and sales team input.
  • Record baseline metrics: organic traffic, top landing pages, conversion rates, form submissions, page speed.
  • Decide what is in scope: visual refresh only, new content structure, new platform, or all three.
  • Agree on budget, timeline and who signs off on decisions.

If the redesign includes a platform change, read our guide to moving from WordPress to Laravel as well.

Phase 2: Audit what you already have

Your current site has value you cannot see in the design: rankings, backlinks and content that answers real questions.

  • Crawl the full site and export every URL, title, meta description and H1.
  • Export top pages by organic traffic and conversions for the last 12 months.
  • Export pages with external backlinks.
  • Note structured data in use (products, FAQs, articles, organization).
  • List all forms, where submissions go, and any integrations (CRM, email platform).
  • Inventory tracking: analytics, tag manager, ad pixels, conversion events.
  • Identify thin, outdated or duplicate content to merge or retire.

Phase 3: Plan the new structure and content

  • Design the new sitemap and navigation based on user tasks, not your org chart.
  • Map every old URL to its new equivalent (see the table below).
  • Keep high-performing URLs unchanged wherever possible.
  • Plan content updates — but keep the substance of pages that rank well.
  • Write unique titles and meta descriptions for new pages.
  • Plan structured data for each page type.
  • Prepare multilingual structure and hreflang if you serve several languages.

Example redirect map

Old URL New URL Action
/services/web-design.html /services/web-design 301 redirect
/about-us /about-us Keep (no change)
/news/2019-trade-show /news/trade-show-2019 301 redirect
/old-product-x /products/product-x-v2 301 to closest equivalent
/temp-promo-page (none) 410 or redirect to relevant category

Redirect to the closest relevant page, not the home page. Mass redirects to the home page are treated much like broken links.

Key takeaway: The redirect map is the single most important SEO document in a redesign. Every URL that has traffic or backlinks needs a deliberate destination.

Phase 4: Design and build with SEO and performance in mind

  • Use a mobile-first design approach; test on real devices.
  • Keep one clear H1 per page and logical heading levels.
  • Set performance budgets for images, fonts and scripts. (Our Core Web Vitals guide explains what to target.)
  • Use descriptive alt text for meaningful images.
  • Generate clean, readable URLs.
  • Build an XML sitemap that updates automatically.
  • Add canonical tags and avoid duplicate URL variations.
  • Meet accessibility basics: colour contrast, keyboard navigation, form labels.
  • Block the staging site from search engines with password protection, not only robots.txt.

Phase 5: Pre-launch QA

Test the new site as a customer would, and as a search engine would.

Functional checks

  • Every form submits, sends notifications, and reaches the CRM or inbox.
  • Thank-you pages and conversion events fire correctly.
  • Search, filters, and any login or checkout flows work end to end.
  • Emails are not landing in spam (check SPF, DKIM and DMARC).
  • 404 page is helpful and branded.

SEO checks

  • All redirects in the map return 301 and land on the right page — test them in bulk.
  • No redirect chains or loops.
  • Titles, meta descriptions and H1s are present and unique.
  • Structured data validates.
  • Internal links point to new URLs directly, not through redirects.
  • Analytics and tag manager are installed and tested.

Technical checks

  • SSL certificate is valid; all HTTP requests redirect to HTTPS.
  • Performance tested on mobile networks.
  • Backups are configured and a restore has been tested.
  • Error logging and uptime monitoring are active.

Phase 6: Launch day

Choose a low-traffic day and time, and avoid launching right before a weekend or holiday when your team is unavailable.

  1. Take a full backup of the old site and database.
  2. Freeze content changes on the old site.
  3. Deploy the new site and run database migrations.
  4. Remove staging restrictions: password protection, "noindex" tags, robots.txt blocks.
  5. Activate the redirect rules.
  6. Update DNS if the hosting has changed, keeping TTL low in advance.
  7. Run the redirect test list again on the live domain.
  8. Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools.
  9. Submit a few test leads and confirm they arrive.
  10. Announce internally and tell the sales and support teams what changed.

Phase 7: The first 90 days after launch

Some fluctuation in search traffic after a redesign is normal while search engines re-crawl. What you are watching for is sustained drops on specific pages.

  • Monitor Search Console daily in the first two weeks for crawl errors and 404s.
  • Compare top landing pages against your baseline weekly.
  • Fix any newly discovered broken URLs with redirects.
  • Check that conversion tracking matches actual form submissions.
  • Gather feedback from users and staff.
  • Review Core Web Vitals field data once enough visits accumulate.

Who should own each part of the checklist

A redesign touches marketing, sales, IT and leadership. Unclear ownership is how important items fall through the cracks. Assign a named person to each area before work starts.

Area Typical owner Responsibilities
Goals and sign-off Business owner or marketing lead Approves scope, budget, design and launch date
Content Marketing or communications Writes, edits and approves copy and images
SEO and redirects SEO specialist or agency URL inventory, redirect map, metadata, post-launch monitoring
Build and QA Development team Design implementation, integrations, testing, deployment
Tracking Marketing operations or analyst Analytics, tag manager, conversion events, ad pixels
Hosting, DNS and email IT or hosting provider DNS changes, SSL, backups, email authentication
Customer-facing teams Sales and support leads Test forms, review messaging, prepare for questions

Hold a short pre-launch meeting where each owner confirms their items are complete. It is a simple step that prevents most launch-day surprises.

Handling content during the build

Content is the part of a redesign most likely to cause delays. A few practical habits help:

  • Start content early, ideally in parallel with design, not after the build is finished.
  • Use real content in designs as soon as possible. Placeholder text hides layout problems and makes approvals meaningless.
  • Set a content freeze date on the old site so the final migration does not miss recent updates.
  • Keep a migration tracker listing each page, its owner, status and new URL.
  • Review legal and compliance pages — privacy policy, cookie notice, terms — since new forms, tracking tools or markets may require updates. Seek professional advice where regulations apply to your business.

Common mistakes to avoid

  • Leaving "noindex" on the live site.
  • Deleting old blog posts that still bring traffic.
  • Redirecting everything to the home page.
  • Changing domain, platform, structure and content all at once without a plan.
  • Forgetting ad landing pages, which can break paid campaigns overnight.
  • Not involving the people who answer customer enquiries.

Next steps

A redesign is part design project, part data migration and part SEO project. Treat all three with equal care and your new site should keep its hard-earned visibility. If you want an experienced team to handle the technical side, DigiVort's website migration and SEO and content services cover redirect mapping, QA and post-launch monitoring. Start a project to tell us about your current site and goals.

Frequently asked questions

Will redesigning my website hurt my Google rankings?

It can if URLs change without redirects, content is removed, or technical settings are wrong at launch. With a full URL inventory, 301 redirects, preserved content and careful post-launch monitoring, most redesigns keep their visibility and often improve it.

How long does a website redesign take?

For a typical business website, plan for several weeks to a few months from discovery to launch. Content preparation and approvals are often the biggest variables, so start them early.

Should we change our domain at the same time as the redesign?

Avoid it if you can. Changing domain and design at once makes it harder to diagnose any traffic changes. If a domain change is necessary, plan redirects and Search Console updates very carefully.

What is the most common redesign mistake?

Launching with the staging site's 'noindex' setting or robots.txt block still active, or forgetting redirects for old URLs. Both are easy to prevent with a launch checklist and a second person verifying.