Website Redesign Checklist: 15 Things to Fix Before Launching Your New Website

A website redesign is an opportunity to improve your brand presentation, user experience, website performance, and ability to generate leads. But a new design can also introduce technical problems that affect organic visibility, tracking, and conversions if important details are overlooked.

Pages that previously ranked in Google may lose visibility if their URLs change without proper redirects. Valuable content may disappear during migration. Analytics events may stop working, forms may fail on mobile devices, and search engines may struggle to crawl the new website.

That is why a successful redesign requires more than approving layouts and checking whether buttons work.

This website redesign checklist by Web & Digital Solutions covers 15 essential checks to complete before launching a new website. Whether you are redesigning a small business website, rebuilding an eCommerce store, or migrating to a new content management system, use these steps to protect your existing performance and prepare your website for launch.

Why You Need a Website Redesign SEO Checklist

A website redesign can change the elements that search engines and visitors rely on to understand and use your website. These changes may include URLs, page content, navigation, metadata, internal links, mobile layouts, and technical settings.

If these elements are not managed properly, a redesigned website may launch with broken links, missing pages, indexing restrictions, or incomplete conversion tracking.

A website redesign SEO checklist helps your team identify these risks before they affect users and organic search performance. It also gives designers, developers, SEO specialists, and marketing teams a shared list of launch requirements.

The objective is not to avoid every ranking fluctuation. It is to preserve valuable existing assets, resolve preventable issues, and ensure the new website is ready to be crawled, measured, and used by customers.

Website Redesign Checklist: 15 Essential Pre-Launch Checks

1. Crawl and Audit Your Existing Website

Before making changes, document how the current website performs and how it is structured.

Use a website crawler such as Screaming Frog to identify existing URLs, status codes, page titles, meta descriptions, canonical tags, headings, internal links, and indexability issues. Export the data so you can compare the old website with the new version later.

Also review Google Search Console and your analytics platform to identify pages that receive organic clicks, attract valuable traffic, or generate enquiries and sales.

Before launch, confirm:

• Important existing URLs have been recorded.
• High-performing pages have been identified.
• Existing technical errors are documented.
• Current organic performance has been saved as a baseline.

This baseline helps you distinguish existing problems from issues introduced during the redesign.

2. Create a Complete URL Mapping Spreadsheet

URL mapping is one of the most important parts of a website migration checklist.

If the new website uses different URLs, each old page should be mapped to the most relevant destination. A missing mapping can lead to broken links, unnecessary redirects, or users landing on irrelevant pages.

Create a spreadsheet containing the old URL, new URL, current status code, organic traffic or business importance, redirect requirement, and testing status.

For example:

Existing URL	New URL	Required action
/seo-services/	/seo-services-london-ontario/	Implement a relevant 301 redirect
/web-design/	/web-design-and-development-services-london-ontario/	Implement and test a 301 redirect
/about/	/about/	Verify the page remains accessible

These are illustrative examples. Use your actual URLs and confirm that each destination contains the relevant information.

Do not automatically redirect every deleted page to the homepage. Redirect to a genuinely relevant replacement when one exists. If a page has no suitable replacement, determine the appropriate response rather than creating an irrelevant redirect.

3. Implement and Test 301 Redirects

A permanent redirect helps send users and search engines from an old URL to its new destination.

Redirects are particularly important when changing URL structures, consolidating pages, moving to a new content management system, or retiring existing content.

Check that:

• Every changed URL has an appropriate redirect where required.
• Redirects point directly to the final destination.
• Redirect chains and loops are avoided.
• Redirects do not send unrelated pages to the same destination.
• Important legacy URLs no longer lead to avoidable 404 errors.

Test redirects using a crawler or HTTP status checker. Do not rely only on manually opening a few pages in your browser.

4. Preserve Important Content and Search Intent

A redesign often involves rewriting copy to fit a new layout. However, removing useful content without reviewing its SEO value can weaken a page’s relevance or eliminate information visitors need.

Before deleting or shortening content, review its organic performance, backlinks, search intent, and role in the customer journey.

Retain valuable information where appropriate, including service descriptions, location details, supporting sections, case studies, and answers to customer questions. If the content needs improvement, revise it while preserving its purpose and useful information.

The goal is not to keep every sentence unchanged. It is to ensure that the redesigned page continues to satisfy its intended audience and search intent.

5. Review Page Titles and Meta Descriptions

A redesigned template can accidentally remove metadata, duplicate titles, or generate titles that do not describe the page accurately.

Review the metadata of every important page before launch.

Your checklist should include:

• A unique, descriptive title for each important indexable page.
• A relevant meta description.
• Consistent targeting between the page topic and its title.
• Appropriate branding where it supports clarity.
• No unintended blank or duplicated metadata.

For example, a commercial service page should clearly communicate the service and intended location where relevant. Avoid assigning the same generic title to every service or location page.

