
A redesign should make your website easier to use and manage. It should also preserve the useful work your existing pages already do. A new appearance does not automatically require new URLs, and deleting an unfashionable page can remove something customers still find through search.
No designer can guarantee unchanged rankings after a migration. What you can do is reduce avoidable mistakes, record what changed and make problems easier to diagnose. Start this work before approving the new sitemap.
1. Find out what is worth keeping
Create a list of your current pages, downloadable files and important images. Include pages absent from the menu: an old guide might still attract links or answer a buying question. Add search clicks, useful enquiries and known external links where those records are available. A page with little traffic can still matter if it brings the right enquiry.
For each URL, choose an action: keep, improve, merge into a genuinely relevant page, or retire. Record why. This simple inventory gives the designer and whoever manages SEO a shared basis for decisions.
2. Write a redirect map before the build finishes
If an address must change, identify the closest useful replacement. Google’s site migration guidance recommends permanent redirects when URLs move. Sending every removed page to the homepage is rarely a helpful substitute for matching old content to its new home.
| Old page | Proposed treatment | Reason |
|---|---|---|
| Current service page | Keep its address; improve the content | The service and purpose remain the same |
| Two overlapping guides | Combine them and redirect the retired address | One stronger resource answers both needs |
| Discontinued offer with no equivalent | Review whether a useful replacement exists | An unrelated redirect could confuse visitors |
This is an illustrative planning table, not a prescription for every website. Agree the actual destinations before launch, then test them. Avoid unnecessary redirect chains by pointing each old address directly to the final page.
3. Carry over meaning as well as metadata
A migration can preserve every URL and still lose useful content. Check that important service explanations, examples, qualifications and customer questions survive the design process. Do not replace a detailed page with a large photograph and a vague slogan simply because the new layout looks cleaner.
Transfer accurate page titles and descriptions, or deliberately improve them. Check heading structure, image descriptions and internal links. Update links to their final destinations so visitors are not repeatedly sent through redirects. Keep the canonical address consistent with the page you actually want indexed.
4. Give launch checks an owner
Staging sites often need protection from indexing. Production pages need a separate check when the site goes live. A forgotten noindex setting can undermine an otherwise careful launch.
- Check representative old URLs and their final destinations.
- Confirm important live pages are accessible and indexable.
- Review the XML sitemap and canonical URLs.
- Test navigation, contact forms, phone links and downloads.
- Confirm analytics and enquiry tracking still work.
- Check mobile layouts and the loading of important images.
Name the person responsible for each check and record its result. “The developer is handling it” is not a useful handover note unless the scope is clear.
5. Compare meaningful evidence after launch
Keep a dated record of the launch and the pages that changed. Review Search Console, broken-page reports and actual enquiries over the following weeks. Compare similar periods where possible, allowing for seasonality and changes to advertising. One quiet day does not establish an SEO problem.
If something drops, investigate the affected pages and queries first. A broad traffic total can hide a broken high-value service page or a harmless decline in irrelevant visits. Fix specific faults before making another sweeping redesign.
Bring the migration into your design brief
Include the existing URL inventory, redirect responsibilities and launch checks in your website design brief. If you are planning a website redesign for a London business, Dreamkatcha can discuss the content and design decisions alongside the technical handover. Tell us what you want the new site to achieve.