The short answer
A redesign loses search visibility when the pages Google already knows about disappear without a trace: URLs change with no redirects, pages that brought in visitors get cut, or the new site launches still blocked from search engines. All of that is preventable. The work is mostly bookkeeping, done before launch rather than after the traffic drops.
The checklist below follows Google’s own guidance on site moves with URL changes, which applies to any redesign that changes page addresses, even on the same domain. If your URLs stay exactly the same and only the hosting changes, Google has a separate, simpler guide (site moves without URL changes).
Before the redesign: know what you have
1. Inventory every URL on the current site. Google suggests pulling old URLs from your sitemaps, analytics, server logs, and content management system. Don’t rely on the menu. Old blog posts, landing pages from past ad campaigns, and PDFs are the pages most often forgotten, and they sometimes carry the most links from other sites.
2. Find the pages that earn search traffic. Search Console’s performance report breaks down your Google Search traffic by query and by page (Google, Search Console start guide), and its Links report shows which pages other sites and your own pages link to. Mark the pages that show up in either. They are the ones the redesign must protect most carefully.
3. Save a baseline. Export the current search data and note how many pages are indexed. Without a record of before, there is no way to tell after launch whether a change is a problem or normal movement.
4. Decide what happens to each page. Every old URL gets one of three outcomes: keep it (same or new address), merge it into another page, or retire it. Be cautious about cutting content that ranks just because it doesn’t fit the new design. A shorter, prettier page that no longer answers the question it used to answer can lose the search visibility it had.
The redirect map
5. Map every old URL to its new equivalent. Google calls mapping old URLs to new ones important, and it is the single most important step on this list. A spreadsheet with two columns, old URL and new URL, is enough.
6. Use permanent, server-side redirects. Google recommends 301 or 308 redirects wherever possible, calling them “the best way to ensure that Google Search and people are directed to the correct page,” and treats a permanent redirect as a signal that the new page should be the one shown in results (Google, redirects). Temporary redirects aren’t treated as that signal. JavaScript redirects are a last resort, because Google “might never see it” if the page fails to render.
7. Redirect to the most relevant page, not the homepage. Google’s guidance is direct: “Don’t redirect many old URLs to one irrelevant single URL destination, such as the home page of the new site,” because that “might be treated as a soft 404 error.” If several old pages were merged into one new page, redirecting them all there is fine. For old pages with no equivalent at all, Google says to make sure they return a 404 or 410.
8. Avoid chains. Google’s advice is to avoid chaining redirects and to redirect “to the final destination directly.” This matters most on sites that have been redesigned before and already carry redirects from a previous version.
While the new site is built
9. Keep the staging site out of search. A development copy should be blocked from crawling or password-protected so it doesn’t get indexed. Google notes that this is common and recommends preparing, before launch, the robots.txt file the live site will need and a list of pages whose noindex rules must be removed.
10. Carry the SEO fundamentals across. Page titles, meta descriptions, headings, and image alt text on the pages you marked in step 2 should be reviewed and carried over deliberately, not regenerated by a new theme’s defaults.
11. Update internal links to the new URLs. Redirects catch old links, but the new site’s own links should point straight at the new addresses. Google lists this as a step in its migration guidance, along with giving each new page a self-referencing canonical tag.
12. Include images, files, and other embedded content. Google reminds site owners to include the URLs of embedded content, such as images, videos, and scripts, in the move plan. Image search traffic and linked PDFs are easy to lose without noticing.
Launch day
13. Remove the blocks. Take off the staging noindex and any robots.txt rule that blocks crawling. A new site that launches still telling search engines to stay away is an easy mistake to make, an expensive one to miss, and one of the easiest to check.
14. Switch everything at once. For small and medium sites, Google recommends “moving all URLs on your site simultaneously instead of moving one section at a time.”
15. Test the redirects. Run a sample of old URLs, starting with the pages from step 2, and confirm each one lands on the right new page in a single hop.
16. Submit the new sitemap. Add the new sitemap in Search Console. The Change of Address tool is only needed when moving to a different domain or subdomain; Google says it isn’t needed for HTTP-to-HTTPS moves, www changes, or path changes within the same domain.
After launch
17. Watch Search Console. Check the Sitemaps and page indexing reports for both new pages being indexed and old URLs returning errors they shouldn’t. Fix any 404 that should have been a redirect as soon as it appears.
18. Expect some movement, and give it time. Google says visibility “may fluctuate temporarily during the move,” and that for a small to medium-sized site it “can take a few weeks for most pages to move.” A dip in the first weeks is not by itself a sign something is broken. A page that drops out entirely, or a steady stream of 404s, is.
19. Update the links you control. Google suggests updating profile links and contacting sites that link to your old pages. For a local business that also means your Google Business Profile, social profiles, and directory listings.
20. Keep the redirects. Google’s guidance is to keep redirects for as long as possible, generally at least one year, and notes that leaving them in place indefinitely can help visitors. When the site is redesigned again in a few years, keep them in the new redirect map too.
What a careful redesign can and can’t promise
Following this list protects what the site already has. It doesn’t guarantee better rankings, and no one can honestly promise that. What it does is stop a redesign from throwing away years of accumulated search visibility, and when the new site is clearer, faster, and better organized than the old one, we often find real success.
How Webbify handles it
The Lily Lane Aesthetics project is an example of this kind of work: it expanded from a Squarespace refresh into a broader WordPress redesign and migration, with Webbify creating and managing a staging environment and supporting the migration and deployment. Webbify’s website redesign work starts with the URL inventory and redirect map, not the mockups. When the platform or domain is changing too, that falls under website migrations. And the crawling, indexing, and redirect checks before and after launch are part of technical SEO.