Website Redesign Checklist: What to Audit Before You Rebuild Your Site

A website redesign should start with an audit, not a mood board.

Before you rebuild anything, you need to understand what the current site is already doing well, where it is failing, which URLs and content are valuable, how users move through the site, what generates leads or sales, and which technical systems must survive the transition.

That matters because a redesign can improve UX, branding, performance, accessibility, and conversion rates, but it can also accidentally remove ranking pages, break analytics, drop backlinks, change important URLs, or make high-performing journeys harder to use.

This checklist is designed for businesses planning a redesign, CMS migration, visual refresh, or full website rebuild.

Why a Website Redesign Needs an Audit First

A redesign changes more than appearance.

Changing navigation can alter how users and search engines discover pages. Rewriting content can affect rankings and conversion intent. Replacing templates can change structured data, heading hierarchy, internal links, accessibility, and performance. Moving to a new CMS can affect URLs, forms, integrations, and analytics.

Google’s current site-move guidance emphasizes careful planning, URL mapping, redirects, testing, and monitoring whenever URLs change. It also recommends changing major elements in separate steps where possible rather than changing a domain, CMS, and layout all at once.

That principle applies even when you are not changing domains: reduce unnecessary variables and know what is changing before launch.

A strong redesign audit gives your team a baseline. Without one, it is difficult to tell whether the new website actually improved anything.

Website Redesign Checklist at a Glance

Use this table as the summary. The sections below explain what to inspect in each area.

1. Define Why You Are Redesigning the Website

Start with the business problem.

Common redesign triggers include:

• the site looks outdated
• the brand or positioning changed
• users struggle to find information
• lead quality is weak
• conversion rates are poor
• mobile UX is frustrating
• the site is difficult to edit
• the CMS no longer fits the business
• performance is poor
• accessibility problems are known
• organic traffic has outgrown the current structure
• the company added new products, services, markets, or audiences

Do not combine these into the vague goal “make the site better.”

Write specific redesign objectives such as:

• increase qualified demo requests
• reduce mobile form abandonment
• make three core services easier to discover
• consolidate overlapping service pages
• improve Core Web Vitals
• migrate to a CMS the marketing team can manage
• improve WCAG 2.2 AA accessibility
• preserve organic traffic during a new information architecture rollout

These goals become the standard against which the redesign is judged.

If you are still defining the broader build process, our website development process guide explains how discovery, design, development, QA, launch, and maintenance fit together.

2. Record Your Current Analytics Baseline

Before changing layouts, content, or tracking, capture the current performance of the site.

At minimum, record:

• total users and sessions
• organic search traffic
• direct traffic
• referral traffic
• paid landing-page traffic
• conversions
• conversion rate
• form submissions
• purchases or revenue
• demo bookings
• phone or email clicks
• top landing pages
• top exit pages
• device split
• traffic by country or market
• important event completions

Use a long enough period to account for seasonality. A 30-day snapshot can be misleading for businesses with quarterly or seasonal demand.

For ecommerce, also capture:

• revenue
• transactions
• average order value
• checkout completion
• product page performance
• cart abandonment
• top-selling products
• revenue by landing page or channel

This baseline lets you compare the redesigned site against the old one using business outcomes rather than subjective opinions.

3. Export Search Console Data Before the Rebuild

If organic traffic matters, preserve a pre-redesign SEO benchmark.

Export or record:

• queries with the most clicks
• queries with the most impressions
• pages with the most clicks
• pages with the most impressions
• average positions
• click-through rates
• indexed-page patterns
• crawl or indexing issues
• sitemap status
• Core Web Vitals reports
• manual actions or security issues, if any

Pay particular attention to pages that generate traffic even if they look visually unimportant.

A dated blog post, old service page, PDF, location page, or comparison page may be attracting qualified search traffic and backlinks. Removing it without a migration decision can create avoidable losses.

4. Build a Complete URL Inventory

Create a list of the current site’s URLs before designing the new sitemap.

