Business guide
Website redesign SEO: protect useful pages before changing the design
Plan a business website rebuild around existing search visibility, page purpose, URL changes and tested enquiries instead of treating SEO as a launch-day plugin.
Start with what the existing site already does
A redesign can improve the site while also removing the pages people already find. Before choosing a new layout, export a useful baseline from Search Console and your analytics: landing pages, relevant searches, enquiry routes and the dates being compared. Ask the business which pages support valuable work even when their traffic is modest.
This is not an argument for keeping every old paragraph. It is a way to identify what deserves a considered decision. A specialist maintenance page with a handful of suitable enquiries can matter more than an unrelated article with many visits. Record the purpose and evidence before deciding whether to keep, improve, combine or remove it.
Give each old page an explicit outcome
Make a page inventory with the current address, subject, search role and intended replacement. Preserve useful URLs when there is no good reason to change them. If you combine pages, check that the replacement still answers the distinct needs being served rather than becoming a vague summary.
For permanent URL changes, plan direct server-side redirects to the most relevant replacement. Sending retired service pages to an unrelated homepage is not a considered mapping. Use the domain-move guide if the address itself is changing; it covers redirect duration and Search Console’s applicable change-of-address requirements.
- Evidence
Record its searches, visitors and business purpose.
- Decision
Keep, improve, merge or retire with a reason.
- Destination
Preserve the URL or identify a relevant replacement.
- Verification
Test the live page and any required redirect.
Keep useful meaning while improving the experience
Check that the rebuilt service pages still explain the actual work, coverage, qualification process and next step. A cleaner design can accidentally reduce a detailed service to a heading and a contact button. Customers and search systems need enough readable information to understand what is offered.
Review internal links too. Guides should lead to the matching service, and service pages should expose useful supporting answers. Do not leave important pages accessible only through a site search or an animated control. Check the mobile reading order, heading structure, image descriptions and contact details as part of the content review.
Verify the production setup rather than trusting the preview
Before the switch, test the new site with representative old links and the intended public domain. Check page titles, canonical addresses, sitemap entries and whether any staging noindex setting will remain on production. The person launching must understand which restrictions protect the preview and which would prevent the finished site being indexed.
Retain the intended production analytics property and document any measurement changes. Use the migration checklist for contact, booking and deployment verification rather than making visual approval the only launch gate. A new layout is easier to assess when the evidence still describes the same business journey.
For staging, ask how access is restricted and how indexing is prevented. Noindex is a search instruction, not privacy protection, and Google must be able to crawl a page to read it. A robots.txt block alone is not a reliable way to keep an address out of search. Keep genuinely private previews behind appropriate access controls.
Monitor the same pages and searches after launch
Record the launch date and any later changes. Review indexing, key URLs, impressions, clicks and enquiries over comparable periods. Temporary movement can occur while Google reprocesses significant changes; that does not excuse a broken redirect, a noindex error or a contact form that fails immediately.
My website design work can include an agreed SEO migration plan, with page decisions and launch checks made before the replacement goes live. No rebuild can promise unchanged rankings. The practical aim is to preserve useful signals and customer journeys while making the site clearer and easier to maintain.