Topics: Website design & costs, SEO & AI search
Want this done for your business? Get a fixed quote or book a free 30-minute call.
Quick answer: Before the old site comes down, record every URL with its traffic and backlinks, then point each changed URL to its closest new equivalent with a 301 redirect. On launch day, remove staging noindex tags and confirm that analytics, Meta Pixel and conversion tags fire. Then compare Search Console and enquiry numbers with your baseline every week for a month.
A redesign is the one website project where you can spend good money, end up with a better-looking site, and receive fewer enquiries than before. It rarely happens because the new design is worse. It happens because pages that ranked quietly disappeared, redirects were never set up, or the tags that fed your Google and Meta campaigns stopped firing on launch day. All of it is preventable with a checklist and a few hours of preparation.
Why do rankings drop after a website redesign?
Rankings drop when Google can't connect the old pages to the new ones, or when the new pages say less than the old ones did.
| Cause | How it shows up | How to prevent it |
|---|---|---|
| URLs changed with no redirects | Old URLs return 404 errors; backlinks lead nowhere | A complete 301 redirect map |
| Ranking content deleted | Traffic falls on specific queries | Audit what ranks before cutting pages |
| Noindex carried over from staging | Pages drop out of the index entirely | Launch-day check of meta tags and robots.txt |
| Internal links lost | Key pages buried after a navigation change | Map menus and in-content links to priority pages |
| Slower pages | Worse experience on phones, fewer conversions | Test speed on staging before launch |
| Titles and headings rewritten | Relevance for main queries weakens | Carry over or improve titles for top pages |
| Tracking tags missing | Ads keep spending while reported leads fall | Tag inventory and launch-day test conversions |
The last row isn't an SEO problem, but it is the one most often missed. When conversion tags break, Google Ads and Meta keep spending and their automated bidding optimises on missing or wrong signals. Because the ads still run, nobody notices for days.
What should you record before the old site comes down?
Capture a complete snapshot of what the old site has earned, because once it's gone you can't measure what you lost.
- [ ] Every URL. Crawl the old site with a tool such as Screaming Frog (the free version crawls up to 500 URLs) and export each URL with its title, meta description, main heading, canonical and status code.
- [ ] Top pages and queries. Export the last 16 months of pages and queries from Google Search Console, the longest period it keeps.
- [ ] Pages with backlinks. Use the Links report in Search Console to list pages other sites link to.
- [ ] Conversion baseline. Record monthly enquiries by type (forms, calls, WhatsApp clicks, bookings) and which landing pages produce them.
- [ ] Priority rankings. Note where you rank for 20 to 30 searches that bring in business.
- [ ] Tracking inventory. List every tag and integration: GA4, Google Ads conversion tags, Meta Pixel and Conversions API, call tracking, chat widgets and form-to-CRM connections.
- [ ] Structured data. Note which pages carry schema markup and of what type.
- [ ] Files that get traffic. PDFs, images and downloads people link to or find in search.
- [ ] A full backup. Keep a copy of the old site you can reach after launch.
How do you build a redirect map that keeps rankings?
Map every old URL that changes to its single closest equivalent on the new site, using permanent 301 redirects. The best redirect is the one you don't need, so keep URLs unchanged wherever the new structure allows.
Rules that keep rankings intact:
- One-to-one. Each old page points to the new page that best matches its content.
- Never everything to the home page. Google tends to treat mass redirects to an unrelated page as if the old page had simply disappeared.
- No chains. If older redirects already exist, update them to point straight to the final URL rather than hopping through several.
- Cover the variants. Include http and https, www and non-www, and trailing-slash versions.
- Include files. Redirect PDFs and images that get traffic or links.
- Keep them long-term. Google's site-move guidance recommends keeping redirects for as long as possible, generally at least a year. In practice, leave them in place.
A redirect map is just a spreadsheet:
| Old URL | New URL | Reason |
|---|---|---|
| /services/ac-repair.html | /services/air-conditioner-repair/ | Page renamed |
| /2021/05/maintenance-tips/ | /blog/ac-maintenance-tips/ | Blog structure changed |
| /monsoon-offer/ | /services/air-conditioner-repair/ | Retired offer; closest relevant page |
| /team.php | /about/ | Pages merged |
Before launch, run the full list of old URLs through the redirects on staging and confirm each one ends at a live page.
What must you check on the staging site before launch?
Check the things that only go wrong at the moment of switching over: indexing settings, canonicals, metadata and tracking. Build these checks into the project plan rather than leaving them for launch night; our walk-through from brief to launch in six weeks shows where they fit.
Search essentials:
- [ ] Staging is password-protected or noindexed, and the plan says exactly who removes that at launch
- [ ] robots.txt on the live site allows crawling
- [ ] Canonical tags point to the live domain, not staging
- [ ] Titles, descriptions and headings for your top pages are carried over or improved
- [ ] Structured data is present and passes Google's Rich Results Test
- [ ] Internal links point directly to new URLs, not through redirects
- [ ] The XML sitemap lists only live, indexable new URLs
- [ ] Mobile speed holds up; our Core Web Vitals explainer covers what to test
Tracking essentials:
- [ ] GA4 is installed with key events for form submissions, calls and WhatsApp clicks
- [ ] Google Ads conversion tags fire on the right actions; our conversion tracking setup guide explains how to test them
- [ ] Meta Pixel and Conversions API events fire once each, without duplicates
- [ ] Forms deliver to the inbox and the CRM, and thank-you pages or events still exist
- [ ] Call tracking numbers display correctly
What should you monitor in the first 30 days after launch?
Watch for errors daily in the first week, then compare traffic and enquiries with your baseline weekly. Some fluctuation is normal while Google processes the changes; steady declines on specific pages are not.
| When | What to check |
|---|---|
| Launch day | Crawl the old URL list; submit the new sitemap; inspect key pages in Search Console; send test enquiries and confirm they appear in GA4, Google Ads and Meta Events Manager |
| Days 2–7 | The Pages report and server logs for new 404s; fix missing redirects the same day |
| Weeks 2–4 | Clicks and impressions for top pages against the baseline; priority rankings; enquiries by type; conversions reported in ad platforms |
| Day 30 | A short written review: what dropped, what improved, what's still open |
What if rankings have already dropped after a redesign?
Restore missing redirects and content first, then rebuild internal links. Most recoveries come from undoing specific losses rather than from new SEO work.
- Find the losers. In Search Console, compare pages before and after launch and sort by lost clicks.
- Check the old URLs. If they return 404s, add 301s to the closest new pages.
- Restore content that ranked. Sections, FAQs and detail that were cut for a cleaner design often carried the rankings. Put the substance back, even if the layout is new.
- Check indexing settings. Look for leftover noindex tags, wrong canonicals and robots.txt blocks; our checklist for when a website isn't showing on Google covers each one.
- Rebuild internal links. Link to recovered pages from the menu, home page and related content.
- Fix tracking. Make sure the numbers you're judging recovery by are actually being recorded.
- Request indexing for repaired pages, then give it a few weeks before judging.
Frequently asked questions
Will a website redesign hurt my SEO?
It doesn't have to. Drops usually come from changed URLs without redirects, deleted content or indexing settings left over from staging. Record what the old site ranks for, redirect every changed URL and check the launch carefully, and a redesign can improve rankings.
Do I need 301 redirects if I keep the same domain?
Yes, for every URL that changes. Keeping the domain protects your brand searches, but Google ranks individual pages, and a renamed page is a new URL. Without a redirect, the old page's rankings and backlinks are lost.
How long do rankings take to recover after a redesign?
If the cause is fixed promptly, many sites recover within a few weeks; larger sites and bigger structural changes take longer. There's no guaranteed timeline, which is why it pays to prevent the drop rather than recover from it.
Should I change my URLs during a redesign?
Only when there's a clear benefit, such as replacing messy URLs with readable ones or restructuring a confusing site. Every changed URL needs a redirect and carries some short-term risk. If the current URLs are clean, keep them.
What should I check the day a new website goes live?
Confirm noindex tags are gone and robots.txt allows crawling, test the redirects from your old URL list, submit the new sitemap, and send test enquiries to check analytics, Google Ads and Meta tracking. Then check that forms reach your inbox and CRM.
Plan the launch before you design the pages
We plan website redesigns that keep rankings, and we write the URL inventory, redirect map and tracking checks into the scope before any design work starts. Tell us about your current site or book a free call to plan your redesign.