A useful website redesign checklist starts before the first new layout: record the pages, search traffic and customer actions that already matter. Then plan the content, URL changes, conversion journey and launch checks around protecting that value. A redesign should make the business easier to understand and the website easier to use, while preserving useful existing material. Visual improvement alone does not prove the new site works. This guide takes you through inventory, redirects, content decisions, mobile testing and monitoring, with an example of how a changed service URL should be handled. It is suitable for a marketing site, service business or ecommerce migration.
Capture the baseline before the design work starts
Export existing URLs from your sitemap and crawl data, and review which pages earn enquiries or useful search visits. Keep a record of titles, headings, content, incoming links and important documents. A page with modest traffic may still answer a valuable buyer question.
Write down what is broken in the current journey. If visitors abandon a form because its fields are unclear, a new visual style will not solve that on its own. Prioritise specific problems and acceptance criteria. Use our website development quote guide to make sure the redesign estimate includes migration work.
Map URLs and content rather than redirecting everything home
Keep a URL if the page still serves the same purpose and there is no reason to change it. When a URL changes permanently, map it to the closest useful replacement. Google's site-move guidance recommends planning and testing these changes.
For example, if an old /web-design page becomes a more complete /services/website-development page, a direct permanent redirect can preserve the route for visitors. An unrelated retired campaign should not automatically land on the homepage. Update internal links to the final destination, and let genuinely missing content return an honest 404 when no suitable replacement exists.
Test the journeys that produce business value
List the actions the website is expected to support: phone calls, emails, forms, bookings, checkout, account access or document downloads. Test them on touch devices and with keyboard navigation. Verify error messages and successful completion, not just the appearance of the initial screen.
For a lead form, submit realistic data and confirm that it reaches the right inbox or record system. Then test invalid input, duplicate submission and a slow connection. For ecommerce, include out-of-stock variants and payment failures. The ecommerce SEO checklist adds product and collection checks when the project includes a store.
Launch with a rollback plan and monitor what changed
Make sure staging restrictions do not accidentally block production pages, while keeping private staging environments protected. Check canonicals, sitemap URLs, robots behaviour and page responses on the actual host. Record a backup and a practical rollback process before switching traffic.
After launch, compare conversion reporting, server errors and search discovery with the baseline. Short-term changes need investigation rather than an immediate assumption that the redesign failed. Prioritise broken journeys first. Our website development team can help coordinate the build, migration and post-launch fixes within one agreed scope.
A practical comparison
| Phase | Evidence to collect | Owner to name |
|---|---|---|
| Before design | URL and conversion baseline | Marketing and site owner |
| Before launch | Redirect map and tested journeys | Developer and reviewer |
| At launch | Correct metadata and production responses | Release owner |
| After launch | Errors, enquiries and search changes | Operating team |
Common mistakes and your next steps
Avoid these mistakes
- Deleting useful content because it does not fit a new layout.
- Redirecting every old URL to the homepage.
- Assuming an analytics script proves conversion events are correct.
Your action checklist
- Save URLs, content and performance baselines.
- Approve a direct old-to-new URL map.
- Test mobile and keyboard journeys.
- Validate metadata, responses and sitemap URLs.
- Check enquiries and errors after launch.
Frequently asked questions
Should all URLs change during a redesign?
No. Keep useful stable URLs when possible. Change them only for a clear structural reason and map permanent replacements carefully.
Can a redesign affect rankings?
Yes. Content, URLs, navigation and technical delivery can change how pages are understood. A careful migration reduces avoidable disruption but cannot guarantee rankings.
What should be checked first after launch?
Verify the homepage, important landing pages and customer actions work, then investigate indexing, analytics and less critical presentation issues.
What to do next
A redesign succeeds when the new experience works and the existing value remains discoverable. Treat migration, measurement and operational checks as core deliverables, not last-minute extras.
Have a project or a specific growth question? Talk it through with Outfox Social.
Plan a safer website redesign
