A redesign can improve usability while damaging search visibility if important URLs disappear or the new site blocks crawling. Before launch, export the current URL list, map each valuable page to its best replacement, test redirects on staging and keep Search Console access. This practical sequence is for a normal redesign on the same domain; a domain change needs additional site-move steps.
1. Record what exists before changing the site
Export the current sitemap and crawl the live site to list indexable URLs, status codes, titles, headings, canonical tags, internal links and image URLs. Add Search Console page and query data, analytics landing pages, and any known campaign links. Flag pages that attract visits, enquiries, links or impressions, then verify they still deserve a place on the redesigned site.
This baseline helps distinguish a migration issue from a seasonal or normal fluctuation. Keep a copy of key page content, structured data, robots.txt and analytics configuration. If several subdomains are involved, document which host serves each feature.
2. Decide which URLs stay and which change
Keep a URL when it still describes the same page and works well for visitors. If a page is replaced, map the old URL to the closest relevant new page. Do not send every retired page to the homepage; the destination should satisfy the original intent. If there is no meaningful replacement, return a proper 404 or 410 rather than creating a misleading redirect.
Build a two-column redirect sheet with the old path and final destination. Avoid redirect chains: an old URL should land directly on the final canonical URL. Use server-side 301 redirects for permanently moved pages and test the status code, destination and behavior for query strings where they matter.
3. Test the new site before launch
- Confirm staging is private and not accidentally available as an indexable duplicate.
- Check that production pages return successful status codes and the robots rules allow important pages to be crawled.
- Review titles, descriptions, headings, canonicals, internal links and structured data.
- Test redirects from the old URL list, including old campaign or backlink URLs.
- Submit forms and confirm analytics events still record the key enquiry actions.
- Compare the new sitemap to the intended live URLs, not staging URLs.
4. Launch and monitor
Release the site, enable the redirects and check a representative sample immediately. Review server errors and crawl statistics, then use Search Console’s URL Inspection and Page Indexing reports to investigate important URLs. Submit an updated sitemap when appropriate. Monitor organic landing-page traffic, impressions and enquiries against the baseline over the following weeks. Google notes that crawling can increase after a site move, so keep the old redirects in place and watch for technical errors.
Google’s site-move documentation recommends preparing URL mappings and redirects for changed addresses. Google’s redirect guidance explains permanent server-side redirects. These steps reduce avoidable technical errors; they cannot guarantee a particular ranking or traffic outcome.
Common redesign SEO problems
- Launching a new page structure without a complete redirect map.
- Leaving staging noindex tags or robots disallow rules on the production site.
- Changing the copy, internal links, URLs and domain at once without a test plan.
- Removing useful pages because they look old without reviewing their traffic or links.
- Failing to update canonical tags, XML sitemap, analytics or Search Console verification.
- Removing redirects too early; old links and bookmarks can continue to be used.
A practical launch-day order
Back up the old site; publish the new site; activate the redirect map; check HTTPS and crawlability; test top pages and enquiry journeys; confirm analytics; submit the sitemap; then monitor errors and key landing pages. Assign one person to own the checklist and record issues with a URL, status, impact and fix.
If your project includes a wider rebuild, pair this guide with the small business launch checklist. For an independent website review, visit the Bennie Studio app.
Last reviewed: October 2026. Search performance can fluctuate after a redesign. Check Google Search Central and your hosting documentation for the current steps that apply to your site.