Website Redesign Checklist: 5 Phases, Every Check Tied to Conversions

A complete website redesign checklist runs through five phases: audit, plan, build, test and monitor, with every item tied to a measurable business outcome rather than a visual preference. The first action is always the same: run an analytics and SEO audit, or gather stakeholders and data owners if that audit does not yet exist.

TL;DR:

• Export 12 months of page level analytics, inventory indexed URLs, record rankings and backlinks, then name approvers before wireframes begin.
• Set 2 to 4 KPIs against your baseline, monitor results daily for 14 to 30 days, and wait at least 30 days before judging.
• Give every old URL with traffic, rankings, or backlinks a named destination, preserve metadata, and monitor Search Console as new pages enter the index.
• Test real visitor performance against Core Web Vitals thresholds at the 75th percentile: LCP 2.5 seconds, INP 200 milliseconds, and CLS 0.1.
• On staging, test mobile journeys, every form and payment flow, plus WCAG 2.2 AA basics such as keyboard access, visible focus, and sufficient contrast.

Table of Contents

• The complete checklist at a glance
• Pre-redesign audit: what to pull before you touch a single page
• Setting goals, KPIs and a measurement plan
• UX and conversion checks that protect the redesign's purpose
• Content strategy, URL mapping and protecting your SEO equity
• Performance and Core Web Vitals checklist
• Accessibility checks aligned to WCAG 2.2
• Quality assurance, launch checklist and rollback plan
• Post-launch monitoring and how to read the data
• GridLock Digital: a practical worked example of delivering this checklist
• Why most redesigns miss the point
• Get the checklist built for you, not just planned
• FAQ
• Sources

The complete checklist at a glance

Every redesign follows the same five phases, and each one has a handful of checks that matter more than the rest. Keep this list next to your project plan and tick items off as you go, or copy it into your own tracker.

• Audit: export 12 months of analytics by page, list top 20 pages by traffic and conversions, and record current keyword rankings.
• Plan: agree 2 to 4 KPIs, map personas to priority journeys, and get sign off from every decision owner.
• Build: apply conversion-centred UX rules, preserve metadata and build a 1:1 redirect map.
• Test: check Core Web Vitals, run WCAG 2.2 accessibility checks, and test every form and payment path on staging.
• Monitor: watch indexing, traffic and conversions daily for the first 14 to 30 days against your pre-launch baseline.

If you want a working version of this, build a simple spreadsheet with one tab per phase, a column for owner, a column for status and a column for evidence (a screenshot, a report link or a test result). That single document becomes your traceability record when stakeholders ask what changed and why.

Pre-redesign audit: what to pull before you touch a single page

Nothing in a redesign should start before you know what the current site actually does. Skipping this step is the single most common reason redesigns lose traffic or conversions after launch, according to HubSpot's redesign checklist, which found that treating a redesign as an aesthetic refresh rather than a documented, metrics-led project is the recurring pitfall behind failed relaunches.

1. Pull your baseline metrics first. Export the last 12 months of analytics by page: sessions, bounce rate, conversion rate and revenue or lead value where it exists. A full year smooths out seasonality that a 90-day window would hide.
2. Build a content inventory and score each page. List every indexed URL, then mark it keep, merge or archive based on traffic, conversions and whether it still matches a current business goal.
3. Record your SEO baseline. Note your top-ranking pages, the keywords they rank for, and which pages hold the most valuable backlinks, since these are the pages a redirect mistake can damage most.
4. Confirm who approves what. Name the decision owner for content, design, SEO and development sign-off, and agree the overall timeline before any wireframe exists.

Treat this audit as the traceability record for everything that follows: a later test or metric only means something when you can compare it to a number you captured here.

Setting goals, KPIs and a measurement plan

A redesign without a defined success metric is just a new coat of paint. Before any design work starts, agree 2 to 4 KPIs that map directly to how the business makes money.

• Lead generation businesses: track form submissions and cost per lead, not just traffic.
• Service and trade businesses: track calls initiated and quote requests started versus completed.
• Hospitality and bookings: track booking completions and average booking value.
• Ecommerce or revenue sites: track revenue per visitor alongside conversion rate, since traffic alone can mask a drop in order value.

Set an uplift target against your audit baseline rather than an industry figure, since your own historical data is the only number your team controls for and understands. Give yourself a measurement window of at least 30 days post-launch before judging results, since early traffic patterns are often noisy. Finally, map each KPI to the specific pages and user journeys it depends on, so a drop in conversions points you straight to the page or step that changed rather than the whole site.

