A polished homepage offers little reassurance if the booking page has vanished or an established address now leads to an error. Before signing off a redesign, establish which pages, content and customer journeys must survive, then require evidence that they work on the replacement site. Rankings can still fluctuate, but these checks help prevent avoidable losses caused by the rebuild itself.
Capture a baseline before design begins
Record which landing pages attract organic search clicks and which generate enquiries or sales. Save reporting dates alongside page addresses and figures so later comparisons use consistent measures. Search Console shows search performance; analytics and enquiry records help explain what visitors do afterwards.
Put this baseline in the redesign brief so the web design agency Manchester businesses appoint can see which pages need protecting. Agree how their performance will be measured after launch.
Build a separate URL inventory from a crawl of the website, CMS records and available sitemaps. Search Console reports can supplement that inventory, although they will not necessarily contain every existing address.
Decide which pages and content to retain
Mark priority pages in the inventory and specify what each must continue to offer: service details, product information, specifications, useful answers or a route to enquire.
Preserve the page’s purpose, rather than every sentence. Correct outdated information and improve confusing copy while retaining the detail customers need. A cleaner layout should still accommodate those answers.
Review titles, headings and navigation alongside the main content. Each retained page needs a logical place in the replacement site and working internal links that help visitors reach it. Record proposed removals and consolidations before development starts.
Map every necessary URL change
A visual refresh alone does not require new page addresses. Retain URLs where they still make sense, and document necessary changes individually.
Imagine a repair business keeping `/services/repairs/` because the service and page purpose remain unchanged. If its booking page moves from `/repair-booking/` to `/book-a-repair/`, the old address should point directly to the relevant replacement through a permanent redirect, such as a 301.
A genuinely retired page with no equivalent can return a 404 (not found) or 410 (gone) response. Redirecting it to an unrelated homepage would give visitors a poor substitute for the information they expected.
Alongside each URL, record the decision, destination where applicable, expected response and eventual test result. Update internal links to use the intended live addresses directly, avoiding unnecessary journeys through redirects. The completed map becomes part of the launch approval record.
Make launch approval evidence-based
Test the replacement website against the priority-page list and URL map. Record the check performed, its expected result and whether it passed.
For the booking example, a pass means the old address redirects directly to the correct live page, the booking information remains available and a customer can complete the form.
Include these checks:
- Open priority pages and confirm their essential content and internal links are intact.
- Check that pages intended for search are free of accidental restrictions left over from development.
- Complete important mobile journeys, including menus, enquiries and purchases where relevant.
Review the technical settings behind those results. The `robots.txt` file controls crawling, while a `noindex` directive requests exclusion from search indexing. Canonical tags signal a preferred URL among duplicate or similar pages; check that important pages reference the intended address rather than a staging URL or an unintended alternative.
Broken priority-page redirects and accidental noindex directives should block launch approval. Minor cosmetic refinements can follow separately. Repeat critical checks immediately after launch, because live settings may differ from staging.
Monitor the live site and investigate changes
Submit the updated sitemap in Search Console to support discovery. Submission alone is not confirmation that pages have been indexed.
Assign responsibility for reviewing indexing reports, search clicks, landing-page performance and enquiries. Arrange closer checks around launch, followed by scheduled reviews using the saved baseline and URL map.
If reported traffic falls, confirm that analytics and enquiry tracking still work before diagnosing a search problem. Establish whether the change affects particular pages, devices or the whole website, then test affected URLs and compare their content, links and indexing settings with the approved record.
Keep a dated issue log showing the affected page, evidence, owner and correction. Retest the relevant page or customer journey before closing an issue.

