Moving a website is one of those projects where every extra change multiplies the risk. it's like trying to tune an engine while it's still running at full speed - the more variables you introduce, the harder it is to diagnose what went wrong when traffic drops. This is why I always tell startups to treat the migration as a surgical move, not a redesign opportunity.
From a macroeconomic perspective, the cost of a botched migration is a regression in growth compound. Two months of flat traffic can easily set you back a quarter's worth of revenue targets. So the principle of minimal change isn't just technical pedantry - it's a growth strategy.
A few things I've found critical when dealing with platform shifts:
Start by crawling the current site with something like Screaming Frog. The crawl comparison feature is gold - you can run it on both old and staging sites side by side and spot everything from missing meta tags to broken internal links in one pass. Most of the points below can be checked there.
keep URLs identical if humanly possible. If not, make sure 301 redirects are mapped page-for-page, not just category-level. And don't delete the old XML sitemap immediately - keep a separate one with old URLs live for a month post-migration so Google can follow the redirects. WordPress users often rely on a plugin for the sitemap, be aware that when you switch DNS, that plugin might vanish unless you've planned for it.
titles and H1s should stay the same. If you're rewriting content at the same time, you're increasing risk unnecessarily. Same goes for content pruning - migrations are the worst time to cut pages. Keep the inventory identical, you can trim later when you have stable data.
for each page, ensure the number of internal links isn't reduced. Screaming Frog's inlinks/outlinks comparison will show you that. Image alt tags and schema markup: copy exactly unless they were poorly optimised from the start.
On the technical side, Next.js sites can be tricky. You must confirm that all metadata, content, and internal links appear in the rendered HTML - not just in JavaScript. Use the Rich Results test tool, click "View tested page," and check the HTML tab. Meta data should live inside the <head> tags, Next.js sometimes injects it into the body for speed. And ideally serve via server-side rendering (SSR), not client-side, because many search crawlers and AI bots still struggle with JS.
Finally, indexation status per URL should remain consistent. Check canonicals, robots tags, and any robots.txt entries that still apply. page speed should match or beat the current site - no regression there.
Keep the number of moving parts low. that's the only way to isolate the cause if something goes wrong.
