Entry 002 · 6 min
Migration Recovery Starts With URL Intent
A recovery plan is less about moving pages and more about preserving the job each old URL was doing.
When organic traffic drops after a migration, the visible symptom is usually a chart. The useful questions live one layer below it.
Which URLs used to earn demand? What intent did each one satisfy? Where does that intent resolve now? A technically valid redirect can still be strategically wrong when it sends a specific page to a generic destination.
Reconstruct the old system
For the InsideVVIP recovery, I started by treating the legacy site as a dataset. Historical URLs, clicks, templates, images, internal links, and current response states had to be reconciled before the new build could be trusted.
The work becomes clearer when each legacy URL is placed into one of a few decisions:
- preserve the page and improve it
- consolidate it into a stronger destination
- redirect it to the closest equivalent intent
- retire it deliberately
That mapping is the actual migration plan. The framework, CMS, and image pipeline matter, but they cannot compensate for a missing intent map.
Recovery is a system property
The new site also has to make the recovered value durable. Fast templates, consistent metadata, canonical rules, image handling, internal links, and validation all contribute.
I prefer to make those rules part of the build so the site does not depend on someone remembering every SEO detail for every future page.