1. Inventory the current site
Record every live URL, page purpose, owner, and important asset before changing the structure. Mark pages to keep, combine, rewrite, redirect, or retire, and use analytics or Search Console data to identify content with real visitors or links.
Include the reason for each decision and preserve key metadata or media where they still serve a reader. A high-traffic page may need a rewrite or merge rather than a simple move.
2. Map old pages to new destinations
Create a one-to-one mapping where possible. A retired page should point to the closest useful replacement; do not send unrelated old URLs to the homepage. Note which links, images, and calls to action need updating.
Use the mapping table to identify redirects, but keep unchanged URLs unchanged where practical. Confirm that every destination answers the old page’s intent and that critical forms or downloads still work.
3. Move and review the content
Transfer the approved copy and media, then check headings, links, image descriptions, and page-specific metadata. A visual review catches layout changes; a separate URL crawl or manual link check catches paths that still point to the old site.
Compare the old and new versions at desktop and mobile widths. Check image paths, accessible labels, page titles, canonical URLs, and links to related content in addition to visual appearance.
4. Monitor after launch
Submit the updated sitemap and inspect important URLs in Search Console after the new site is available. Watch for not-found pages, unexpected indexing blocks, and broken redirects, then fix the source issue rather than adding unrelated redirects.
Keep a short issue log with URL, observed problem, owner, and resolution. Use the content inventory to control scope and the redirect mapping guide for moved URLs.
Related official guidance: Google Search Central: Site moves with URL changes.