Meta descriptions are not a direct Google ranking factor, but they can help communicate page relevance and influence how a search result is presented.

6. Check Headings and On-Page SEO Elements

Redesigning page templates can change heading structures, remove content sections, or introduce multiple visually prominent headings that are not organised logically.

Review the main heading, subheadings, image alternative text, internal links, and contextual content on important pages.

Use headings to establish a meaningful content hierarchy rather than choosing heading levels only for visual styling.

Also confirm that important service information remains accessible in crawlable page content and that links use descriptive anchor text where appropriate.

7. Verify Canonical Tags

Canonical tags help indicate the preferred URL when similar or duplicate pages exist.

During a redesign, canonical tags can accidentally continue pointing to staging URLs, old page versions, or unrelated destinations. This can create confusion about which page should be treated as the preferred version.

Before launch, confirm that:

• Important indexable pages have appropriate canonical URLs.
• Canonicals point to the intended live URLs.
• Staging or development URLs are not referenced unintentionally.
• Canonical tags are consistent with the chosen URL structure.

Canonical tags are signals rather than absolute directives, so they should be implemented alongside consistent internal linking and redirects.

8. Test Crawlability and Indexability

A website can look perfect to a visitor while remaining inaccessible to search engines.

Development websites are often protected by password restrictions, noindex directives, or robots.txt rules. These safeguards may be appropriate before launch but can become serious problems if they remain active on the production website.

Check the live website for:

• Accidental noindex directives.
• Robots.txt rules blocking important pages or resources.
• Incorrect canonical URLs.
• Accessible XML sitemaps.
• Working internal links to important pages.
• HTTP status codes that match the intended page behaviour.

Pay special attention to any settings copied from the staging environment. Verify the production configuration rather than assuming it is correct.

9. Review Internal Links and Navigation

Navigation changes can affect how users discover content and how search engines find important pages.

Review the main menu, footer links, breadcrumb navigation where applicable, contextual links, and links between related service pages and blog posts.

Make sure important pages remain accessible through useful internal links. Update links that still point to redirected URLs or pages that no longer exist.

For example, an educational blog about website performance can link to a relevant website optimisation service page. This helps readers discover related services while creating a logical connection between your content and service offerings.

Avoid forcing links into unrelated sections simply to increase internal link counts. Relevance and usability should guide your decisions.

10. Test Mobile Usability and Responsive Design

Your redesigned website should work across different screen sizes, not just on a desktop monitor.

Test important templates on mobile devices and smaller screens. Check whether text is readable, navigation is usable, forms are easy to complete, and key content remains available.

Review:

• Mobile navigation and dropdown menus.
• Buttons, links, and tap targets.
• Contact forms and field validation.
• Images, tables, and embedded content.
• Sticky elements that may cover important information.
• Layout shifts or horizontal scrolling.

Also verify that mobile users can access the same essential content and metadata as desktop users.

11. Check Page Speed and Core Web Vitals

A redesign can improve performance, but large images, excessive scripts, heavy animations, and unnecessary third-party tools can also make the new website slower.

Use Google PageSpeed Insights and real-user data in Google Search Console, where available, to assess performance.

Pay attention to Core Web Vitals:

• Largest Contentful Paint (LCP): Measures loading performance.
• Interaction to Next Paint (INP): Measures responsiveness to user interactions.
• Cumulative Layout Shift (CLS): Measures visual stability.

Google’s current good-performance thresholds are LCP at 2.5 seconds or less, INP at 200 milliseconds or less, and CLS at 0.1 or less, assessed at the 75th percentile.

Optimise oversized images, review font loading, reduce unnecessary JavaScript, and investigate slow server responses where needed. Test representative pages rather than checking only the homepage.

12. Verify GA4 and Google Search Console

A new website should launch with measurement systems configured correctly.

For Google Analytics 4, verify that the correct measurement ID is active and that page views are recorded as expected. If you use Google Tag Manager, confirm that the published container includes the required tags and triggers.

For Google Search Console, verify the appropriate website property and confirm that the new website can be monitored after launch.

Check that:

• Analytics is not missing from important templates.
• Tags are not firing twice.
• Internal testing traffic is handled appropriately.
• Search Console access is available to the responsible team.
• Reporting can be compared with the pre-launch baseline.

Do not assume that tracking works because the tag appears in the source code. Test actual events using the available debugging and real-time reporting tools.

13. Test Forms, Calls to Action, and Conversion Tracking

A redesigned website must do more than attract visitors. It should allow them to complete the actions that matter to the business.

Test every important conversion path, including contact forms, quote requests, phone links, booking flows, newsletter sign-ups, and checkout processes where applicable.

Submit test forms and verify that enquiries reach the correct inbox or CRM. Check confirmation messages, thank-you pages, error handling, and mobile form usability.

If conversions are tracked in GA4, confirm that the intended events fire correctly and that important events are configured as key events where appropriate.

