1. Record the current site before changing it
Export the existing URL list, page titles, meta descriptions, indexation state and top Search Console landing pages. Capture analytics for important organic landing pages and conversions. Record the backlinks and redirects that point to valuable URLs where the available tools make that possible. This gives you a before-and-after baseline.
2. Decide which URLs should survive
Keep strong URLs when possible. If a URL must change, map the old page to the closest relevant new page. A redirect should satisfy the original visitor intent; do not send every retired URL to the homepage. If there is no replacement, consider whether the content should remain available, be consolidated carefully or return a proper 404/410 status.
3. Preserve intent and useful content
Compare the old and new page purpose, main heading, page title, core copy, internal links and conversion action. A shorter redesign can still be successful, but do not remove content that answers essential customer questions without a plan. Retain high-value resources and make sure new pages have clear internal links from relevant hubs.
4. Check technical controls on staging
Use a private or protected staging environment where practical. If staging uses a noindex directive, verify it is removed on launch. Check canonical URLs, robots rules, sitemap output, structured data, HTTPS, mobile navigation, forms, images, font loading and 404 behaviour. Do not accidentally block production pages with a leftover staging rule.
5. Test redirects and internal links
Crawl the staging version and review status codes, redirect chains, broken links, duplicate titles, missing meta descriptions, multiple main headings and pages without internal links. Test every contact route, especially phone and WhatsApp links on mobile. Redirects should normally be direct rather than chained through several old URLs.
6. Launch with a controlled checklist
Deploy during a period when the team can monitor the site. Verify the homepage, major service pages, contact flow, XML sitemap and canonical domain. Confirm that the server returns correct status codes and that the live assets load from their expected paths. If URLs changed, publish the planned redirects as part of the same launch.
7. Monitor the next few weeks
Submit the current sitemap to Search Console, inspect representative URLs, monitor crawling/indexing reports and compare organic landing-page data with the baseline. Investigate unexpected drops by checking status codes, redirects, noindex directives, canonical selection, internal links and content changes. Avoid making many unrelated changes before the cause is understood.
Next step
Planning a rebuild? Pair this checklist with our website development service and SEO service.