A website redesign checklist should help you decide what to keep, what to change, and what must work on launch day. If you run a small B2B firm, the goal is to help the right buyer understand your offer and contact you. That buyer might arrive from Google Search, a referral, an industry article, or an AI answer. Start with the pages and customer paths you already have. This checklist gives your team a way to scope the redesign and test the result.

Phase 1: Baseline and Scope Before You Redesign

Before a single mockup, capture what the current site actually does. These records give your team a baseline for later decisions.

Export your baseline. Pull enough analytics to cover a complete business cycle, including seasonal changes: traffic by landing page, conversion events, form submissions, phone and email clicks, and top entry pages. Export Search Console queries and the pages they point to. Skip this and you lose the only honest before-and-after comparison you will ever have.

Crawl and inventory indexable URLs. You need a plain list of every URL that returns content, plus which ones are linked from navigation, which are orphaned, and which have no inbound internal links at all.

Identify your highest-value pages. Two lists matter: pages with the most external links, and pages that convert. They are often not the same pages, and both deserve protection.

Map forms, CRM, and integrations. Every form has a destination. Document where submissions go, which autoresponders fire, which CRM records are created, and who gets notified. A working layout cannot tell you whether a lead reached the right person.

Name content owners and approvers. For each major section, write down who writes, who reviews, and who has final say. Unowned content leaves a key part of the project without a decision-maker.

Define measurable acceptance criteria. "Modern look" is not a criterion. "Homepage communicates the primary offer above the fold, loads without layout shift, and routes visitors to one of three next steps" is. Google's own SEO Starter Guide notes there is no guarantee any particular site will be added to Google's index, and that changes can take weeks or months to show up — so build acceptance criteria around things you control: clarity, speed, structure, accessibility, and lead flow.

Phase 2: Page Inventory and Information Architecture

Now make a decision about each page. A new layout cannot tell you which old content deserves to survive.

Decision When to use it What to document
Keep Page performs, content is current Owner, review date
Improve Good topic, weak structure or copy Specific edits, target reader
Consolidate Two or more pages compete for the same intent Canonical destination, merge plan
Retire Outdated offer, no traffic, no links Removal date, redirect target

Then build the target sitemap. Count templates, not just pages: a service page template, a case-study template, a resource article template, a contact template. Template count is one major driver of design and build effort, so include it alongside page count in your scope conversation.

For each key template, define three things: the audience, the job they are trying to do, and the single next step you want them to take. One conversion objective per template keeps design decisions honest. If a page is meant to book a call, the layout should not compete with a newsletter signup and three unrelated downloads.

Navigation deserves its own pass. Decide what appears in the primary nav, what lives in a footer, how site search behaves, and which pages cross-link to which. Cross-links between related service and proof pages do more for buyer comprehension than another banner.

Phase 3: Content, UX and Accessibility Readiness

Content is the largest hidden cost in most redesigns. Treat it as a workstream with dates, not a task that happens after design.

Build a content inventory with migration status. For every page: keep as-is, lightly edit, rewrite, or write new. Assign an owner and a due date. Real copy, not lorem ipsum, should be in the design before signoff — placeholder text hides length problems that reappear during build.

Design with realistic content and edge cases. Long headlines, missing images, wide tables, and a case study with no approved metrics all test the layout. Our SEO-friendly website design guide covers the search decisions to make at this stage. If the design only works with ideal content, it will break in production.

Structure pages logically. The W3C's page structure guidance recommends adding headings and nesting them logically to label sections according to their relationships and importance, and marking up page regions so users can navigate efficiently. This helps screen reader and keyboard users, and it also gives search engines cleaner signals about what each section contains.

Treat accessibility review as acceptance criteria. W3C accessibility guidance is a useful reference for a review pass: color contrast, focus states, form labels, error messaging, keyboard operability. No one can promise compliance on your behalf, but you can require evidence that the review happened.

Prototype and test before build. Show a clickable prototype to people who resemble your buyers. Watch where they hesitate, not just where they click, and record what should change before development begins.

Inventory the design system. Buttons, form fields, cards, spacing, type scale. A short component list makes developer handoff faster and keeps future pages consistent.

Timeline and Dependencies: Set a Date You Can Explain

How long does a website redesign take? There isn't a useful universal number. A five-page site with approved copy, one page template, and no integrations is a different project from a site with hundreds of URLs, several languages, a new CMS, and a lead-routing workflow. Ask for a timeline built from deliverables and approval dates, rather than accepting a launch date on its own.

