JAM Digital / SEO
SEO migration checklist: what to check before, during and after launch
Plan a website migration with a practical checklist for URL mapping, redirects, launch checks and monitoring, with clear owners at every stage.
Before you dive in
The key points.
Establish the scope and baseline before changing URLs or platforms.
Assign ownership for mapping, redirects and launch checks.
Monitor the released site against the original baseline.
A website migration needs an SEO plan before development is finished. If URLs, navigation, content or the platform are changing, record what currently attracts visitors, decide where each useful page will go and agree how the move will be checked. This SEO migration checklist turns those decisions into a practical launch process.
The aim is to preserve useful journeys while improving the site. A new design alone does not tell you whether people can still find a service, follow an existing link or send an enquiry.
Establish the scope and baseline
Start by defining what is changing: domain, CMS, hosting, URL structure, content, design or several of these together. A hosting change with stable URLs needs a different plan from a redesign that removes half the pages.
Record a baseline before the move. Export landing-page performance from Search Console and analytics, crawl the existing site and retain a list of important pages. Identify pages with enquiries, valuable links or a clear role in the sales journey. Include PDFs and campaign landing pages where they matter.
For a telecommunications infrastructure business, that inventory might include technical documents and audience-specific service pages. Treat these as part of the customer journey, rather than assuming only navigation pages matter.
Build the URL mapping before launch
Give every important existing URL an explicit decision: retain it, redirect it to a relevant replacement, or retire it deliberately. A useful mapping sheet contains the old URL, proposed destination, action, owner and test result.
Avoid sending unrelated retired pages to the homepage. Choose the closest genuine replacement; where none exists, decide whether useful content should be retained or a proper removal response is appropriate. Test full URLs, including old links that already redirect, so the migration does not introduce unnecessary chains.
Google’s site-move guidance covers URL mapping, permanent redirects and monitoring. Use it alongside the requirements of your own platform.
Use a shared sign-off checklist
| Stage | Check | Suggested owner | Evidence to retain |
|---|---|---|---|
| Planning | Important pages and performance baseline recorded | SEO lead | Crawl and exports |
| Planning | URL mapping reviewed against new content | SEO and content leads | Approved mapping sheet |
| Staging | Titles, headings, canonicals and navigation checked | SEO lead | Crawl comparison |
| Staging | Forms, key journeys and measurement tested | Development and marketing | Test record |
| Launch | Redirects and important landing pages checked | Developer and SEO lead | Response checks |
| Launch | Production crawl controls reviewed | Developer | Robots and page checks |
| After launch | Organic landing pages and enquiries monitored | Marketing lead | Annotated reporting |
Name a person for each role. “The agency” or “the developers” is too broad when a time-sensitive decision needs an answer.
Check the release, not just the preview
Staging can behave differently from production. After release, test the actual public URLs, including redirect destinations, status codes, canonical tags and internal links. Confirm that production pages intended for search are not carrying staging restrictions. Keep staging protected separately.
Submit the appropriate sitemap through Search Console and inspect key pages. Test enquiry journeys as agreed with the business, including who receives submissions. An analytics event firing is useful evidence of instrumentation; it does not prove the sales team received a usable lead.
Keep a rollback decision and escalation contact ready. Define what would justify reverting the release and which issues can be repaired in place. Make that decision on business impact, rather than treating every ranking movement as an emergency.
Monitor the right changes
Check important pages and errors closely after launch, then compare performance over an appropriate period. Annotate the release in reporting and consider seasonality, campaigns and tracking changes before attributing every movement to the migration.
Google notes that search visibility can fluctuate during a move. A better monitoring plan combines technical checks, landing-page traffic and qualified enquiries. Investigate unexpected losses at page and query level, then assign a corrective action.
Plan the migration alongside the redesign
Use the website redesign checklist to agree the broader project and the website cost guide to understand scope. JAM Digital connects SEO planning with website development so the launch has clear priorities and responsibilities.
Your next steps
Put it into practice.
- Record important URLs, performance and project responsibilities.
- Prepare and review the URL mapping and redirects.
- Agree shared launch checks and sign-off.
- Verify the released site and monitor meaningful changes.