For eCommerce websites, test the complete purchase journey, including add-to-cart, checkout, payment, order confirmation, and relevant transaction reporting.

A working button is not enough. Confirm that the action completes successfully and is measured accurately.

14. Test Structured Data, Images, and XML Sitemaps

If your existing website uses structured data, review it before migration and verify that the new templates preserve the relevant markup.

Check that structured data reflects visible page content and contains accurate information. Test important page types using the appropriate Google validation tools.

Also confirm that:

• Images load correctly and use appropriate dimensions.
• Meaningful images have descriptive alternative text.
• Important image URLs have not been unintentionally broken.
• The XML sitemap includes the intended canonical, indexable URLs.
• Redirected, non-canonical, or error URLs are not unnecessarily included in the sitemap.

Structured data can help search engines interpret content, but valid markup does not guarantee enhanced search appearances.

15. Complete a Final Pre-Launch Test

Before switching the new website live, run through a final quality assurance checklist with your designer, developer, SEO specialist, and marketing team.

Pre-launch checklist:

• URL mapping is complete.

• Required redirects are implemented and tested.

• Important content and metadata are retained or improved.

• Canonical tags are correct.

• The production website is crawlable and indexable as intended.

• Internal links and navigation work correctly.

• Mobile layouts and forms are usable.

• Page speed and Core Web Vitals have been reviewed.

• GA4 and conversion tracking have been tested.

• Structured data and XML sitemaps have been checked.

• Contact details, legal pages, and key calls to action are correct.

• Backups and a rollback plan are available.

Not every issue needs to block launch, but critical problems—such as a site-wide noindex, broken conversion forms, or missing redirects for important URLs—should be resolved before the website goes live.

What to Monitor After the Website Launches

Your website redesign checklist should continue beyond launch day. Some issues only become visible once search engines crawl the new website and real visitors begin using it.

During the first few days, verify that the website is accessible, forms work, analytics records activity, and no major technical errors have appeared.

Over the following weeks, monitor Google Search Console for indexing changes, crawl errors, organic clicks, impressions, and changes affecting important pages. Compare these results with your pre-launch baseline while accounting for normal fluctuations.

Review GA4 for changes in engagement and conversion activity. If performance declines, investigate whether the cause relates to technical accessibility, redirects, content changes, tracking errors, user experience, or external search changes.

Avoid making multiple large SEO changes at once without evidence. Identify the affected pages, investigate the likely cause, and prioritise fixes based on their impact.

Final Thoughts: Launch a Better Website Without Overlooking SEO

A website redesign should improve the experience for visitors while preserving the value your existing website has built over time. That means considering SEO, technical configuration, content, mobile usability, analytics, and conversions throughout the redesign—not treating them as last-minute tasks.

Use this website redesign checklist to align your team before launch, test the critical user journeys, and establish a baseline for measuring performance after the new website goes live.

At Web & Digital Solutions, we approach website design and development with a focus on usability, technical foundations, and search visibility. If your business is planning a redesign, our web design and development services can help you plan a website that supports your business goals. You can also explore our SEO services to understand how search optimisation can be incorporated into your wider digital strategy.

Frequently Asked Questions About Website Redesigns

1. What should I check before launching a redesigned website?

Review URL mapping, redirects, page content, metadata, canonical tags, crawlability, mobile usability, performance, analytics, conversion tracking, internal links, and forms. Test the live production website before announcing the launch.

2. Can a website redesign affect SEO rankings?

Yes. Changes to URLs, content, internal linking, canonical tags, redirects, and indexability can affect organic visibility. Careful planning and post-launch monitoring help reduce preventable problems, although ranking fluctuations cannot always be avoided.

3. Do I need 301 redirects when redesigning a website?

You generally need appropriate permanent redirects when important URLs change or pages are moved to new destinations. Map old URLs to relevant new pages, test the redirects, and avoid redirect chains and irrelevant homepage redirects.

4. Should I keep my existing website content during a redesign?

Retain content that serves users, supports search intent, attracts relevant traffic, or contributes to conversions. You can improve or consolidate content, but review its value before removing it.

5. How do I test SEO after a website launch?

Crawl the live website, test important redirects, inspect canonical tags and indexing directives, review the XML sitemap, and monitor Google Search Console. Compare organic performance against the pre-launch baseline and investigate unexpected changes.

6. How do I check whether analytics is working after a redesign?

Use GA4 real-time reporting, DebugView, and Google Tag Manager preview tools where applicable. Test page views and important conversion events, confirm tags are not duplicated, and verify that form submissions or purchases are recorded correctly.

7. How long should I monitor SEO after a website migration?

Monitor technical health immediately after launch and review organic performance regularly over the following weeks and months. The time needed to assess recovery or growth depends on the website, the scale of changes, crawling and indexing, and the competitiveness of its search market.