Keep useful URLs and content wherever practical
A redesign changes the customer experience; it does not require changing every address. Start by identifying pages people use, pages linked from elsewhere and the services that generate relevant enquiries. Preserve those URLs when the new page serves the same purpose.
Changing colours or a layout alone is different from changing a domain, content structure or booking system. Name each change so the launch plan covers the actual risks.
Create the inventory before the design is finished
Combine the current sitemap, internal links, CMS or code routes and available search reports. Include downloadable documents, important images and campaign landing pages where they matter. A list of navigation links will miss pages reached from search or old emails.
- Record each current URL, its purpose, response status and proposed action.
- Keep useful content and record what genuinely needs replacing or retiring.
- Identify important enquiries, booking links and external systems.
- Capture available search and enquiry baselines with their dates and limitations.
- Confirm access to the domain, hosting and relevant search properties.
Map replacements page by page
Where an address must change, choose the new page that genuinely replaces its content. Use a permanent redirect for that relationship and update the site’s own links to the final destination. Sending every removed page to the homepage gives visitors an ambiguous result.
Some pages have no replacement. An accurate not-found response can be appropriate when content is intentionally removed. Do not create an empty page or misleading redirect simply to make every URL return success.
Keep preview access separate from production
A preview should be protected or deliberately excluded from search. Before release, verify that the production build uses the public domain and the intended indexing settings. Check both response HTML and the rendered page; a working design can still contain a noindex directive.
Record the previous working deployment and how to restore it if a material issue appears. Do not move business email or unrelated DNS records as an accidental side effect of changing the website host.
Check the release as a visitor and a crawler
Test the real public domain after launch, including representative old addresses. Confirm that HTTP status, visible content and metadata agree.
- Old-to-new redirects reach the correct destination without loops or avoidable chains.
- Canonical links, internal links and sitemap entries use the intended final URLs.
- Important content, images and service links are available without a special interaction.
- Forms and booking journeys work on mobile; a labelled test reaches its intended destination where authorised.
- Missing pages return a genuine error status and a useful route back.
Expect monitoring after the launch
Search engines need to revisit changed pages. Google recommends keeping migration redirects for at least a year in most cases, and longer where visitors still use old links. Search performance may fluctuate even with a careful migration.
Use the relevant search tools to inspect crawling, indexing and selected canonicals after the release. Compare the same markets and page groups, investigate specific failures and keep the old URL map available. A deployment marked ready is not the end of migration verification.
What to send Clara for a redesign assessment
Share the current website, the problem you want to solve and any fixed timing. Include the systems that must keep working and what you know about existing enquiries or search traffic. Access can be arranged through proper account permissions after the scope is clear; do not send passwords in an enquiry.
