A website redesign checklist is a step-by-step plan that takes a rebuild from business goals to a stable launch: audit what exists, define goals and scope, map content and URLs, design and build with performance and accessibility in mind, test thoroughly, launch with redirects in place and monitor search, speed and leads for weeks afterwards.
Redesigns fail less often because of design and more often because of planning: missing redirects, lost content, broken forms and tracking that stops on launch day. This checklist groups the work into three phases, plan, build and launch, with the checks that protect traffic, leads and budget.
Key takeaways
- Start with the business problem, not the visual style. Decide what the new site must achieve and how you will measure it.
- Audit before you design. Know which pages earn traffic, links and leads, so you do not throw them away.
- Build a URL and redirect map early. Every old URL that matters needs a destination on the new site.
- Treat performance, accessibility and forms as launch criteria, not post-launch fixes.
- Plan the first 30 days after launch: monitoring, fixes and a review against the goals you set.
What does recent data say about the sites most redesigns replace?
Many existing sites have real weaknesses a redesign can fix, and a careless redesign can make them worse. The HTTP Archive Web Almanac 2025 Performance chapter reports that only 48% of sites had good Core Web Vitals on mobile in July 2025, up from 44% in 2024, against 56% on desktop. Home pages did worse than other pages: 45% passed on mobile compared with 56% of secondary pages.
Accessibility is similarly weak. The WebAIM Million 2025 report found detectable WCAG failures on 94.8% of the top one million home pages, with low-contrast text on 79.1% and missing image alt text on 55.5%.
How current websites perform (2025 research)
These numbers make a practical point: a redesign is the cheapest moment to fix speed and accessibility, because you are rebuilding templates anyway. Retrofitting later costs more.
Phase 1: What should you do before any design work starts?
1. Write down the business problem
What: one paragraph on why the site is being rebuilt. Why: “it looks dated” is not a goal, and vague goals make every design debate subjective. How: name the problem, such as low enquiry quality, a new service line, a rebrand or a platform that is hard to maintain.
2. Set measurable goals and a baseline
What: three to five measures, such as qualified enquiries, organic clicks to service pages and mobile Core Web Vitals. Why: without a baseline you cannot tell if the redesign worked. How: export the last 12 months from analytics, Search Console and the CRM before anything changes.
3. Audit current content and performance
What: a crawl of every URL with traffic, backlinks, conversions and index status. Why: some old pages quietly earn most of your leads or links. How: combine a crawler such as Screaming Frog with Search Console and analytics data, then mark each page keep, merge, rewrite or remove. The SEO audit checklist lists what to capture.
4. Interview buyers and sales
What: short conversations with recent customers, lost prospects and the sales team. Why: they know which questions the current site fails to answer. How: ask what they looked for, what was missing and what nearly stopped them enquiring.
5. Agree scope, budget, owners and timeline
What: a written scope covering pages, templates, integrations and content. Why: scope creep is the most common reason redesigns overrun. How: list what is in and out, name one decision-maker, and include time for content writing, which is usually underestimated.
6. Choose the platform and hosting deliberately
What: a decision on CMS, theme approach and hosting. Why: these choices decide speed, maintenance cost and how easily editors can work. How: compare options against your goals; if you choose WordPress, read our WordPress SEO guide on themes, plugins and builders first.
| Redesign type | What changes | Main risk | Must-have safeguard |
|---|---|---|---|
| Visual refresh | Design and templates, same URLs | Slower templates, lost headings | Performance and heading checks on staging |
| Content and structure rebuild | Navigation, page set, some URLs | Deleted pages that earned traffic | Content audit and redirect map |
| Platform migration | CMS, templates, often URLs | Broken redirects, missing metadata | Full URL mapping and crawl comparison |
| Domain change | Every URL | Temporary loss of rankings | Google site-move process and long-term redirects |
Phase 2: What should you check while designing and building?
7. Plan the information architecture from buyer tasks
What: a sitemap and navigation based on what buyers need to find. Why: navigation that mirrors your org chart confuses visitors. How: test proposed menus with a few target buyers using simple tasks. Our site architecture guide explains how.
8. Build the URL and redirect map
What: a spreadsheet mapping every old URL that matters to its new destination. Why: missing redirects are the single biggest cause of traffic loss after a redesign. How: use one-to-one 301 redirects to the closest equivalent page, avoid sending everything to the home page and avoid redirect chains. Follow Google’s guidance on site moves with URL changes.
9. Write content before final design
What: real copy for key pages before designs are signed off. Why: designs built around placeholder text often break when real content arrives. How: write service pages and the home page first, following the structure in our service page copywriting guide.
10. Set a performance budget for templates
What: limits on page weight, scripts, fonts and image sizes per template. Why: speed is easier to protect than to recover. How: agree targets for LCP, INP and CLS, size images properly and test each template on a mid-range phone. The Core Web Vitals guide sets out a fix order.
11. Build accessibility into components
What: accessible colours, focus states, headings, labels and alt text in the design system. Why: fixing each page later is slow and expensive. How: check contrast during design, label every form field and test menus with a keyboard. Use the WCAG 2.2 quick reference as the checklist.
12. Carry over SEO metadata and structured data
What: titles, meta descriptions, canonicals, structured data and indexing rules for every kept page. Why: these are often lost when content is rebuilt. How: export them from the old site and import or re-enter them before launch.
13. Rebuild forms, tracking and CRM connections
What: every form, analytics tag, conversion event and CRM integration on the new site. Why: tracking and lead delivery are the most common silent failures at launch. How: list every tag and integration on the old site, recreate them in staging and test with real submissions. See our form optimisation guide.
14. Keep staging private
What: a staging site behind a password or noindex. Why: an indexed staging site creates duplicate content and leaks unfinished pages. How: block staging, and remember to remove the block on the live site at launch.
Four gates before a redesign goes live
Every valuable page has a home or redirect.
Key templates pass speed and accessibility checks.
Forms reach the CRM and inbox; tracking fires.
Metadata, sitemap, robots and canonicals are correct.
Phase 3: How do you launch and protect performance afterwards?
15. Run a full pre-launch test
What: a crawl of staging plus manual tests on desktop and mobile. Why: broken links, missing pages and layout bugs are cheaper to fix before launch. How: crawl staging, compare against the old URL list, test top templates on real devices and submit every form.
16. Back up the old site and plan a rollback
What: a full backup of files and database, plus a written rollback step. Why: if launch goes badly, you need a fast way back. How: keep the backup off the server and agree who decides on a rollback and when.
17. Launch at a quiet time with the team available
What: a launch slot with developers and marketers on hand. Why: problems found on a Friday evening wait until Monday. How: choose a low-traffic weekday window and avoid launching during campaigns or peak season.
18. Check the essentials in the first hour
What: a short launch checklist run immediately. Why: some errors, such as noindex left on or redirects not live, can hurt quickly. How: confirm search visibility is on, redirects work for a sample of old URLs, the sitemap lists new URLs, HTTPS works and forms submit.
19. Submit the sitemap and monitor Search Console
What: submit the new XML sitemap and watch coverage, crawl errors and Core Web Vitals. Why: Search Console shows indexing problems before they become traffic drops. How: check daily for the first two weeks, then weekly. Our website migration SEO guide explains what normal fluctuation looks like.
20. Review results against the goals after 30 and 90 days
What: a structured review against the baseline from step 2. Why: a redesign is an investment and should be judged on outcomes, not opinions. How: compare qualified enquiries, organic clicks, speed and accessibility with the baseline, list fixes and decide the next round of improvements.
What are the most common redesign mistakes?
- Deleting old pages that earned traffic or links without redirecting them.
- Launching with “discourage search engines” or noindex still switched on.
- Forgetting tracking tags, conversion events or CRM integrations.
- Choosing a heavy theme or builder that slows every page.
- Writing content last, so it is rushed or copied from the old site without improvement.
- Judging success by how the site looks instead of the goals set at the start.
Some ranking movement after a large redesign or migration is normal while search engines recrawl. A sustained drop usually points to redirects, lost content or indexing settings, which the checks above are designed to catch.
Who should be involved in a redesign, and what does each person own?
Redesigns stall when decisions have no owner. Name one person for each area before work starts:
| Role | Owns | Signs off |
|---|---|---|
| Project owner | Goals, scope, budget, timeline | Final launch decision |
| Marketing or SEO lead | Content audit, redirect map, metadata, tracking | Search and analytics readiness |
| Content owner | Copy for key pages, tone, accuracy of claims | Content readiness |
| Designer | Templates, design system, accessibility of components | Design and accessibility checks |
| Developer | Build, performance budget, integrations, staging | Technical readiness and rollback plan |
| Sales representative | Buyer questions, objections, lead handoff needs | Forms and CRM routing |
In a small business one person may hold several roles. That is fine, as long as each area has someone who will say “this is ready” or “this is not ready”.
What should the launch-day checklist include?
Keep a short, printed checklist for the launch itself, separate from the full project plan:
- Fresh backup taken and stored off the server.
- Search engine visibility switched on and staging noindex removed.
- HTTPS working on all versions of the domain; http and www variants redirect once.
- A sample of 20 to 50 old URLs tested, including top traffic pages, all returning 301 to the right page.
- XML sitemap live, listing new URLs only, and submitted in Search Console.
- robots.txt correct and not blocking CSS, JavaScript or important sections.
- Every form submitted once; entries checked in the CRM, team inbox and auto-reply.
- Analytics and conversion tags firing on the live domain.
- Cache cleared and key templates checked on a phone.
Assign each line to a named person and tick it off in a shared document, so nothing depends on memory. If any item fails, decide in advance whether it blocks the launch or can be fixed within the first day. Missing redirects, broken forms and an indexing block should always stop a launch; a minor styling issue on one page usually should not. Keep the old site’s backup and redirect map open during launch so you can compare quickly.
How should you budget time and money for a redesign?
Most redesign budgets focus on design and development and underestimate everything else. A realistic plan sets aside time and money for:
- Discovery and audit: content inventory, analytics review, buyer interviews.
- Content: writing, editing and approving copy for key pages, which often takes longer than the build.
- Design and build: templates, components, integrations and staging.
- Migration: redirect mapping, metadata transfer and data imports.
- Testing: device testing, accessibility checks, form and tracking tests.
- Post-launch support: at least a few weeks of fixes and monitoring.
Keep a contingency for scope that only becomes clear once real content arrives. It is better to launch a smaller set of excellent pages and add more later than to launch everything half-finished.
Which related guides should you read next?
- Website migration SEO goes deeper on redirects and domain moves.
- B2B website strategy defines what the site must do for buyers.
- Website UX and UI design covers task-led design and testing.
- WordPress SEO helps if you are rebuilding on WordPress.
- Website development explains maintainable builds and release processes.
Frequently asked questions
How long does a website redesign take?
It depends on scope. A visual refresh of a small site may take a few weeks, while a content and platform rebuild for a larger site often takes several months, with content writing usually the longest part.
Will a redesign hurt my SEO?
It can if pages are removed without redirects or metadata is lost. With a content audit, a redirect map and post-launch monitoring, most sites keep or improve their visibility.
Should I change my URLs during a redesign?
Only when there is a clear benefit, such as fixing a confusing structure. Every changed URL needs a 301 redirect, so keep existing URLs wherever they still make sense.
What should I measure after launch?
Qualified enquiries, organic clicks to key pages, indexed pages, Core Web Vitals and form delivery, compared with the baseline you recorded before the redesign.
Do I need a backup if my host keeps backups?
Yes. Keep your own full backup off the server before launch, so you can restore the old site quickly if needed.
Who should own the redirect map?
The SEO or marketing lead should own it, with the developer implementing it. One person should check that every important old URL has a tested destination before launch.
Sources and further reading
- HTTP Archive Web Almanac 2025: Performance chapter (July 2025 data).
- WebAIM Million 2025
- Google Search Central: site moves with URL changes
- Google Search Central: Core Web Vitals and Search
- W3C: WCAG 2.2 quick reference
- The checklist structure and launch gates are Bargaon’s editorial guidance, not research data.
Planning a redesign and want to keep your traffic and leads? Bargaon’s website development service plans, builds and launches redesigns with content audits, redirects, speed and CRM tracking covered.