Sources can include:

• XML sitemaps
• CMS exports
• analytics landing pages
• Search Console
• server logs
• crawl tools
• internal links
• backlink reports

Include more than standard pages. Inventory:

• pages
• posts
• products
• categories
• tags
• author archives
• location pages
• campaign pages
• PDFs
• images that receive search traffic
• downloadable assets
• old URLs that still receive visits
• existing redirected URLs

Google’s site-move guidance specifically recommends creating an old-to-new URL mapping when URLs change and using permanent redirects to the most relevant destination.

Do not wait until launch day to figure out where old URLs should go.

5. Classify Every Important Page: Keep, Improve, Merge, Redirect, or Remove

Your redesign should not blindly migrate every piece of old content.

Assign each meaningful URL an action:

• Keep: the page performs well and still serves a clear purpose.
• Improve: the topic or page is valuable but needs better content, UX, or conversion design.
• Merge: multiple pages overlap and should become one stronger page.
• Redirect: the page is being replaced by a new relevant URL.
• Remove: the content no longer serves users or the business and has no useful replacement.

Use evidence when making decisions.

A page with low traffic may still be important because it supports sales conversations, customer onboarding, internal linking, or a specific high-value query. A high-traffic page may generate little business value.

Evaluate traffic, rankings, backlinks, conversions, relevance, and user intent together.

6. Identify Your Highest-Value Organic Landing Pages

Create a protected list of pages that currently perform well in search.

For each, record:

• current URL
• primary topic
• major ranking queries
• traffic
• backlinks
• internal links
• conversion contribution
• current title and H1
• content sections
• structured data
• canonical URL
• intended redesign action

These pages deserve extra care.

If a ranking URL can stay the same, keeping it stable is often simpler than changing it without a strong reason.

If the URL must change, map it directly to the closest equivalent page rather than sending many unrelated URLs to the homepage. Google warns that irrelevant mass redirects can confuse users and may be treated like soft 404s.

7. Audit Backlinks Before Removing or Moving Pages

Backlinks can be easy to overlook during visual redesign work.

Identify pages with meaningful external links and note:

• linking domains
• destination URL
• anchor context
• whether the destination will remain
• new destination if it changes

If a linked page is removed or merged, preserve the value and user path with the most relevant permanent redirect.

Also check important links from:

• business directories
• partner websites
• industry publications
• social profiles
• paid campaigns
• email templates
• downloadable documents

After launch, update high-value external links when practical rather than relying forever on redirects.

8. Audit the Current Information Architecture

A redesign is an opportunity to simplify the site structure, but only after you understand the existing one.

Review:

• main navigation
• dropdowns and mega menus
• service hierarchy
• product categories
• resource organization
• footer navigation
• breadcrumbs
• local or regional sections
• account areas
• search
• utility links

Ask whether users can quickly answer:

• Where am I?
• What does this company offer?
• Which option applies to me?
• Where can I learn more?
• What should I do next?

Look for duplicate labels, vague menu items, overly deep hierarchies, hidden high-value pages, and categories that reflect internal company language rather than customer language.

Our website navigation best practices can help when rebuilding the menu and page hierarchy.

9. Audit the Homepage Against Its Actual Job

Do not redesign the homepage only because stakeholders are tired of looking at it.

Evaluate whether the current homepage clearly communicates:

• what the company does
• who it is for
• why it is different
• what visitors should do next
• major services or product categories
• evidence and trust
• relevant proof
• important paths into the website

Review homepage analytics and click behavior if available.

If the homepage sends users into several distinct journeys, note which ones matter most before changing hierarchy.

Use our homepage design best practices when planning the new version.

10. Audit Conversion Paths, Not Just Individual Pages

A user rarely converts because of one isolated page.

Map important journeys such as:

Search landing page → service page → case study → contact form

or:

Paid landing page → product page → cart → checkout → purchase

For each journey, inspect:

• entry point
• next-step clarity
• CTAs
• friction
• trust
• forms
• error states
• mobile usability
• confirmation experience
• follow-up workflow

