Website redesign guide
Website redesign checklist: protect what works while improving the site.
A redesign changes more than the appearance of a website. It can change URLs, content, navigation, forms, analytics and the signals search engines have already processed.
Use this guide to create a baseline, decide what happens to every existing page, test the new site and monitor the release. The objective is not to freeze the old website; it is to make intentional changes without accidentally discarding useful content or customer journeys.
By Elevéa Cloud · Published
Key decisions before you start.
- Record current URLs, content, enquiries and search baselines before changing the site.
- Map every changed useful URL directly to its closest relevant replacement; do not send unrelated pages to the homepage.
- Test the new site before launch, then monitor redirects, indexing, forms and analytics after release.
Updated by Elevéa Cloud.
Plan the redesign as four connected phases.
| Phase | Work to complete | Evidence to keep |
|---|---|---|
| Before design | Crawl or export current URLs; record content, search, enquiry and performance baselines; identify owners and constraints. | A complete inventory and an agreed decision process. |
| During content and design | Assign keep, improve, merge or remove decisions; map the new structure; prototype important customer journeys. | Approved page purposes, content owners and tested key flows. |
| Before launch | Finish the redirect map; test forms, accessibility, analytics, canonicals, structured data, sitemap and production settings. | A signed-off release checklist, redirect file and rollback responsibility. |
| After launch | Crawl old and new URLs; monitor errors, indexing, enquiries and analytics; compare equal complete reporting periods. | Recorded issues, owners and evidence-based follow-up changes. |
Inventory the current website before replacing it.
Export or crawl public HTML pages, PDFs and other useful indexed resources. Record each URL’s title, canonical, status, indexability, internal links and content purpose. Add search and analytics evidence where available, while recognising that measurement tools may be incomplete.
Do not judge a page only by sessions. A low-volume page may answer an important buyer question, support a sales conversation, earn relevant links or be required for customers and compliance.
Give every page an explicit decision.
Mark each page keep, improve, merge or remove, with an owner and reason. Define the audience, useful information and next action for every planned replacement. This creates an accountable content scope instead of allowing pages to disappear during visual design.
Keep facts, service explanations and evidence in visible page content. Search and AI systems need accessible source material; decorative images or unsupported schema cannot replace it.
Build a one-to-one redirect map.
Keep the existing URL when the subject and purpose remain substantially the same. When a useful URL must change, redirect it directly to the closest relevant new page. Avoid redirect chains and sending unrelated removed pages to the homepage. A genuine 404 or 410 is clearer when no replacement exists.
Redirect worksheet columns.
Old URL · current status · evidence · keep/merge/remove decision · new URL · redirect status · owner · pre-launch test · post-launch test · notes.
Update internal links, canonical URLs and sitemap entries to use final destinations rather than relying on redirects. Review external campaigns, profiles or important links that your team controls.
Preserve measurement definitions.
Record search queries, landing pages, clicks, impressions and agreed enquiry actions before launch. Document how forms, calls or other conversions are counted. Preserve consent requirements and avoid treating a changed analytics configuration as business growth.
Compare equal complete periods after release and annotate the launch date. Search demand, seasonality, campaigns and other business changes can affect results independently of the redesign.
Design around real customer tasks.
Test whether a visitor can identify the right service, understand the evidence and complete the next step on a phone and desktop. Include navigation, error, empty, loading and confirmation states where relevant.
Review keyboard access, visible focus, labels, headings, contrast, alternative text and responsive reflow. Automated checks can help find issues but do not establish complete accessibility.
Pre-launch website redesign checklist.
- Customer journeys: test navigation, search where present, forms, confirmation, email delivery, phone and contact links.
- Content: verify names, services, locations, policies, evidence, titles, headings and social sharing information.
- Accessibility: test keyboard use, focus, labels, alternatives, contrast, zoom and responsive reflow on representative templates.
- Technical SEO: check status codes, canonicals, robots rules, indexability, structured data, sitemap and internal links.
- Migration: test every redirect mapping and confirm there are no loops, chains or accidental broad homepage redirects.
- Measurement: verify consent behaviour, analytics loading and agreed enquiry events without exposing sensitive form data.
- Operations: document domain, hosting, backups, monitoring, account ownership, launch owner and rollback decision.
What should you monitor after launch?
Crawl the old URL list against production and record its final response. Monitor 404s, server errors, redirect loops, blocked resources and forms. Inspect representative priority URLs in Search Console, resubmit the canonical sitemap and confirm that important pages can be fetched.
Review enquiries and search data regularly, but do not react to one partial day. Investigate page-level changes and confirm measurement first. Keep redirect rules, the original baseline and a log of post-launch changes so later effects can be interpreted.
Download the website redesign checklist.
The text template includes baseline, content, redirect, pre-launch, launch and post-launch checks, plus suggested columns for a redirect worksheet. Copy it into your own project system and assign an owner to each item.
Download the checklistElevéa Cloud provides website design and development services for new sites and planned redesigns. Use our development-company selection guide to compare scope, evidence, ownership and support.
Direct answers
Website redesign and migration questions.
How do you redesign a website without losing SEO?
Keep useful URLs where possible, inventory every current page, map each changed valuable URL to its closest relevant replacement, preserve important content and internal links, and test indexing signals before launch. Monitor crawling and search data afterward. Rankings still cannot be guaranteed.
When should a website URL change during a redesign?
Change a URL only when the new structure or page purpose makes the change worthwhile. If the topic remains substantially the same, keeping the URL reduces migration work. Every changed useful URL needs a direct redirect to the closest replacement.
What should be tested before launching a redesigned website?
Test navigation, forms, contact routes, responsive layouts, keyboard access, labels, analytics, redirects, canonical URLs, structured data, robots rules, sitemap output and important production journeys.
How long should website redirects stay in place?
Google recommends keeping redirects for as long as possible and generally at least one year for site moves. Users, external links and other search systems may rely on them for longer, so retain useful redirects when practical.
Sources and scope.
This checklist is a planning aid, not a guarantee of rankings, traffic, accessibility, security or a risk-free migration. Adapt it to the site and use specialist review where the consequences require it.
- Google Search Central: site moves with URL changes
- Google Search Central: redirects and Google Search
- W3C Web Content Accessibility Guidelines 2.2
- web.dev: Web Vitals
Sources reviewed 17 November 2026.