Why a redesign can erase years of rankings
Google does not rank your website as a single thing. It ranks individual pages, each with its own URL, its own history, and its own links from other websites. When a redesign changes those URLs or deletes those pages, Google treats the new site as a stranger. The trust your old pages earned does not transfer automatically, and rankings you built over years can vanish in a week.
The damage almost never comes from the new design itself. It comes from four preventable mistakes: changing URLs for cosmetic reasons, deleting pages that quietly brought in traffic, cutting page text because the new layout looks cleaner with less of it, and launching with a hidden setting that tells Google not to index the site at all. I have seen each of these happen, and every one costs far more to recover from than to prevent.
Start with an inventory, not a mockup
Before anyone designs anything, make a list of every page you have and what each one earns you.
- Crawl your current site with a free tool like Screaming Frog, which lists every URL, or export the pages report from Google Search Console.
- In Search Console, note which pages received clicks and impressions over the last twelve months. Impressions are the times your page appeared in search results.
- Mark every page that gets traffic as protected. It keeps its URL, or it gets a redirect. No exceptions.
This usually takes an hour or two for a small business site, and it is the single highest-value hour of the whole project. You cannot protect what you have not counted.
Keep URLs the same, or map them one-to-one
The safest URL is the one you do not change. If your services page lives at /services, keep it at /services in the new design. Google sees the same address with fresher content, which is exactly what you want.
When a URL must change, set up a 301 redirect, which is a permanent forwarding instruction that tells Google and visitors the page has moved. Two rules matter here. First, redirects must be one-to-one: the old kitchen remodeling page points to the new kitchen remodeling page, not to the homepage. Redirecting everything to the homepage is the classic mistake, and Google treats those pages roughly like deleted ones. Second, avoid chains where old page A points to B, which points to C. Point A straight at its final destination.
Write the whole map in a spreadsheet before launch: old URL in one column, new URL in the next.
Protect the content, not just the addresses
A page ranks for a phrase because its text actually covers that phrase. If your old page had 800 words about water heater replacement and the redesigned page has 150 words and a big photo, expect to lose that ranking even though the URL never changed.
Carry over the page title, the main heading, and the substance of the body text. Keep the descriptive text on images, called alt text, which is the short label screen readers and Google use to understand a picture. You can absolutely rewrite copy to sound better. Just do not shrink a page's coverage of its topic, and do not merge five service pages into one thin page because the new template only has room for one.
Launch day and the ninety days after
On launch day, three checks come before celebrating.
- Confirm the noindex setting is off. Development sites are usually hidden from Google on purpose, and forgetting to unhide the live site is a surprisingly common disaster.
- Submit your new sitemap in Google Search Console.
- Click through your redirect map and confirm the old URLs actually forward.
Then watch Search Console weekly for about ninety days. The pages report shows 404 errors, which are visits to addresses that no longer exist; each one is a redirect you missed. Compare clicks per page against your pre-launch inventory. A small dip for a few weeks is normal while Google recrawls. A page that falls off a cliff and stays down is a signal to check its redirect and its content parity.
What to do next
If a redesign is on your calendar, here is the order of operations.
- Export your pages from Search Console and crawl the site. Build the inventory spreadsheet.
- Mark protected pages and decide, page by page, whether the URL stays or gets a one-to-one 301 redirect.
- Draft new copy alongside old copy and check that no protected page loses substance.
- Before launch, verify redirects on a staging copy and confirm indexing will be enabled.
- After launch, review Search Console weekly for three months.
If your current developer cannot walk you through this list, that is worth a conversation before the project starts, not after. At HashWhales this checklist is built into every redesign we do, because recovering lost rankings is slow and keeping them is cheap.