UX and conversion checks that protect the redesign's purpose

Visual refreshes are the easy part. The checks that actually protect revenue are the ones that govern how a visitor moves from landing on a page to taking an action.

• Map priority journeys first. Define the two or three paths that matter most, such as "find a service, see pricing, request a quote," and design every related page around that path.
• Cut steps to conversion. Every extra click or page between arrival and action is a chance to lose someone, so flatten navigation and remove unnecessary intermediate pages.
• Make calls to action unmistakable. A visitor should never have to search for the "call us" or "get a quote" button; it belongs above the fold on every key page.
• Shorten forms. Ask only for what you need to follow up, since every additional field reduces completion rates.
• Check mobile first, not last. Test every journey on a phone before checking desktop, since most visitors will arrive that way.
• Add trust elements near the decision point. Reviews, guarantees or clear contact details next to a CTA reduce hesitation at the exact moment it matters.

Conversion-centred design rests on behavioural principles: focus, structure and reduced friction, and small changes like clearer CTAs or shorter forms often produce outsized gains in completion rates.

Pro Tip: Put your primary CTA in the same place on every key page; consistency reduces the thinking a visitor has to do.

Content strategy, URL mapping and protecting your SEO equity

A redesign that quietly tanks your rankings is almost always a redirect or metadata failure, not a ranking algorithm problem. Work through this in order.

1. Build a 1:1 redirect map before development starts. Every old URL that has traffic, rankings or backlinks needs a named destination; a redesign that changes URLs without this map is the most common cause of lost organic traffic.
2. Preserve or improve metadata and structured data. Title tags, meta descriptions and schema markup should carry over unless you have a specific reason and a replacement ready.
3. Update internal links and reach out on high-value backlinks. Fix internal links pointing to old URLs, and where possible, ask external sites linking to a changed page to update the link rather than rely on a redirect alone.
4. Watch Search Console through the transition. Google's own guidance on site moves confirms that warnings in Search Console are expected as redirects take effect, and the right response is active monitoring and a complete redirect map rather than treating every warning as a crisis. Submit a fresh sitemap and watch the index count until old URLs drop out and new ones appear.

Performance and Core Web Vitals checklist

Speed is not a nice-to-have in a redesign, it is a conversion lever. Google's Core Web Vitals set the industry benchmark for user-centric performance: Largest Contentful Paint at 2.5 seconds or under, Interaction to Next Paint at 200 milliseconds or under, and Cumulative Layout Shift at 0.1 or under, all measured at the 75th percentile of real visits.

Mobile pages that take longer than three seconds to load see substantially higher visitor abandonment, which is why performance belongs on the same checklist as design and content, not as an afterthought once the site is built.

• Optimise images before upload: correct dimensions, modern formats and compression.
• Lazy load anything below the fold so it does not compete for initial load time.
• Inline critical CSS and defer non-essential styles.
• Defer or async third-party scripts such as chat widgets and tracking pixels.
• Use caching and a CDN to cut server response time for repeat and distant visitors.

Test with Lighthouse and PageSpeed Insights before launch, and use CrUX or a Real User Monitoring provider afterwards, since the thresholds themselves were set using real-world field data and combining field and lab results gives the clearest picture of where a fix is actually needed. Keep watching these metrics weekly after launch, since a new plugin or image upload can quietly push a page back over threshold.

Accessibility checks aligned to WCAG 2.2

Treat AA conformance under WCAG 2.2 as your practical target rather than an afterthought, since it is the level most legal and procurement standards reference and it covers the checks that affect the widest range of visitors. WCAG 2.2 added new success criteria on top of the 2.1 standard, including rules around focus visibility and target sizes that a redesign should build in from the start rather than patch afterwards.

• Test full keyboard navigation through every journey, not just the homepage.
• Confirm focus is always visible on buttons, links and form fields.
• Write meaningful alt text for every image that carries information.
• Check colour contrast against AA thresholds on text and interactive elements.
• Make tap targets large enough for touch and limited-dexterity users.

Automated tools such as the WAVE browser extension catch a useful first layer of issues, but pair them with a manual keyboard pass and, where possible, a screen reader check, since automated scanners miss context that only a human test picks up.

