Capture the current site
URLs, traffic, queries, backlinks, sitemaps and pages that must not be lost.
Migration and technical SEO
Changing domain, CMS, framework, URL structure or design can alter signals accumulated over time. The delicate part is not launch day itself: it is reaching it with a clear map of what must stay stable.
URLs, traffic, queries, backlinks, sitemaps and pages that must not be lost.
Redirects, canonicals, robots, rendering, internal links and HTTP responses verified immediately.
Errors, coverage, queries and pages checked until the move settles.
Not every page has the same value. Before launch I identify the parts carrying traffic, links or search signals that should remain connected.
When they change, they need a relevant destination.
Content and intent should not disappear just because the design changed.
They must point to the correct new versions, not staging or obsolete URLs.
Menus, breadcrumbs and contextual links can change the weight of important pages.
A migration is handled as a system change, not just a visual replacement.
Collect URLs, sitemaps, organic landing pages, existing redirects and useful Search Console and analytics data.
Highlight changed URLs, moved content, removed pages and differences in internal structure.
Prepare relevant destinations while avoiding chains and blanket redirects to the homepage.
Check canonicals, robots, noindex, sitemaps, structured data and rendering before go-live.
Immediately after launch, verify the most important URLs and the highest-risk errors.
The checklist is split because many migration errors can only be prevented before release.
We can cover pre-launch checks, redirect mapping and validation after publication.