The short answer
Before launching a redesigned website, preserve pages that still help visitors, create an old-to-new URL map, use direct permanent redirects for changed URLs, check the live pages and submit the new sitemap. After launch, monitor indexing, queries, clicks, errors and real-user page experience in Search Console. This process reduces avoidable technical and user problems, but it cannot guarantee rankings: Google says visibility may fluctuate temporarily during a site move and that good page-experience scores do not guarantee top positions. [1] [3]
1. Protect useful content before changing the design
Start with an inventory of the current site. Export or record every important page, its URL, purpose, primary topic, internal links, contact or enquiry action, and any available performance evidence. Include service pages, location pages, guides, case studies and other pages that answer real customer questions. This is not a reason to preserve every weak or obsolete page unchanged; it is a way to make deliberate decisions instead of deleting useful material by accident.
For each page, choose one outcome: keep the URL, improve the page at the same URL, move it to a relevant new URL, combine it with another page, or retire it because there is no suitable replacement. Preserve the substance that users need, then improve clarity, navigation and calls to action. Avoid replacing a detailed page with a generic homepage simply because the redesign has fewer templates.
2. Map every changed URL to its best destination
Create a spreadsheet with at least four columns: old URL, new URL, action and test result. Google recommends creating an old-to-new URL mapping, updating internal links and sitemaps, and ensuring each new page has a self-referencing canonical URL. [1]
Where a page has moved, configure a server-side permanent redirect, such as a 301 or 308, from the old URL directly to the final relevant page. Do not send many unrelated URLs to the homepage. Google warns that irrelevant redirects can confuse visitors and may be treated as soft 404s. Avoid chains such as old URL → temporary URL → new URL; link and redirect directly to the final destination where possible. [1] [4]
Keep redirects in place for as long as practical. Google’s site-move guidance says generally at least one year allows time for signals to be transferred and old URLs to be recrawled. [1] Update internal links, navigation, XML sitemaps, campaign links and important profile links so they use the new URLs rather than relying on redirects forever.
3. Validate the redesigned site before launch
Test the staging site with a repeatable checklist, then repeat the highest-risk checks on production. Confirm that important pages return the expected status, load over HTTPS, have a clear title and main heading, contain the intended copy, and do not accidentally carry noindex rules from staging. Check canonical tags, robots.txt, structured data where used, image alt text, forms, phone links and primary calls to action.
Open representative pages on mobile and desktop. Check that menus, content, buttons and forms work with a keyboard and on smaller screens. Measure performance with real-user and lab tools where available. Google recommends looking at the overall page experience, including Core Web Vitals, secure delivery, mobile display and intrusive interstitials. It also cautions that a strong report or perfect score is not a ranking guarantee. [3]
Before switching DNS or publishing the new templates, crawl the staging or production candidate and compare it with the URL map. Check that internal links point to final URLs, the new sitemap contains the intended canonical URLs, and analytics collection and Search Console ownership are verified without duplicating or exposing private data.
4. Launch carefully and monitor evidence, not assumptions
At launch, activate the redirects, publish the new sitemap and verify key URLs with Search Console’s URL Inspection tool. If the domain or subdomain changes, use Search Console’s Change of Address tool; it is not needed for a path change on the same domain. [1]
For the first days and weeks, review the Indexing and Performance reports. Search Console can show indexed or excluded pages, crawl issues, queries, pages, countries, impressions and clicks. [2] Compare the old and new URL groups, check for unexpected 404s or redirect errors, and review server logs or analytics for broken journeys and failed forms. Google notes that processing a small or medium site move can take a few weeks and that temporary visibility fluctuation is normal. [1]
Record launch changes and review trends over comparable periods. A traffic change alone does not prove a particular cause, so investigate page-level data before drawing conclusions. Fix technical errors first, then improve content or user journeys based on evidence from customers, analytics and Search Console.
A practical final check
Before approving the launch, ask: have useful pages and content been accounted for; does every changed URL have a relevant destination; do redirects go directly to final URLs; are canonicals, internal links and sitemaps updated; do the main pages work on mobile; are forms, analytics and Search Console verified; and is someone responsible for monitoring indexing, errors and enquiries after release?
If you want help planning a redesign around responsive delivery, performance and an SEO-ready structure, Engage24’s Website Design & Development service describes custom websites, mobile-first builds, WordPress development, speed optimisation, SEO-ready structure, analytics and Search Console integration, plus post-launch support. [5] Get a tailored quote after reviewing your current URLs and launch requirements.

