Website Migration Without Losing SEO: 2026 Checklist
Founder & Lead Developer, Codingclave · 200+ projects since 2017
The Redesign That Cost a Business Half Its Enquiries
A business launches a new website. It is faster, it looks far better, and everyone is pleased.
Six weeks later, enquiries have halved. Nobody connects the two events immediately, because the new site is clearly better. Eventually someone checks Search Console and finds that a hundred pages which used to rank are returning 404s, and the URLs changed without redirects.
This is the most preventable failure in web development, and it happens constantly — because redesigns are managed as design projects with a launch date rather than as migrations with a risk plan.
I'm Ashish Sharma, founder of Codingclave. We do website development and replatforming for Indian businesses, including cleaning up after migrations that went badly. This is the checklist we work through, and the four mistakes that cause most of the damage.
The Four Mistakes That Cause Most Losses
1. URLs changed without redirects
The single largest cause. Your old page ranked, had inbound links, and had accumulated authority over years. The new site puts that content at a different address, and the old address returns a 404.
Every ranking signal that pointed at the old URL now points at nothing.
Prevention: a complete redirect map, built before launch, tested before launch.
2. Content became thinner
A redesign focused on visual cleanliness frequently removes text. That 1,500-word service page becomes an elegant 300-word page with generous whitespace.
It ranked because of what it said. Now it says less, and it ranks accordingly.
Prevention: compare word count and topical coverage page by page against the old site for anything that had traffic. If content is being cut from a ranking page, that needs a deliberate decision, not a design instinct.
3. Staging blocks deployed to production
Development sites are blocked from search engines. Someone forgets to remove the block, and the live site tells search engines not to index it.
This one is almost comically simple and genuinely common, and it can take weeks to notice.
Prevention: first item on the launch-day checklist, verified by a second person.
4. Internal linking rebuilt badly
The old site linked from the homepage to key service pages and between related content. The new navigation is cleaner and links to fewer places, leaving important pages reachable only through a sitemap.
Prevention: check that every page which mattered still has internal links pointing to it, ideally from more than one place.
Before You Start: Decide What Actually Changes
Migration risk scales with how much changes at once. Be deliberate.
| Change | Risk | Advice |
|---|---|---|
| Design only, same URLs and content | Low | Safest possible redesign |
| Design plus content rewrite | Medium | Protect ranking pages specifically |
| Platform change, same URLs | Medium | Achievable more often than people assume |
| URL structure change | High | Only with a real reason and a complete redirect map |
| Domain change | High | Requires careful sequencing |
| Everything at once | Very high | Split into phases if at all possible |
The advice that saves the most trouble: do not change URLs unless you have to. A tidier structure is rarely worth the exposure by itself. When a platform forces the change, accept it and plan properly. When it is a preference, decline it.
And avoid changing domain, structure and content simultaneously. If something goes wrong you will not know which change caused it.
Pre-Launch Checklist
Work through this before launch day, not on it.
Capture a baseline
You cannot detect a problem without knowing what normal looks like.
- Crawl the existing site and export every URL
- Export Search Console data — queries, pages, clicks and impressions for the last several months
- Export analytics — landing page traffic and conversions
- List your top pages by organic traffic, by conversions, and by inbound links. These are your protected set
- Record current rankings for your priority keywords
Do this before anything changes. Reconstructing a baseline after launch is not possible.
Build the redirect map
A spreadsheet: every old URL, its new destination, and the reason.
Rules that matter:
- Redirect to the closest equivalent page, not the homepage. A blanket homepage redirect signals that the specific page is gone
- Use permanent redirects for permanent moves
- Avoid chains. Old URL to new URL directly, not through two intermediate hops
- Include every URL variant you have used — with and without trailing slashes, old parameter forms, previously redirected URLs
- Where no equivalent exists, decide deliberately: recreate the content, redirect to the closest parent, or let it go with a proper 404. Do not force an irrelevant redirect
Test the map before launch against your protected set of pages.
Protect the content that earns
For every page in your protected set, compare the new version against the old: word count, headings, the terms it ranked for, its title and meta description.
If the new version is materially thinner, that is a decision to make consciously. A cleaner page that ranks nowhere serves nobody. Our guide on why Indian business websites do not generate leads covers balancing design against substance.
Check the technical foundations
- Titles and meta descriptions carried over or deliberately improved
- Canonical tags pointing at the right URLs
- Structured data preserved — losing article, product or FAQ markup loses rich results
- Image alt text carried over
- XML sitemap generated from the new URLs
- Robots rules correct for production
- Mobile rendering verified on a real mid-range phone
- Page speed measured, not assumed — a redesign that looks lighter can easily be heavier
Launch Day
A short list, in order, with someone accountable for each.
- Remove staging crawl blocks. Verify twice.
- Deploy redirects and spot-check your protected pages manually.
- Verify canonical tags on live pages.
- Submit the new sitemap in Search Console.
- Confirm analytics and conversion tracking fire. Broken tracking on launch day means a blind first week.
- Crawl the live site immediately and look for 404s, redirect chains and missing titles.
- Test the primary conversion paths — forms, WhatsApp buttons, phone links. A perfect SEO migration with a broken enquiry form is still a failure.
Point seven is the one people skip because it is not an SEO task. It is where the actual money is.
The First Month
Migrations are judged over weeks, not on launch day.
Days 1-3. Watch Search Console for crawl errors and spikes in 404s. Fix immediately — early fixes cost far less than late ones.
Week 1. Expect fluctuation; this is normal and not a reason to panic or to start reverting things. Watch that indexed pages are rising rather than falling.
Weeks 2-4. Compare organic clicks by landing page against the same period before launch. Totals alone will hide the case where new pages gained while your most valuable pages lost.
Month 2. Rankings should be stabilising. Anything still down needs individual investigation — usually a missing redirect, thinner content, or lost internal links.
What to watch throughout:
| Signal | Healthy | Investigate |
|---|---|---|
| Crawl errors | Near zero after a few days | Rising or persistent |
| Indexed pages | Returns to previous level | Materially lower |
| Organic clicks by page | Stable or recovering | Sustained drop on protected pages |
| Average position | Fluctuates then settles | Steady decline over weeks |
Special Cases
Domain change. Higher risk. Keep the old domain and its redirects in place indefinitely — do not let the registration lapse, or every inbound link you have ever earned dies at once.
HTTP to HTTPS. Redirect every HTTP URL to its HTTPS equivalent, update internal links to absolute HTTPS, and check for mixed content.
Platform change. Frequently forces URL structure changes. Investigate whether the new platform can preserve your existing structure before accepting that it cannot. Our guide on migrating WordPress to Next.js covers a common Indian case, and WordPress vs custom website covers the decision itself.
Consolidating multiple sites. Map every page from every site, decide which version of duplicated content survives, and redirect the rest to it.
Local businesses. Update your Google Business Profile website link and any citations pointing at old URLs. For location-heavy sites, verify every location page survived with its own URL rather than being folded into one page.
Who Should Own This
The most common structural mistake is treating migration as the developer's job.
Developers build the new site. Whether the migration preserves rankings depends on decisions about content, URLs and priorities that need someone thinking about search and about conversions.
Assign explicit ownership of the redirect map, the protected page list and the post-launch monitoring. If nobody owns those three things, they get done partially, at the end, by whoever has time.
If you are commissioning a redesign, ask the agency directly: who builds the redirect map, when is it tested, and who monitors Search Console for the first month? An agency without a clear answer is not planning a migration, they are planning a launch. Our how to choose a web development company guide covers what else to ask.
Related Reading
- Website redesign guide
- Migrate WordPress to Next.js
- Why Indian business websites do not generate leads
- SEO for small business
- Website maintenance guide
- How to choose a web development company
Founder note: the cheapest insurance in any redesign is a spreadsheet of your top fifty pages by organic traffic, checked one by one on the new site before launch. It takes an afternoon and it prevents the failure that costs businesses months. WhatsApp me on +91 92771 84741 if you want a second pair of eyes before you go live.
Frequently asked questions
Almost always because URLs changed without redirects, page content became thinner than what previously ranked, the staging site's blocking rules were carried into production, or internal linking was rebuilt in a way that stranded important pages. All four are preventable, and all four are common because redesigns are usually managed as design projects rather than as migrations.
A well-executed migration with correct redirects usually sees temporary fluctuation for a few weeks and then stabilises. A migration with broken redirects or lost content can take months to recover, and some rankings may not return at all if competitors have moved into the gap. Recovery time depends far more on how quickly problems are found and fixed than on the size of the site.
You need them for every old URL that had traffic, rankings or inbound links, mapped to the closest equivalent new page. Redirecting everything to the homepage is a common shortcut and a serious mistake, because search engines treat a homepage redirect for a specific page as effectively removing that page. Where no equivalent exists, it is better to keep a genuine page than to force an irrelevant redirect.
Only if there is a real reason. Changing URLs is the single largest source of migration risk, and a cleaner URL structure is rarely worth the exposure on its own. If you are changing platforms and the new one imposes a different structure, plan the redirect map carefully. If your current URLs work, keeping them removes most of the risk from the project.
Removing the staging site's crawl blocking before launch. Development sites are typically blocked from search engines, and that blocking gets deployed with everything else, making the live site invisible. It is trivially easy to do and can take weeks to notice if nobody checks, which is why it belongs at the top of the launch-day checklist rather than somewhere in the middle.
Watch three things for the first month: crawl errors in Search Console, which should be near zero after the first days; indexed page count, which should return to roughly the previous level; and organic clicks by landing page compared to the same period before launch. Comparing totals alone hides the case where new pages gained while your most valuable pages lost.