Start with the page inventory and count the distinct templates. Mark which pages need new copy or images, which need review by product or legal teams, and which depend on data or integrations. Then map the work in order: discovery and decisions, content and design, development, migration, testing, and launch approval. Some tasks can overlap, but a page cannot receive a meaningful final review before its real content exists. A new form cannot pass QA before someone has decided where the inquiry should go.

Give each phase an owner, a deliverable, and a decision deadline. Keep a short buffer for issues found during testing; record what would delay launch and who can approve a change in scope. If a vendor proposes a precise duration without checking your content, URL inventory, stakeholders, and integrations, ask what assumptions sit behind it. The schedule should tell your team when it needs to act, not just when the supplier plans to build.

Phase 4: Build, QA and Launch Ownership

Launch is a controlled migration, not a one-time event. Someone must own it by name.

  • Staging and rollback. A staging environment that mirrors production, plus a documented rollback plan and a recent backup.
  • Critical user flows. Test signup, demo request, contact, checkout, and any gated download end to end — not just that the page loads.
  • Interactive components. Navigation menus, accordions, tabs, filters, and modals on desktop and mobile.
  • Responsive breakpoints. Check the layouts you actually designed for, plus one you did not.
  • Scripts and tracking. Reinstall and verify analytics, tag manager, chat, and heatmap tools. Confirm events fire.
  • Integration map validation. Submit a test lead and follow it all the way to the CRM record and notification email.
  • Named go-live owner and approval authority. One person says go, one person can say stop.
  • First 30 days. A triage cadence: daily error and form-deliverability checks in week one, a content refresh queue, and a stakeholder readout at day 30.

If URLs are changing, that work has its own discipline — preparation, thorough testing, and a URL mapping from old to new, as Google describes in its guidance on moving a site. We cover the mechanics in our website redesign SEO checklist, and it is worth reading alongside this one. For teams planning the build itself, our website design and website design and SEO pages describe how planning, design, development, testing, and launch support fit together.

A Hypothetical Worked Example

Imagine a 12-person industrial equipment supplier with 140 published pages. Baseline export shows 60 pages with zero organic entrances in a year and 18 pages producing most form fills. Page inventory decisions: keep 30, improve 45, consolidate 50 into 22, retire 15. Template count drops from nine to five. Content owners are named for each of the five templates. Accessibility review flags contrast and form-label issues. At launch, one test lead is submitted and traced to the CRM. At day 30, the team reviews error logs, form deliverability, and a queue of ten pages flagged for copy refresh. No rankings are promised at any point — the measurable goals are clarity, lead routing accuracy, and a shorter path from landing page to inquiry.

FAQ

How long does a website redesign take?

It depends on the existing page inventory, the number of distinct templates, whether copy and images are ready, required integrations, and how quickly stakeholders approve decisions. Request a phased schedule with named owners and review deadlines. Treat the date as a working plan that can change when scope or approvals change, not as a universal industry average.

How much will it cost to redesign a website in 2026?

Start with the scope, then ask for a quote. A site with a few existing templates and approved copy takes different work from one that also needs a CMS change, new content, integrations, and accessibility fixes. Give vendors the same page inventory, template list, and test requirements. You can compare their prices only after those items are clear. For a fuller way to read a proposal, see our website design cost guide.

How can I redesign my existing website?

First, save your current URLs, content, analytics, and inquiry data. Decide which pages stay, change, merge, or go. Work out the new navigation and page templates with real copy before you approve layouts. Then build in staging and test the paths a customer uses, including the form and its destination. Name one person who can approve the launch. If URLs change, add a separate migration plan; the redesign SEO checklist covers that work.

What should be on a website redesign checklist before launch?

Before launch, verify the buyer path, lead routing, tracking, and rollback plan. Can a buyer find the right service and contact you on a phone? Does a test inquiry reach the right inbox or CRM record? Do the analytics events record the action? Check navigation, keyboard use, form labels, tracking, and backups. Open important old URLs and confirm where they lead. Keep a short list of who owns each fix and who decides whether the site can go live.

Who should own go-live approval?

Choose one decision-maker. Design, content, development, and QA owners can each sign off on their work, but someone needs the full picture and authority to delay launch. Record that name and the unresolved issues before you set the date.

If you have a page inventory and a target launch window, share them with us. We can help define the website work that needs to happen before a date is credible.

Sources