Website Redesign SEO Checklist: Preserve the URLs That Matter

Build a baseline before removing the old site

Export an inventory of public URLs, important landing pages and known inbound links where the business has access to that data. Record page titles, main topics and the business role of each page. Distinguish pages that still help visitors from pages that are obsolete or duplicated.

Use verified analytics and search-console data if available, but do not invent a baseline when the accounts are unavailable. Even a manual inventory of the current site is better than assuming that only the homepage matters. Keep an agreed rollback or recovery path for the launch.

Preserve stable URLs when the topic is unchanged

A visual redesign does not require changing every address. If a service page still serves the same purpose, keeping its established URL can avoid unnecessary migration work. When the content changes substantially, decide the destination based on the visitor's likely intent rather than the neatness of a new navigation menu.

For an illustrative business website, an old bathroom-fittings catalogue page should not be sent to an unrelated software-service page simply because both businesses share an owner. Relevance matters more than finding any URL that returns a successful status.

Create a deliberate redirect map for real URL changes

Google's site-move guidance recommends mapping old URLs to their relevant new destinations and using server-side permanent redirects where appropriate. Avoid routing every removed page to the homepage or building unnecessary redirect chains. Keep the map in a form that can be reviewed and tested.

If there is no relevant replacement, decide the correct removal behaviour instead of pretending the content still exists. Test the actual HTTP outcome and final destination, not just whether a browser eventually opens some page.

Check canonicals, indexing controls and the sitemap

Confirm one intended production hostname, such as the agreed www or non-www address, and ensure canonical URLs match it. Do not let a staging hostname become the advertised production identity. Keep useful internal links pointed directly at the chosen destination rather than relying on redirects for ordinary navigation.

A private preview can correctly use noindex and crawler restrictions. The public launch needs a separate check that the relevant controls have been changed intentionally and that authentication is not blocking public pages. A canonical tag does not publish a private site or force a search engine to index it.

Re-test the business journey after deployment

Check forms, telephone links, email links, appointment routes and any commerce or account journeys. A technically successful migration is not a successful launch if the website sends enquiries to an abandoned inbox. Verify important pages at mobile and desktop sizes.

Ensure structured data reflects visible content and business facts. Keep organisation identity and contact details consistent. Do not add fabricated local branches, ratings or expertise to compensate for a change in design.

Monitor and investigate rather than promise stability

After launch, review verified indexing reports, crawl errors and important landing-page performance. Allow for recrawling and changes in search presentation. Investigate missing content, unexpected redirects or blocked pages before attributing every fluctuation to the new design.

• Retain the reviewed old-to-new URL map and launch date.
• Submit or confirm the production sitemap in owner-controlled webmaster tools.
• Inspect important pages and redirect destinations after release.
• Record fixes and real content updates without repeatedly changing dates just to appear fresh.