Quality assurance, launch checklist and rollback plan

The gap between a smooth launch and a stressful one is almost always preparation, not luck.

1. Verify everything on staging first: every redirect, the sitemap, robots.txt rules and canonical tags, checked against the live map built during the audit.
2. Test every functional path: forms, booking or payment flows, and any third-party embed, submitted end to end rather than just viewed.
3. Check the deployment itself: DNS propagation, CDN cache invalidation, and a launch time that avoids your highest-traffic hours.
4. Agree rollback triggers in advance: name the metrics that would trigger a rollback (broken checkout, a spike in 404s, a conversion collapse) and name who has the authority to pull it.

Communicate the launch window to everyone involved before it happens, not during it, so a problem gets reported to the right person in minutes rather than hours.

Post-launch monitoring and how to read the data

The first days after launch are the noisiest, so watch closely but judge carefully. Check indexing status, traffic, conversions and server error rates daily for the first 14 to 30 days.

• Compare against your own pre-launch baseline, never against an industry average, since your own historical numbers are the only fair comparison.
• Expect some noise in the first week as search engines re-crawl and users adjust to a new layout.
• Treat a sustained drop, not a single bad day, as the signal to investigate.
• Patch small issues quickly; reserve a full rollback for a broken core function like checkout or form submission.

Practitioner guidance on redesign monitoring recommends holding off on firm conclusions until you have at least 30 days of post-launch data to compare against the pre-launch baseline, since early figures rarely tell the full story.

GridLock Digital: a practical worked example of delivering this checklist

Our own project workflow at GridLock Digital maps directly onto these phases: strategic planning covers the audit and goal-setting stages, hand-built mobile-responsive development covers UX and performance remediation, and ongoing care covers post-launch monitoring. We track each requirement against a test and an acceptance result, so a client can see exactly what was checked before a page went live, and exactly what changed if a metric moves afterwards.

Why most redesigns miss the point

Too many redesign briefs start with "we need a fresh look" instead of "we need more quote requests." That single framing error is why so many relaunches lose conversions even when the new site looks better: nobody defined what better was supposed to mean in revenue terms. The managers who get this right treat sign-off, communication and change control as seriously as the design itself, with named approvers for content, SEO and development, and a clear acceptance criterion attached to every requirement before a single page goes live. Outcomes, not opinions, should decide what ships.

— Dylan

Get the checklist built for you, not just planned

Running through this checklist is one thing, having someone execute it against your specific business is another. We design and build conversion-focused websites for small businesses, hand-coding lightweight, mobile-responsive sites and planning every page around the action you want a visitor to take, whether that is a call, a quote request or a booking. Our Website Redesigns and Conversion-Focused Design services cover exactly the phases above, from audit through launch, and our GridLock Care plans continue the post-launch monitoring once your new site is live.

If you would rather have this checklist executed than ticked off yourself, get in touch through our service plans page to discuss a redesign, a landing page or ongoing site care.

FAQ

What do you need to know before designing a website?

Before any design work starts, you need your current analytics baseline, a content inventory, your SEO rankings and backlinks, and agreement from every decision owner on goals and timeline. Skipping this step is the most common reason redesigns lose traffic or conversions, according to HubSpot's redesign guidance.

What are the five golden rules of a website?

There is no single official "five rules" standard, but most practitioner checklists converge on the same priorities: clear goals and KPIs, strong UX and conversion paths, preserved SEO equity, strong performance against Core Web Vitals, and accessibility aligned to WCAG 2.2. Treat these as the five checks no redesign should skip rather than a fixed rulebook.

Does website redesign affect SEO?

Yes, a redesign can affect SEO, usually through changed URLs, lost metadata or broken internal links rather than the new design itself. Google's own guidance on site moves confirms that Search Console warnings during a migration are normal, and a 1:1 redirect map with active monitoring prevents lasting ranking loss.

How to redesign an existing website?

Work through five phases in order: audit your current analytics and content, define 2 to 4 measurable KPIs, build with conversion-focused UX and preserved SEO signals, test performance and accessibility before launch, then monitor daily for at least 14 to 30 days against your pre-launch baseline. Each phase should produce evidence you can check against the one before it.

Sources

• Web
• What's New in WCAG 2.2 | Web Accessibility Initiative (WAI) | W3C
• Site move with URL changes | Google Search Central

Made with BabyLoveGrowth to grow visibility across Google and AI search