A redesign can improve one page while breaking the journey around it.

Record current conversion rates for your most important paths so you know what the redesign needs to beat.

11. Audit Forms, Checkout, Booking, and Other Critical Functions

List every interactive function the current site depends on.

Examples:

• contact forms
• lead forms
• newsletter forms
• checkout
• payment gateways
• booking
• quote calculators
• site search
• filters
• account login
• membership
• file uploads
• chat
• gated downloads
• CRM synchronization
• support widgets

For each function, record:

• where it appears
• which tool powers it
• where data goes
• notifications it triggers
• integrations involved
• tracking events
• consent requirements
• owner inside the business

This prevents a common redesign failure: the new site looks correct but breaks an operational workflow nobody documented.

12. Audit Mobile and Tablet UX Separately

Do not assume desktop problems describe the whole site.

Review actual mobile and tablet behavior for:

• navigation
• tap targets
• sticky elements
• forms
• popups
• tables
• pricing sections
• comparison grids
• accordions
• product galleries
• checkout
• long headings
• horizontal overflow
• landscape orientation

Look at analytics by device to identify pages where mobile conversion or engagement is materially worse than desktop.

The redesign should solve those problems rather than simply reproduce the old desktop structure in a more modern visual style.

See our responsive web design best practices for a broader cross-device implementation checklist.

13. Run an Accessibility Audit Before You Redesign

Accessibility issues should become design requirements, not bugs discovered after development.

Audit:

• heading hierarchy
• semantic landmarks
• keyboard navigation
• focus visibility
• focus order
• color contrast
• link purpose
• image alt text
• form labels
• error messages
• required-field instructions
• modal and menu behavior
• captions and transcripts
• zoom and text resizing
• content reflow
• touch target sizing
• motion and animation
• authentication flows

W3C recommends using the latest WCAG 2 version, and WCAG 2.2 remains the current Recommendation. WCAG testing also requires more than automated scans; manual and assistive-technology testing are important for issues tools cannot reliably interpret.

Use the existing problems as acceptance criteria for the new design.

Our website accessibility checklist provides a more detailed audit framework.

14. Benchmark Performance and Core Web Vitals

Capture performance before redesigning so the new visual system does not become slower.

Measure:

• Largest Contentful Paint
• Interaction to Next Paint
• Cumulative Layout Shift
• server response time
• image weight
• JavaScript weight
• CSS weight
• font loading
• third-party scripts
• number of requests
• caching behavior

Current Core Web Vitals guidance defines good thresholds at the 75th percentile as:

• LCP: 2.5 seconds or less
• INP: 200 milliseconds or less
• CLS: 0.1 or less

Measure both field data and lab diagnostics where available.

Record which pages, templates, images, scripts, or third-party tools are causing problems so the redesign team knows what not to reproduce.

15. Audit Technical SEO Before the New Build

Before rebuilding, document the current technical SEO setup.

Review:

• title tags
• meta descriptions
• headings
• canonical tags
• robots meta directives
• robots.txt
• XML sitemaps
• structured data
• hreflang
• pagination
• internal links
• redirects
• 404s
• duplicate URLs
• parameter URLs
• indexable archives
• image URLs
• HTTPS
• status codes

You do not need to preserve every existing implementation.

You do need to understand it before replacing it.

For WordPress sites, use our WordPress SEO checklist to make sure the redesigned CMS preserves the fundamentals.

16. Audit Existing Redirects and Legacy URLs

A redesign is not the first migration for many sites.

You may already have redirects from:

• old domains
• previous slugs
• HTTP to HTTPS
• discontinued products
• old campaigns
• deleted categories
• previous redesigns

Export the current redirect rules before changing hosting, CMS, plugins, or server configuration.

If you replace old redirects without carrying them forward, long-lived backlinks and bookmarks may start returning 404s.

Avoid unnecessary redirect chains. Where possible, old URLs should point directly to the final destination.

