Technical SEO
Website Migration SEO Plan: Responsibilities and Checks
Before moving a website, record what will change, where existing pages and assets will go and who will carry out the work.
The short answer
Before moving a website, record what will change, where existing pages and assets will go and who will carry out the work. Agree on the tests and problems that would stop launch. Approving the design alone does not make the move ready.
On this page
Build the migration plan before making irreversible changes. This guide provides a planning model, not a claim that a migration has been performed or that rankings can be protected without uncertainty.
Distinguish the type of move
| Change | If URLs stay the same | If URLs change |
|---|---|---|
| Domain | Usually not the defining condition of a domain move | Map the old addresses and plan the domain transition |
| Paths/URL structure | Check whether the change is only presentation | Map old resources to the appropriate new destinations |
| Platform | Check content, functions, output and access after the rebuild | Add URL and asset mapping to the platform checks |
| Hosting | Plan server, availability and production-response checks | Resolve the hosting and URL transition as separate workstreams |
Google’s URL-change guidance and its hosting-move guidance treat different conditions. Do not copy a redirect checklist into a host-only move and assume the project is covered.
List your pages and map their destinations
The following paths are fictional. They illustrate decisions; they are not links or instructions to alter a real website.
| Old resource | Decision | New destination or status | Approval needed |
|---|---|---|---|
| /services/main-service/ | Retain | Same path; verify content and inquiry function | Service owner |
| /services/old-name/ | Rename | /services/new-name/ with the appropriate permanent move | Service and technical owners |
| /guides/duplicate-topic/ | Merge | Relevant consolidated guide, only after its answer incorporates what is needed | Content owner |
| /downloads/product-guide.pdf | Preserve or replace | Correct current document and updated references | Document owner and rights approval |
| /images/product-view.jpg | Preserve asset relationship | Approved image path and correct use | Media/content owner |
| /discontinued-offer/ | Proposed retirement | Hold for business review; if removed without a relevant replacement, plan the appropriate not-found response | Business owner |
Do not redirect every old page to the homepage. The destination needs to be relevant. Include downloadable documents and images, not just page URLs. Record the reason for each merge or retirement so a bulk process cannot quietly discard useful material.
Assign implementation and approval
| Action | Implementing owner | Approving owner | Blocker if unresolved |
|---|---|---|---|
| URL and resource map | Content/SEO planner | Business content owner | Important resource lacks an agreed destination |
| Redirect rules | Developer or server owner | Technical lead | No authorized implementer or testable rule |
| Content and document release | Content/platform team | Source/rights owner | Missing permission or critical content |
| Hosting and deployment | Infrastructure/deployment owner | Technical release owner | Environment or recovery procedure unverified |
| Business journey tests | Website/QA owner | Service owner | Inquiry, purchase or essential function fails |
| Launch decision | Release coordinator executes | Named business release authority | Critical acceptance criteria not met |
Agree who will take each role in your project. Technical migration work is not automatically included in an SEO writing or general marketing scope. Do not share passwords or grant unrestricted access just to meet a deadline.
Test readiness and define the stop conditions
- Environment: distinguish staging and production, verify the intended access/directives and confirm a recoverable release record.
- Representative paths: test retained, moved, merged and retired decisions, including documents and images.
- Content: check approved answers, important links, metadata/output requirements and permissions.
- Business functions: test the actual inquiry, purchase or other critical journey with the responsible owner.
- Observation: preserve the baseline, release date, known limitations and monitoring owner.
- Decision control: define which failure stops launch, who can authorize a correction and who can approve a rollback.
In a fictional launch review, the new pages render correctly, but the inquiry route fails and a current product document is missing. The decision is to hold, assign the function fix and restore the approved document—not launch because the homepage looks finished.
A rollback needs its own safe process and approval: what is restored, what new data or changes could be affected, and how functions are rechecked. It is not a promise to recover search rankings.
Review the move against dated records
Google notes that search fluctuations can occur while a move is processed, and the time varies. A change after launch is not automatically proof of failure—or permission to ignore a real broken path.
| Observation | Record | Response |
|---|---|---|
| A mapped destination fails | Time, old/new resource, response and affected scope | Technical owner corrects and verifies the rule |
| A critical business function fails | Reproducible test and approved stop condition | Use the release decision process |
| Search figures fluctuate | Comparable pages/markets, release dates and source limits | Investigate in context; no fixed recovery promise |
| Measurement definition changed | Old/new event or page-group scope | Mark the comparison break rather than reporting a false trend |
Use the technical review scope for evidence standards and the measurement guide for comparable business reporting. If discussing work with Stormy Increment, review the listed service options and confirm the specific migration and platform responsibilities directly; no unrestricted migration product or guaranteed recovery is implied.
Use our technical SEO audit scope guide to define the evidence, review boundary and implementation responsibility.
Need help with your next step?
Tell us about your website and the question you are trying to work through.