A redesign can improve how your site looks, loads and converts. It can also quietly erase years of search visibility if URLs change, content disappears or redirects are missed. Most ranking losses after a relaunch are avoidable, because they come from missing steps rather than from the design itself.
This checklist covers the work that protects your search performance, from the first inventory through the weeks after launch. Some movement in rankings right after a relaunch is normal, so the goal is to prevent avoidable damage and spot problems early.
Start with a full URL inventory
Before touching the design, list every URL on the current site. Crawl the site with a tool such as Screaming Frog, then add URLs from your XML sitemap, Google Search Console performance report and Google Analytics landing page report. Pages that earn traffic or links may not appear in your navigation, so using several sources catches them.
In a spreadsheet, record for each URL: page title, meta description, main heading, organic clicks, number of backlinks if available, and whether it will exist after the redesign. This sheet becomes your redirect map and your post-launch checklist.
Decide what stays, merges or goes
A redesign is a good moment to prune thin or outdated pages, but do it on purpose. Sort each URL into one of three groups.
- Keep: pages with traffic, rankings, links or conversions. Preserve their content and URL where possible.
- Merge: overlapping pages that can be combined into one stronger page, with the old URLs redirected to it.
- Remove: pages with no value, redirected to the closest relevant page or returning a proper 404 or 410 if nothing fits.
Resist the urge to rewrite high-performing pages from scratch. Keep the core copy that earns rankings and improve the layout around it.
Map every change with 301 redirects
If any URL changes, including a switch from http to https, a new domain, or a new folder structure, the old address needs a permanent 301 redirect to its new equivalent. Redirect each old URL to the most relevant new page, not to the homepage. Sending everything to the homepage tells search engines the specific content is gone.
- Add a column to your inventory with the new URL for each old one.
- Implement redirects at the server or platform level.
- Avoid chains, where A redirects to B and B redirects to C. Point A straight to C.
- Test a sample of old URLs and confirm they return a 301 and land on the right page.
Platform changes are where this goes wrong most often. If you are moving from WordPress to another system, our web development team plans the redirect map as part of the build.
Carry over metadata and on-page elements
New templates frequently drop things the old site had. Check that each important page keeps its title tag, meta description, heading structure, image alt text, canonical tag, and any structured data such as local business or product markup. Make sure internal links still point to live pages rather than to redirected ones.
Also protect tracking. Confirm your analytics and conversion tags carry across, and review the setup in Tag Manager so form submissions and calls still record after launch.
Build and test on staging
Develop the new site on a staging copy that search engines cannot index. Use password protection, since a noindex tag can be forgotten and carried into the live site. Before launch, test the following on staging:
- Every priority page loads and displays correctly on mobile and desktop
- Forms submit and notifications arrive
- Redirect rules work as planned
- Page speed is acceptable on key templates
- Robots.txt and noindex settings are ready to switch for production
On launch day, the most common error is leaving staging restrictions in place. Check robots.txt and page source immediately after going live.
Launch, then verify in Search Console
Schedule the launch for a quieter traffic period and have someone available to fix issues. After it goes live, work through these checks.
- Submit the updated XML sitemap in Google Search Console and confirm it is processed without errors.
- Use the URL Inspection tool on the homepage and several key pages to confirm they are indexable.
- Re-crawl the live site and compare it against your inventory to find missing pages or broken links.
- Watch the Pages indexing report and the Crawl stats for spikes in 404 errors or server errors.
- Compare clicks and impressions for your top pages against the weeks before launch.
- Verify conversions are still recording in analytics.
Keep monitoring for several weeks. If a page drops, check redirects, content changes and internal linking first. For a rebuild handled end to end, see our web design services.
Key takeaways
- Build a complete URL inventory from a crawl, your sitemap, Search Console and analytics before changing anything.
- Redirect every changed URL with a one-step 301 to the most relevant new page.
- Carry over titles, descriptions, headings, canonicals and tracking, and test it all on a protected staging site.
- After launch, submit the sitemap, inspect key URLs, and monitor Search Console for several weeks.