The Short Version
Most ranking drops after a redesign come from a short list of avoidable mistakes: missing redirects, pages quietly removed, a robots.txt block left over from staging, and internal links still pointing at old URLs.
None of these are hard to prevent. They just need someone to own them before launch day, not after. This checklist covers what to record before you start, what to check on the staging site, what to do on launch day, and what to watch for the following 30 days.
This website redesign SEO checklist exists because of a call I get a few times a year. A business has launched a new website, it looks far better than the old one, and three weeks later the enquiries have dried up. When I open Search Console, the story is usually the same: dozens of old URLs returning 404, no redirects in place, and the pages that used to bring in leads simply gone.
The frustrating part is that the design agency usually did good work on the design. SEO just wasn't in the brief. So here's the checklist I give clients before a rebuild, in the order it needs to happen. Hand it to your designer or developer at the start, not the week before launch.
📉Context
Why Redesigns Lose Rankings
Google ranks pages, not websites. When a redesign changes a URL, deletes a page, or rewrites its content, Google has to work out again what that page is about and whether it deserves its old position. Some movement is normal. Google's own guidance on site moves with URL changes says to expect temporary fluctuation, and that for a medium sized site it can take a few weeks or more for new URLs to replace old ones.
A temporary wobble is fine. A lasting drop usually has one of these causes:
| Cause | How common in my audits | How it shows up |
|---|
| Old URLs with no redirect | Very common | 404 errors in Search Console, old pages vanish from results |
| Content cut during the redesign | Common | Pages still exist but rank lower because the text that matched searches is gone |
| Staging noindex or robots.txt block left on | Less common, very damaging | Whole site drops out of Google within days |
| Everything redirected to the homepage | Common on rushed launches | Old rankings disappear, homepage does not replace them |
| Slower templates | Occasional | Gradual decline, poor Core Web Vitals on new page groups |
The first two causes account for most of the damage I see. They're also the cheapest to prevent, because they're decided on paper before anyone writes code.
📋Step 1
Before the Designer Starts: Record What You Have
You can't protect what you haven't written down. Before the old site changes, export these and save them somewhere the whole team can find:
- A full list of current URLs. Use your XML sitemap, a crawl of the site, and the Pages tab in Search Console. Sitemaps often miss old pages that still get traffic, so don't rely on them alone. If you're not sure your sitemap is complete, my guide to XML sitemaps explains what it should contain.
- Search Console performance by page for the last 12 months. This tells you which pages earn clicks and must be protected at all costs.
- GA4 landing pages with key events. Some pages bring few visits but most of your enquiries. Those matter more than traffic totals suggest.
- Pages with backlinks. Search Console's Links report shows which pages other sites link to. Losing those without a redirect throws away links you may have spent years earning.
- Page titles, meta descriptions and headings for your top 20 pages. Redesigns often replace carefully written titles with something generic like "Services".
For a typical Malaysian SME site with 30 to 150 pages, this takes a morning. It's the most valuable morning of the whole project.
💡
Mark your protected pages
From those exports, mark the 10 to 20 pages that bring in most clicks, leads or links. Tell the designer these pages keep their URL, their main heading topic and most of their text unless there's a strong reason to change them. Everything else has more flexibility.
🔀Step 2
The Redirect Map
If you only do one thing from this list, do this. A redirect map is a spreadsheet with two columns: every old URL, and the new URL it should send visitors to. Your developer then turns it into permanent redirects on the server.
The rules I follow
- Use permanent server side redirects. Google recommends 301 or 308 redirects and says permanent redirects don't cause a loss in PageRank.
- Redirect to the closest equivalent page. Old service page to new service page, old blog post to the same post at its new address.
- Don't send everything to the homepage. Google specifically warns against redirecting many old URLs to one irrelevant page such as the home page. It tends to be treated like a missing page.
- Avoid chains. If a page was already redirected once in the past, point the original URL straight at the final new URL.
- Let true junk go. Old test pages, expired promotions and empty tag pages can return 404 or 410. Not every URL needs a home.
- Keep redirects in place. Google's guidance is to keep them as long as possible, generally at least a year. I tell clients to keep them indefinitely.
A note on WordPress
Most redesigns I see in Malaysia are WordPress to WordPress, often with a new theme or page builder. The risk there is quieter: permalink settings change, category bases appear in URLs, or pages are rebuilt as new posts with new slugs. Check the URL of every protected page on staging against your list. If WordPress is your platform, our WordPress SEO page covers the usual traps in more detail.
🔧Step 3
Checks on the Staging Site
The staging site is the test version before launch. It should be blocked from Google while you work on it, which is exactly why problems slip through: the block that protects staging is the same block that destroys rankings if it goes live.
| Check | What good looks like |
|---|
| Protected pages | Same URL (or a mapped redirect), similar heading and most of the useful text kept |
| Titles and meta descriptions | Carried over or improved, never left as theme defaults |
| Heading structure | One clear H1 per page, logical H2s. See my guide to heading tags |
| Internal links | Menus, footers and body links point to new URLs directly, not through redirects |
| Canonical tags | Each page has a self referencing canonical pointing to its live URL, not the staging domain |
| Structured data | Organisation, breadcrumb and FAQ markup carried over and matching visible text |
| Speed on mobile | Key templates tested on a mid range phone connection, not just office Wi Fi |
| Tracking | GA4 and Google Tag Manager installed, enquiry forms firing key events |
Pay attention to the canonical row. I've seen launches where every page's canonical tag still pointed to the staging subdomain, which tells Google the real page lives somewhere it can't access. It's a one line fix, but only if someone looks.
If your redesign is also meant to fix deeper problems, the wider website design and SEO strategy post covers how to plan the structure itself. This checklist is narrower: it's about not breaking what already works.
🚀Step 4
Launch Day
Pick a quiet day. For most B2B firms that means avoiding month end and the days before a big campaign. I'd also avoid the week of a major public holiday in Malaysia, when your team is less likely to notice problems quickly.
It's also worth glancing at Google's Search Status Dashboard before you go live. Google listed a September 2026 spam update starting on 24 September, and it ran into early October. If you relaunch in the middle of a confirmed update, you won't be able to tell whether a drop came from your redesign or from Google. A week's delay is cheap compared with weeks of guessing.
On the day itself, work through this list in order:
- Remove the staging noindex tag and replace the staging robots.txt with the live one.
- Load your redirect map and test 20 old URLs by hand, including your protected pages.
- Submit the new XML sitemap in Search Console.
- Use URL Inspection on your five most important pages and request indexing.
- Submit a test enquiry through every form and confirm it arrives and is tracked.
- Update your Google Business Profile website link if the URL changed. My Google Business Profile guide shows where to find it.
If you're changing domain as well, for example from a .com to a .com.my, Search Console's Change of Address tool applies. You don't need it for a move from HTTP to HTTPS or between www and non www on the same domain.
📅Step 5
The First 30 Days
Most problems show up in the data within a fortnight. This is the schedule I follow for clients:
| When | Check | Red flag |
|---|
| Day 1 to 3 | Crawl the live site; check robots.txt and noindex again | Any important page blocked or returning an error |
| Week 1 | Search Console Pages report and 404 errors | Old URLs showing as not found that should have redirected |
| Week 2 | Performance report, compare with the same period before launch | Protected pages losing most of their clicks |
| Week 3 | GA4 key events by landing page | Enquiries falling while traffic holds steady |
| Week 4 | Core Web Vitals and mobile usability | New page groups marked Poor |
Don't panic over small changes in week one. Some fluctuation is expected and normal. What you're looking for is a pattern: a group of pages falling together, or one important page disappearing completely. Those almost always have a specific cause you can find and fix.
Also check how your pages appear in AI answers once things settle. AI Overviews draw their supporting links from pages in Google's index, so pages that lost rankings often lose AI visibility too. My piece on how to measure AI search visibility explains the Search Console report that shows this.
⚠️
When to call for help
If clicks are still down by a large margin after four weeks and you can't find missing redirects or blocked pages, get a proper SEO audit before making more changes. Rewriting pages in a panic usually makes the diagnosis harder.
Who Should Own This
The checklist is simple. The hard part is ownership. Designers own how the site looks, developers own how it works, and usually nobody owns whether it still ranks. Before your project starts, name one person responsible for the redirect map, the staging checks and the 30 day review. It can be someone in house, your developer, or an outside consultant.
If you'd like a second pair of eyes, I review redirect maps and staging sites as part of technical SEO work. Whoever does it, do it before launch. Fixing a redesign afterwards is always slower and more expensive than getting it right the first time.
Frequently Asked Questions
Will a website redesign affect my Google rankings?
It can. Changing URLs, removing pages or cutting content forces Google to reassess those pages. Google says some temporary fluctuation is normal during a move. Lasting drops usually come from missing redirects, deleted content or a leftover staging block, all of which can be prevented with planning.
How long does it take rankings to recover after a redesign?
If redirects and content were handled properly, most small and medium sites settle within a few weeks. Google notes that larger sites take longer. If clicks are still well below normal after four to six weeks, look for a specific cause such as missing redirects or blocked pages.
Do I need to keep the same URLs when I redesign my website?
Keeping URLs for your most important pages is the safest option. If URLs must change, set up a permanent 301 redirect from each old URL to its closest new equivalent. Avoid redirecting many old pages to the homepage, which often ends up treated much like a missing page.
How long should I keep 301 redirects after a redesign?
Google recommends keeping redirects as long as possible, generally at least one year. In practice I advise clients to keep them indefinitely. Other websites, old emails and bookmarks keep sending people to old URLs for years, and removing the redirects breaks those visits.
Should SEO be included in my website redesign quotation?
It should at least be in the brief. Ask your designer who will create the redirect map, carry over titles and meta descriptions, and check robots.txt and noindex settings at launch. If nobody is named, budget for an SEO review before launch rather than a recovery afterwards.
Is it better to redesign my website in stages?
For larger sites, often yes. Google advises changing one thing at a time where possible, so moving domain, platform and design all at once makes problems harder to trace. For a small SME site a single launch is usually fine, provided the checklist is followed.
