URL mapping, not guesswork
We build an explicit map from every meaningful old URL to its new equivalent — product pages, category pages, blog/content pages, and any custom landing pages. Pages with no clean equivalent get a documented decision, not a silent 404.
Redirects and metadata
301 redirects are implemented on the new platform before launch, and we carry over metadata (titles, descriptions, canonical tags) where it's genuinely still accurate for the new URL. We check for redirect chains and loops rather than assuming a one-to-one map is clean.
What we can and can't promise
We can't guarantee specific rankings — no one honestly can, since ranking depends on many factors outside any migration. What we do control, and treat as a hard requirement, is URL continuity: that old links and bookmarks resolve to the right new page instead of a dead end.
Frequently asked questions
How can migration risk to Google rankings be reduced?
Accurate URL mapping, one-hop redirects, consistent canonicals, updated internal links and post-launch monitoring are important controls. We treat them as core deliverables, but cannot guarantee specific positions because rankings depend on factors beyond the migration.
What happens to pages that don't exist on the new platform?
We flag them during the mapping phase and agree with you on the best redirect target — usually the closest matching category or a relevant hub page, rather than a generic redirect to the homepage.
Do you update internal links, not just external redirects?
Where practical, yes — internal links pointing to old URL patterns get updated as part of the migration, since redirect chains add latency and dilute link value.