Insight

A website redesign migration checklist that follows the whole journey

The checks we use to carry content, URLs and enquiries into a redesigned website, informed by our own JAS rebuild.

A working URL can still be an incomplete page

During our own website rebuild, we checked retained addresses against their original records and the rendered pages. That highlighted an important distinction: a successful response can still lead to a page with no useful main content.

The migration check therefore follows the whole journey. It asks whether the page is present, meaningful, discoverable and able to hand a customer action into the business.

1. Build the inventory before making changes

Collect the published pages, articles, portfolio records, taxonomy archives and known aliases. Add relevant URLs from search reports, analytics and inbound links where those sources are available. A CMS export alone may not contain every historical address.

  • Record the current URL, content type and intended replacement.
  • Identify useful copy, images, downloads and metadata.
  • List forms, stored submissions, notifications and integrations.
  • Keep a baseline and a recoverable copy before making changes.

2. Give each important URL a deliberate outcome

Retain an established URL where the purpose remains the same. When a page moves, map it to the most appropriate replacement and use an intentional redirect. A removed page needs an appropriate removal response rather than an unrelated destination.

Test the actual response and final address. Check for loops, unnecessary hops and rules that make an unknown address look like a working page.

Google’s site-move guidance

Review the important templates at representative sizes. Confirm that headings, main copy, images, tables and customer actions are present. Older builder markup can survive in excerpts even when the full page looks correct.

  • Check page meaning as well as content length.
  • Follow internal links, breadcrumbs, related content and navigation.
  • Check phone layouts, keyboard controls and horizontal overflow.
  • Confirm important content remains available in the intended rendering modes.

4. Follow a form through to its destination

Submit an authorised test using clearly labelled test details and confirm the result. The website should explain success, retain the submission in the intended store and notify the right destination. An attractive confirmation screen does not prove the handover occurred.

Check validation and failure behaviour too. If notifications depend on a queue or external mail service, agree how failures become visible and how a stored enquiry can be recovered. Do not mix test submissions with genuine sales reporting.

5. Align indexing signals

Check the canonical address, index directives and sitemap entry against the page’s intended role. Keep staging and preview environments out of public indexing, and confirm that a production release has the correct settings.

Validate the structured data already produced by the site before adding another layer. Business facts, page identity and visible content should agree. A sitemap is a discovery aid; its presence does not establish that a page is indexed.

  • Use the preferred protocol and hostname consistently.
  • Check the main page and article sitemaps after publication.
  • Retest redirect destinations and genuine missing-page behaviour.
  • Inspect representative URLs in the search tools when access is available.

6. Release with a route back and a monitoring owner

A deployment plan identifies what changes, how it is validated and how the prior version can be restored. A content backup and a code rollback solve different problems; both may be needed.

After launch, monitor failures, enquiries and search coverage. Compare against the baseline and investigate the underlying pages rather than assuming every traffic change has the same cause. Record who owns that review and the route for issues to be actioned.

Make the checklist part of the redesign brief

These checks work best when the content inventory, URL map and form destinations are agreed during planning. They then become acceptance work for the new website instead of a list discovered at the end.

Our London website design approach

Understand the architecture choices

Discuss your redesign