17. Audit Canonicals, Indexing Rules, and Staging Protections

Redesign projects frequently use staging environments.

Document how staging is protected and how the live site currently handles indexing.

Before launch, confirm that the production site will not accidentally inherit:

• noindex
• blocked robots.txt rules
• staging canonicals
• staging sitemap URLs
• password-protection logic
• test analytics IDs

Google’s site-move guidance specifically reminds site owners to remove temporary noindex rules and ensure canonical annotations point to the new live URLs.

These checks belong in the launch plan before development begins.

18. Audit Analytics, Pixels, Consent, and Event Tracking

List every measurement and advertising system on the existing site.

Examples:

• Google Analytics
• Google Tag Manager
• Google Ads
• Meta Pixel
• LinkedIn Insight Tag
• Microsoft Advertising
• heatmaps
• session recording
• affiliate tracking
• call tracking
• consent management platform
• CRM attribution
• custom events

Record:

• account IDs
• container IDs
• events
• conversions
• triggers
• custom dimensions
• ecommerce tracking
• consent dependencies
• cross-domain tracking

The redesigned site should not launch with “we will add analytics later.”

If your new CTA names, forms, checkout steps, or URL structures change, tracking may also need to change.

19. Audit CMS, Plugins, Integrations, and Business Dependencies

Create a technology inventory.

Document:

• CMS
• theme or page builder
• plugins
• ecommerce platform
• payment gateways
• forms
• CRM
• email marketing
• automation tools
• ERP
• booking tools
• search
• CDN
• hosting
• DNS
• transactional email
• authentication
• APIs
• webhooks
• analytics
• consent platform

For each dependency, ask:

• Is it still needed?
• Who owns the account?
• Is it actively supported?
• Is the license transferable?
• Is there a better alternative?
• Does the new CMS support it?
• What happens if it fails?

A redesign can be the right time to simplify the stack, but removals should be deliberate.

20. Audit Content Ownership and Migration Responsibility

Decide who is responsible for every content task.

Clarify:

• who writes new copy
• who approves it
• who exports existing content
• who migrates it
• who formats it
• who sources images
• who writes alt text
• who checks links
• who uploads PDFs
• who validates SEO metadata
• who reviews redirects

Content migration is often treated as a small line item and then becomes one of the largest sources of delay.

Separate “move the content” from “decide whether this content should exist.” Those are different tasks.

21. Audit Brand Assets and Design-System Requirements

Inventory the assets the redesign will use:

• logos
• logo variations
• color palette
• typography
• icons
• illustrations
• photography
• UI patterns
• brand guidelines
• downloadable assets
• video

Also identify inconsistencies in the current site.

The new design system should solve repeated problems rather than simply create another set of one-off page designs.

Our web design best practices covers hierarchy, consistency, usability, and conversion principles that are useful during this stage.

22. Review Hosting, Security, Backups, and Deployment

Document the current infrastructure before changing it.

Check:

• hosting provider
• server environment
• PHP/runtime versions where relevant
• SSL/TLS
• CDN
• DNS
• backups
• backup retention
• restore process
• firewall/security services
• administrator accounts
• deployment process
• staging environment
• transactional email
• uptime monitoring

Take a verified backup before any migration or launch.

Know how to roll back if the redesign causes a critical issue.

A redesign launch should have both a go-live plan and a recovery plan.

23. Create an Old-to-New URL Mapping Before Development Ends

Do not leave redirects until the final day.

Your mapping should identify:

• old URL
• action
• new URL
• redirect type
• notes
• owner
• validation status

Example:

If a page has no relevant replacement, forcing a redirect to the homepage is usually worse than returning a proper 404 or 410.

Google recommends direct, relevant permanent redirects for moved pages and advises keeping them for at least a year, often longer for users.

24. Decide Which URLs Should Stay Exactly the Same

A redesign does not require a new URL structure.

Keep existing URLs when:

