Move to Next.js. Keep every ranking you've earned.

A two-to-four week wobble while Google reprocesses the new URLs is normal even on a clean migration. What isn't normal is a decline that doesn't recover by week six — that means URLs were genuinely lost, which is what the URL inventory and redirect map at the start of the process exist to prevent.

Two to four weeks depending on how many pages and post types the site has. Sites with a large blog or heavy shortcode use on the content side take longer to extract cleanly than they do to rebuild.

We keep it reachable for a period after cutover if the redirects are served there, and only decommission it once the coverage report and top-page traffic have been watched through the reprocessing window.

Yes. Every migration ships with the same admin panel that comes with a new build — you edit pages, prices and blog posts yourself, with no developer in the loop for routine changes.

Every shortcode gets found and triaged before the build starts — rebuilt as a React equivalent where it's load-bearing, converted to static markup where it isn't. Scope and cost depend on what your specific plugin stack is actually doing, so this gets confirmed in the scoping call rather than assumed upfront.

Not always. If the complaint is just that the site feels slow, that's often a cheaper fix — caching, image optimisation, trimming plugins. A migration earns its cost when the site is becoming an application, plugin debt has made changes genuinely risky, or performance is measurably costing conversions. We'll tell you if you don't need one.