Most people find out their redesign hurt their SEO about three weeks after launch. The new site looks great. Everyone's happy. Then the phone gets a bit quieter, someone opens Search Console, and the graph looks like a ski slope.
The design almost never causes it. What causes it is the stuff nobody sees: old URLs that now lead nowhere, page titles that got "cleaned up", a city page someone thought was ugly and deleted. Google spent years learning what your old site was about. A careless redesign asks it to start over.
We rebuild a lot of older sites at Grayshaper. Hand-coded PHP and CodeIgniter builds, tired WordPress themes, Wix sites moving to Next.js. This is the process we follow so the new site keeps what the old one earned. It's not glamorous. Most of it happens in a spreadsheet.
First, find out what's actually bringing in traffic
Before anyone opens Figma, get a full list of every URL on the current site that matters. Not just what's in the menu. Old sites collect pages the owner forgot about: a 2019 blog post that still ranks, a PDF price list, a landing page from an ad campaign that ended years ago.
Pull from more than one place, because each one misses something:
Google Search Console. Open the Performance report, set the date to the last 16 months and export the Pages tab. Any URL with clicks or impressions goes on the list.
A crawl of the live site. The free version of Screaming Frog handles up to 500 URLs, which covers most small business sites.
Your XML sitemap, if you have one. It sometimes lists pages a crawler can't reach through links.
Backlinks. The Links report in Search Console shows which of your pages other sites link to. Those links carry real weight, and they all point at old URLs.
Analytics landing pages, for pages that get visits from places other than Google, like Facebook or email.
Merge it all, remove duplicates and sort by clicks. A typical local service business ends up with somewhere between 40 and 300 rows. The top 20 usually do most of the work. Those are the pages you protect no matter what.
Build the redirect map before you design anything
A redirect map is a two column sheet. Old URL on the left, new URL on the right. Every row with traffic or backlinks needs a home on the new site.
The rule is simple. Send each old page to the most similar new page, not the homepage. When fifty old URLs all redirect to the homepage, Google treats most of them like deleted pages (it calls them soft 404s), and whatever ranking they had goes with them.
Here's what that looks like in practice:
/services.php?id=4goes to/services/windshield-replacement/index.php/about-usgoes to/about/blog/2019/05/how-to-choose-a-dentistgoes to/blog/how-to-choose-a-dentistAn old "Spring Offer" page with backlinks goes to the current offers page, not the homepage
Doing this early matters because it shapes the design. If the map shows twelve city pages that each bring in calls, the new site needs room for twelve city pages. That's a navigation and sitemap decision. It's cheap to make in week one and painful to make the night before launch.
The URLs that trip people up
These come up again and again on older sites:
index.php in the URL. CodeIgniter and older PHP sites often serve the same page at
/index.php/contactand/contact. Google may have indexed both. Redirect both.Trailing slashes and capital letters. To Google,
/About-Us/and/about-usare two different pages. Pick one style for the new site and redirect every variant.Query string URLs like
?page_id=82on WordPress or?id=4on custom PHP. They're easy to miss in a crawl and often have years of links pointing at them.Images and PDFs. If a photo ranks in Google Images or a PDF menu gets downloaded every day, moving the file breaks that too.
Redirect chains. If the old site already sent A to B, and now you're sending B to C, update the first rule so A goes straight to C. Every extra hop is slower and leaks a little value.
Don't "clean up" pages that are ranking
This is where designers and SEO people argue, and the SEO side should win more often than it does.
A new site is a good excuse to tidy the copy. But a page sitting at position 3 for "emergency dentist in Dallas" is there for a reason. Usually its title, its H1, its headings and a good chunk of its text all say exactly what people search for. Rewrite it into something shorter and more "on brand" and you can lose that spot.
For the top pages on your list, keep these close to what they were unless there's a clear reason to change them:
The title tag and the H1
The main topic, and the words people actually search with
Roughly the same amount of useful text. If the old page had 900 words about crowns and bridges and the new one has 120 words and a big photo, expect a drop.
The URL itself, if you can. A redirect is good. Not needing one is better.
You can still make these pages better. Add real photos, an FAQ section, actual reviews, clearer buttons. Just add to what's working instead of throwing it out.
Carry over the invisible stuff
A lot of what helps a site rank never shows on screen, so it's the first thing left behind in a rebuild. Open the old site's source code and make a list:
Schema markup. LocalBusiness, Dentist, AutoRepair, FAQPage, Review. If the old site had it, the new one needs it too, ideally done better. Run both through Google's Rich Results Test.
Meta descriptions on pages with a good click through rate. Search Console shows you which ones.
Image alt text, especially on service and gallery pages.
Internal links. If old blog posts linked to your service pages and the new blog template drops those links, your service pages just lost support.
Tracking. Analytics, Google Ads conversion tags, Meta pixel, call tracking numbers. Losing these won't hurt rankings, but you won't be able to tell if the redesign worked.
Verification files for Search Console, Bing or anything else sitting in the root folder.
Launch day: the checks that catch most disasters
Most launch problems come from things that are fine on staging and wrong on the live site. Go through these in the first hour:
Remove noindex. Staging sites should be hidden from Google. Live sites shouldn't. It sounds obvious, and it's still the most common reason we see a brand new site disappear from search. Check the robots meta tag and robots.txt on a few real pages.
Test every redirect. Paste your list of old URLs into a bulk checker, or crawl them in list mode. Each one should return a 301 and land on a working page in one hop. Look for 404s and 302s.
Check canonical tags. They should point at the live domain, not staging. This one hides well because the page itself looks perfect.
Submit the new sitemap in Search Console and request indexing for your top ten pages.
Update your Google Business Profile website link if the URL changed. For local businesses this link matters a lot. Add a UTM tag so you can see GBP visits on their own in Analytics.
Test forms and call buttons on a real phone. Not the browser's mobile preview. A real phone, on mobile data.
If you're moving to a new domain as well, use the Change of Address tool in Search Console once the redirects are live. Keep the old domain registered and redirecting for at least a year. Longer is better.
What to expect in the first few weeks
Even a clean migration usually wobbles a little. Google has to recrawl the site, follow the redirects and work out that the new pages replace the old ones. A small dip in impressions for a week or two is normal. Don't start changing things on day three. You'll only make it harder to see what's going on.
Here's what to keep an eye on:
The Pages report in Search Console. Watch for a jump in "Not found (404)". Every one of those is a missing redirect. Fix them as they show up.
Performance, compared to the weeks before launch. Check your top pages one by one. If a specific page dropped and is still down after three or four weeks, put the old and new versions side by side. Something important got removed.
Calls and form fills. This is the number the business owner cares about, and it can go up even when rankings stay flat. A faster site with clearer buttons often turns the same traffic into more enquiries.
If you're still down after six to eight weeks, it's no longer a "wait and see" situation. Something got lost along the way. Go back to the redirect map and the old page copy and find it.
Questions people ask us about redesigns and SEO
Will a website redesign hurt my SEO?
It can, but it doesn't have to. Rankings usually drop because of broken URLs, deleted pages or rewritten content, not because the site looks different. With a proper redirect map and your top pages kept intact, most sites hold their positions, and many improve because the new site is faster.
How long does it take rankings to recover after a redesign?
After a clean migration, small dips usually settle within two to four weeks. A domain change takes longer, sometimes a few months. If you're still well down after two months, something was missed.
Should I use 301 or 302 redirects?
Use 301 for anything permanent, which is almost everything in a redesign. A 302 tells Google the move is temporary, so it may hang on to the old URL.
Can I change my URLs to make them cleaner?
Yes, as long as every old URL redirects to its new version. Clean URLs are nice but they don't do much on their own. If your current URLs are already readable, keeping them is the safer bet.
Do I need to keep all my old blog posts?
Keep any post that gets traffic or has links pointing at it. Posts with no clicks in the past year and no links can be merged into a better post or removed, with a redirect to the closest related page.
Planning a rebuild? Before you start, we're happy to look at your current site and tell you which pages you can't afford to lose. Book a call and have your Search Console access ready.