• the page topic is unchanged
• the URL is already clean
• the page ranks well
• it has backlinks
• changing it provides little benefit

Change URLs when there is a genuine architectural or naming reason.

Every unnecessary URL change creates migration work, testing work, redirect dependency, and potential reporting disruption.

25. Define Redesign Success Metrics Before Launch

Choose the metrics that will determine whether the redesign worked.

Depending on the business, track:

• qualified leads
• lead conversion rate
• sales
• revenue
• demo requests
• booking completion
• checkout completion
• product discovery
• organic clicks
• non-branded search visibility
• mobile conversion rate
• Core Web Vitals
• accessibility defects
• support requests
• content engagement
• task completion

Avoid using “time on site increased” as the only sign of success. More time can mean stronger engagement or greater confusion.

Tie metrics to the goals defined at the beginning.

26. Build a Pre-Launch Comparison Checklist

Before launch, compare the new site against your audit.

Verify:

• every retained page exists
• every changed URL has a mapped outcome
• redirects work
• high-value internal links still exist
• titles and metadata are present
• canonicals are correct
• structured data is appropriate
• forms submit successfully
• CRM and email workflows work
• analytics events fire
• paid pixels work
• consent works
• mobile layouts work
• keyboard navigation works
• accessibility issues were addressed
• Core Web Vitals did not materially regress
• sitemap uses live URLs
• robots.txt is correct
• production pages are indexable
• staging URLs are not referenced
• 404 page works
• backups are available
• launch rollback steps are documented

A redesign is ready when the business, technical, SEO, and user-experience requirements are ready—not when the homepage looks finished.

Common Website Redesign Mistakes to Avoid

The most damaging redesign mistakes usually come from missing context rather than bad visual taste.

Avoid:

• redesigning without baseline data
• deleting ranking pages because they look old
• changing every URL for cosmetic reasons
• merging pages without checking search intent
• launching without redirects
• redirecting everything to the homepage
• rebuilding navigation without user journeys
• forgetting existing redirect rules
• carrying staging noindex rules into production
• losing analytics or conversion tracking
• ignoring mobile-specific problems
• postponing accessibility until after launch
• adding heavy animation without performance budgets
• migrating every weak page because it already exists
• changing CMS, domain, content, and architecture simultaneously without a controlled plan

A redesign should reduce risk while improving the site, not exchange known problems for unknown ones.

Website Redesign Audit Checklist

Before approving the redesign scope, confirm that you have:

• [ ] documented business goals and conversions
• [ ] captured analytics benchmarks
• [ ] exported Search Console data
• [ ] created a complete URL inventory
• [ ] classified important content
• [ ] protected high-value organic landing pages
• [ ] audited backlinks
• [ ] reviewed navigation and information architecture
• [ ] mapped conversion journeys
• [ ] documented forms and critical functionality
• [ ] audited mobile and tablet UX
• [ ] audited accessibility
• [ ] benchmarked Core Web Vitals
• [ ] documented technical SEO
• [ ] exported existing redirects
• [ ] reviewed canonicals and indexing rules
• [ ] documented analytics and ad tracking
• [ ] inventoried CMS, plugins, and integrations
• [ ] assigned content migration responsibilities
• [ ] inventoried brand assets
• [ ] documented hosting, backups, and deployment
• [ ] prepared old-to-new URL mappings
• [ ] identified URLs that should remain unchanged
• [ ] defined redesign success metrics
• [ ] created a pre-launch comparison checklist

This audit becomes the redesign brief.

Final Takeaway

A website redesign should begin by understanding the current system.

Before rebuilding, identify which pages attract traffic, which journeys convert, which URLs have links, which technical systems support the business, which accessibility and performance problems need fixing, and which content no longer deserves to survive.

Then redesign intentionally.

Preserve what is valuable. Improve what is weak. Remove what is unnecessary. Map every meaningful change.

That approach gives the new site a better chance of improving usability, conversions, SEO, and maintainability without sacrificing the value the current website has already earned.

Frequently Asked Questions