A business hires an agency for a redesign. The new site is genuinely better looking. Six weeks after launch, the map pack position is gone, "near me" traffic is down 60%, and the agency says rankings "fluctuate." They don’t fluctuate like that. Losing rankings after a redesign is rarely bad luck: the redesign broke specific things, the same specific things almost every time.
Rankings don’t get lost in redesigns. They get left behind: page by page, tag by tag, by whoever didn’t make the migration checklist.
The URL massacre
Agencies love clean new URL structures. /services/emergency-plumbing-austin/ becomes /what-we-do/plumbing/: tidier, and catastrophic. Every URL that ranked was an address Google had built trust in; change it without a 301 redirect and that trust points at a 404. The fix is a complete redirect map, old URL to new, live the minute the new site is. Google documents exactly how to move a site without losing rankings. The process exists; it just requires someone to own it.
How to build the redirect map
- Collect every old URL: the Pages report and Performance data in Search Console, the old sitemap, and a crawl of the old site before it is switched off.
- Map each one to its closest equivalent on the new site. Redirecting everything to the home page throws away what each page had earned.
- Use permanent 301 redirects, one hop each. Chains of redirects slow crawling and are easy to break later.
- Update the internal links on the new site to point at the new URLs directly, instead of leaning on the redirects forever.
Often the best redirect is the one you never need. If the old URLs ranked and were reasonable, keeping them is the safest choice of all.
The content "cleanup" that deletes rankings
Designers cut text because text fights layouts. The 900-word service page ranking for a dozen local long-tails becomes an elegant 150-word section, and every long-tail goes with the words. Local pages are the most common casualty: the town-by-town service pages get consolidated into one "Areas We Serve" list, and the site stops ranking in every town that lost its page.
The answer is to design around the content, not delete it. Long pages can be broken into clear sections with subheadings, a short FAQ and good spacing. Thin template pages are the opposite problem. If the new site launches with dozens of near-empty pages, expect them to land in Search Console as "Crawled, currently not indexed", which I cover in fixing "crawled, currently not indexed".
The local signals nobody carries over
Local SEO lives on specifics that redesigns treat as clutter: the business name, address, and phone in crawlable text (not baked into an image), LocalBusiness schema markup, the embedded map, and the exact NAP formatting that matches the Google Business Profile. Strip those during a rebuild and Google’s confidence in the business-location connection drops, which is precisely what the map pack ranks on.
Check the markup against the LocalBusiness type on schema.org, and check the website link on the Business Profile itself. If it points at an old URL that now redirects or returns a 404, fix it there too.
The technical regressions
Two more classics: the staging site’s noindex setting shipping to production (check within the first hour of launch, every time), and the new design being heavier than the old one, a builder-based rebuild that doubles load time takes a Core Web Vitals penalty on top of everything else.
Both are cheap to catch before launch. Search the staging templates for noindex before go-live, not after, and run the old and new versions of your key pages through PageSpeed Insights side by side. If the new one is slower, fix it while the old site is still live.
How to protect your rankings on the next redesign
Before anyone designs anything, export every page with clicks from Search Console and every URL with backlinks. That’s the protected inventory. Demand the redirect map as a deliverable. Insist ranking pages keep their content depth, their H1s, and their schema. And re-crawl the site launch week, watching Search Console for 404 spikes.
This is exactly the checklist built into my redesign process: keeping rankings is the deliverable, not an upsell. It’s also, frankly, the argument for hiring the person who actually does the work: migrations fail in handoffs, and a solo build has none.
What to check in the first month after a redesign
- Launch day: confirm there is no site-wide
noindexand that robots.txt is not blocking the site. Submit the new sitemap. - First week: test a sample of old URLs from your inventory. Each should land on the right new page in one hop.
- First two weeks: watch the Pages report for new 404s and for pages moving into "not indexed".
- First month: compare clicks per page against the same period before launch. A page that dropped sharply usually lost content, a redirect or its links.
For local businesses this is not an abstract SEO exercise. The map pack is where the calls and bookings come from. A redesign that loses it costs real work, whether that shows up as a quiet phone, covered in why contractors’ websites don’t get the phone ringing, or as empty appointment slots, covered in why your clinic website isn’t booking appointments.
