A website redesign is one of the few marketing projects that can move results in either direction. Done well, it gives buyers a clearer story, faster pages and easier paths to contact you. Done carelessly, it can wipe out search traffic that took years to earn, break forms nobody tested and leave the team with a site that looks new but works worse.
The difference is rarely the design itself. It is the planning before design starts and the checks before and after launch. This website redesign checklist walks through the full process step by step, from setting goals to monitoring results after go-live, with a focus on protecting what already works.
Signs your website needs a redesign
Not every problem needs a full rebuild. A redesign is usually worth it when several of these are true at once:
- Your positioning has changed. The site describes services, audiences or a brand you have moved away from.
- Buyers struggle to find answers. Navigation has grown page by page, and important information is buried.
- The site is slow or fragile. Performance, mobile and accessibility issues are built into the templates rather than limited to a few pages.
- Your team cannot update it. Simple changes need a developer, so content goes stale.
- Conversion paths are unclear. Visitors arrive but have no obvious next step, or forms and calls to action are inconsistent.
- The technology is holding you back. The CMS, plugins or hosting create security, integration or maintenance problems.
If only one or two pages are underperforming, start with a targeted refresh. If the problems are structural, plan a redesign and use the checklist below.
Step 1: Define goals, scope and owners
Start by writing down what the redesign is meant to achieve in business terms. "A modern look" is not a goal. Better examples include more qualified demo requests, clearer service pages for a new market, fewer support questions, or a site your marketing team can update without help.
For each goal, agree on:
- A measurable KPI, such as form submissions, demo bookings, organic sessions to service pages or conversion rate on key landing pages.
- The scope: which sections are being redesigned, which are being rebuilt and which stay as they are.
- A decision-maker for design, content, technology and SEO, so approvals do not stall.
- Constraints: budget, deadlines, brand guidelines, legal or compliance requirements, and systems the site must connect to.
Writing this down early gives you something to test every later decision against.
Step 2: Benchmark current performance
You cannot judge a redesign without a clear "before" picture. Before anything changes, export and save:
- Analytics data for at least the last twelve months: sessions, users, top landing pages, conversions and traffic sources.
- Google Search Console data: clicks, impressions, average position and the queries and pages that earn them.
- A full crawl of the current site with every URL, status code, title, meta description, canonical and internal link count.
- Core Web Vitals and page speed results for your main templates.
- A list of pages with backlinks from external sites.
Save the crawl and exports somewhere permanent. After launch, they are how you spot which pages lost traffic and why.
Step 3: Audit content and decide what stays
A redesign is a good moment to clean up content, but it is also where most SEO losses begin. Build a content inventory, one row per URL, and decide what happens to each page.
| Decision | When to use it | What to do |
|---|---|---|
| Keep | The page ranks, converts or earns links, and the content is still accurate | Move it across with its URL and core content intact, refresh where needed |
| Improve | The topic matters but the page is thin, outdated or unclear | Rewrite and expand it, keep the URL if possible |
| Merge | Several pages cover the same topic and compete with each other | Combine them into one stronger page and 301 redirect the others to it |
| Remove | The page has no traffic, no links and no business purpose | Retire it, redirect it if a close equivalent exists, otherwise let it return 404 or 410 |
Pay special attention to pages that bring organic traffic or leads. Shortening them, removing sections or rewriting them around a different keyword is a common reason for ranking drops after launch.
Step 4: Plan site structure and the redirect map
With the inventory done, design the new information architecture: the main navigation, the sitemap of pages, and how they link to each other. Organise it around how buyers look for information, such as by service, industry or problem, rather than around your internal org chart.
Then build the redirect map. For every existing URL that will change or be removed:
- List the old URL.
- Choose the single most relevant new URL.
- Set a 301 (permanent) redirect from old to new.
- Avoid redirect chains, where one redirect leads to another, and loops.
- Point anything with no sensible equivalent to the closest parent page only if it genuinely answers the same need; otherwise let it return a 404.
Do not send every old URL to the homepage. Search engines tend to treat that like a missing page, and visitors arriving from old links will not find what they expected.
Step 5: Set design, content and conversion requirements
Before wireframes, agree on what each key page needs to do. For service and landing pages, that usually means a clear headline, proof of expertise, answers to common objections and one obvious next step.
Useful requirements to define at this stage:
- Page templates you need, such as home, service, case study, article, contact and landing pages.
- Messaging and tone of voice, so new copy is consistent across the site. This is where content and brand work pays off.
- Calls to action for each template, and where forms send their data.
- Trust elements you can genuinely support, such as process explanations, team information or real client feedback you have permission to use.
- Accessibility standards, such as WCAG 2.2 AA, so contrast, keyboard navigation, form labels and alt text are designed in from the start.
Write or rewrite content alongside design, not after it. Designs built around placeholder text often break when real copy arrives.
Step 6: Choose the technology and plan integrations
Pick the CMS, framework and hosting based on who will maintain the site and what it needs to connect to, not on what is fashionable. Questions worth answering:
- Can your marketing team create and edit pages without a developer?
- Does it produce fast, crawlable HTML that search engines can render?
- How are titles, meta descriptions, canonicals, redirects, structured data and XML sitemaps managed?
- Which systems must it connect to: CRM, marketing automation, analytics, chat, booking or payment tools?
- Who handles updates, security patches, backups and uptime?
If the redesign involves custom functionality such as calculators, portals or internal tools, scope it as a separate piece of software development with its own requirements and testing.
Step 7: Build with SEO and performance in mind
During development, treat SEO and performance as requirements, not finishing touches. Check that the build:
- Uses one H1 per page and a logical H2 and H3 structure.
- Carries over or improves titles, meta descriptions and on-page content for pages you decided to keep.
- Sets self-referencing canonical tags and correct structured data, such as Organization, Article or Breadcrumb markup.
- Uses clean internal links that point directly to final URLs, not to redirects.
- Optimises images with modern formats, correct dimensions, lazy loading below the fold and descriptive alt text.
- Meets Core Web Vitals targets on mobile for the main templates.
- Works on the devices and browsers your audience actually uses.
Keep the staging site out of search results while you build, using password protection or noindex, and make a note to remove that protection at launch.
Step 8: Test everything on staging
Quality assurance should be a structured checklist, not one final look through the pages. Before launch, test:
- SEO: crawl staging and compare it with your redirect map and content inventory. Check status codes, titles, canonicals, robots directives, structured data and the XML sitemap. Our technical SEO audit checklist covers these checks in more detail.
- Redirects: test a sample of old URLs, including every high-traffic and backlinked page, to confirm each one lands on the right new page in a single hop.
- Forms and integrations: submit every form and confirm the data reaches the right inbox or CRM, with confirmation messages and emails working.
- Analytics: confirm page views, events and conversions fire correctly and match your KPI definitions.
- Accessibility: test keyboard navigation, focus states, colour contrast, form labels and screen-reader output on key templates.
- Performance: run speed tests on the main templates and fix anything heavy before launch.
- Content: proofread copy, check links, contact details, legal pages and images.
Have the decision-makers from Step 1 review staging against the goals you agreed, not just against personal taste.
Step 9: Launch with a plan
Pick a launch window with low traffic and the right people available. On the day:
- Back up the old site and database so you can roll back if needed.
- Deploy the new site and remove staging restrictions such as password protection or noindex.
- Check that robots.txt allows crawling of the pages you want indexed.
- Activate the redirect map and spot-check old URLs again on the live domain.
- Crawl the live site to catch broken links, unexpected redirects and missing tags.
- Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools.
- Test every form and conversion event on production.
- Add an annotation in analytics marking the launch date.
Step 10: Monitor and improve after launch
Launch is the start of the evidence, not the end of the project. For the first few weeks, check regularly:
- Search Console for crawl errors, indexing issues and changes in clicks and impressions on important pages.
- 404 reports and server logs for old URLs that were missed in the redirect map.
- Rankings and organic traffic for the pages you identified as most valuable in Step 2.
- Conversion rates, form submissions and lead quality against your baseline.
- Real user behaviour, such as where visitors drop off on key pages.
Some movement in rankings is normal while search engines recrawl the site. Persistent drops on specific pages usually point to a fixable cause, such as a missing redirect, removed content or a changed title. Keep redirects in place for the long term, and treat the new site as something to improve continuously rather than leave untouched until the next redesign.
Website redesign checklist summary
Use this condensed version to track the project:
- Goals, KPIs, scope and owners agreed
- Analytics, Search Console, crawl and backlink baseline saved
- Content inventory complete with keep, improve, merge or remove decisions
- New site structure and navigation approved
- Redirect map covering every changed URL
- Templates, messaging, calls to action and accessibility standards defined
- CMS, hosting and integrations chosen
- SEO, structured data and performance built in
- Staging QA passed for SEO, redirects, forms, analytics, accessibility and content
- Launch-day plan with backup and rollback ready
- Post-launch monitoring scheduled
Getting help with a website redesign
A redesign touches design, content, development and SEO at once, and problems usually appear where those pieces meet. If you want a team that plans the structure, protects your existing search visibility and builds a site your team can own, see our web development and SEO services. If you are comparing partners, our guide on how to choose an SEO agency lists the questions worth asking.
When you are ready to talk through your redesign, contact us with your goals and current site, and we will suggest a practical plan.