How We Migrated ISDM's 22-Page Site to Webflow Without Losing a Single Search Ranking

ISDM — the Indian School of Development Management — came to us with a specific problem and a hard deadline. They needed to move their website to Webflow. But their site had twenty-two pages, thousands of articles published over years, and enough accumulated SEO equity that losing it would genuinely hurt enrolment. The deadline wasn't flexible.

This is the kind of project that separates agencies who understand SEO from those who treat it as an afterthought. We'd done migrations before, but not at this content volume, not with this much at stake. Here's what we did.

The brief

ISDM runs programmes in development management — social sector leadership, policy, organisational change. Their audience is working professionals and recent graduates looking for a credible postgraduate qualification. Most of their organic traffic comes from people researching the school, the programmes, and development management as a field.

The existing site was on a custom CMS that had become difficult to update, slow to load, and visually dated. Moving to Webflow would give their team direct control over content. But the articles — admissions guides, faculty profiles, programme descriptions, research papers — had been indexed for years. Some of them ranked well for specific queries relevant to their audience.

The task wasn't just to migrate the site. It was to migrate it without triggering the ranking drops that make migration horror stories.

The challenge: scale

Twenty-two pages sounds manageable. But ISDM also had thousands of articles nested within those pages — programme guides, event recaps, research publications, faculty content. Each one was a URL. Each URL had a ranking history. Each one needed to be mapped, accounted for, and redirected correctly.

A missed redirect at that volume isn't a minor SEO inconvenience. It's hundreds of URLs returning 404s, all of which had accumulated some degree of link equity and ranking signal. Google would see them as a mass of broken content and devalue the domain accordingly.

The approach

We started with a full crawl of the existing site before touching anything. Every URL, every title tag, every meta description, every canonical — exported and documented. We cross-referenced this against Search Console to identify which URLs had meaningful impression volume, so we knew which ones were highest priority to get right.

Then we built the redirect map. For content keeping the same URL structure, the redirect map was essentially a confirmation list. For content being reorganised — programme pages moved to a new hierarchy, research articles consolidated into a new archive — every individual URL had an explicit destination.

The Webflow build ran in parallel on a password-protected staging environment, blocked from indexing. As pages were built, content was migrated article by article, with metadata verified for each one. Not bulk-imported and assumed correct — individually checked, because bulk imports have formatting errors and metadata gaps that only show up when you look at the specific page.

Pre-launch: what we tested

Every redirect in the map, tested on staging with a status code checker — 301 confirmed, destination URL correct, no redirect chains (A → B → C causes a small ranking penalty that accumulates). All metadata populated and matching the original. Sitemap generating correctly. No noindex tags left on pages that should be indexable. GA4 firing on page load. All forms routing to the correct inboxes.

We also did a soft launch test: pointed a subdomain at the live Webflow build and ran it through Google's URL Inspection tool to verify how it would be interpreted before full DNS cutover.

The result

The migration completed in 60 days. Zero ranking loss on the pages that mattered. Search Console showed no unexpected 404 spikes, no coverage drops, no impression collapses on their top-ranking URLs. The two edge cases we caught in the 30-day post-launch monitoring window were minor and fixed within 48 hours.

ISDM's team now manages their own content in Webflow — publishing programme updates, research articles, and news without a developer in the loop. The site loads faster. The design matches where the institution is now, not where it was when the last site was built.

What this means for your migration

The difference between a clean migration and a messy one is almost entirely in the preparation. The redirect map, the metadata export, the pre-launch testing — none of this is technically complex, but all of it requires discipline and time. Agencies that quote fast and cheap on migrations usually skip the documentation phase. That's where the ranking drops come from.

If you're planning a migration, book the free audit call. We'll look at your current site, estimate the redirect volume, and tell you where the complexity actually is in your specific situation.

‍