A redesign changes more than colors. If page addresses, content, navigation or technical rules change together, Google has to understand what moved and what still matters. Plan the URL changes before launch and keep a record of the old site.
Build a one-to-one URL map
Export the current URLs from the sitemap, analytics and Search Console. For every old address, choose the most relevant new page. A product page should lead to that product or a genuine successor; a retired service page might go to its closest current service. Do not send unrelated pages to the homepage. JupiWeb’s redirect map builder can export rules for common hosting setups.
Prepare and launch
Keep important page content and internal links where they still fit. On the new site, check canonical tags, language alternates, indexability and the sitemap. Test the redirect rules before switching the domain; look for loops, chains, broken destinations and pages that accidentally return 404 or noindex.
Google’s site move guidance recommends testing the URL map and redirects, updating the new sitemap, and monitoring both old and new URLs. It notes that visibility may fluctuate while Google recrawls and that medium-sized moves can take weeks or longer to settle. Keep redirects for at least a year, then review real traffic and crawl data before removing any.
Watch the first weeks
Use Search Console to inspect priority URLs, sitemap coverage and not-found errors. Check server logs or analytics for old URLs that still receive visits. Fix broken internal links and update profiles, campaigns and partner links to point directly to the new pages.
The migration work should be included in the project scope. JupiWeb lists website builds from €490; URL mapping and migration effort depend on the number of old pages and the quality of the source data.