Define exactly what is changing
Moving to another server while retaining every URL differs from changing a domain. A catalogue redesign may keep the same domain while changing hundreds of category and product links. Moving from HTTP to HTTPS changes addresses too. Preparation therefore starts with a list of changes, rather than one broad instruction to move the website.
Clarify whether the content, URLs, platform, design and order process will change. The more independent changes are launched together, the harder it becomes to identify a later problem’s cause. Choose the sequence for the project: some stages can be separated, while others depend on one another. Both situations need a recorded starting point and a verifiable launch plan.
Map old pages to their new destinations
Keep a list of existing URLs, especially pages with organic visits, external links and important business actions. Sources can include the CMS, Sitemap, analytics and search-owner tools. Include important images and documents: visitors and links can depend on those addresses as well.
Assign a suitable destination to each changed page. An old category should lead to its corresponding new category; a product should lead to the same model or a genuinely equivalent page. When there is no useful replacement, removal is a separate decision rather than a reason to send every URL to the homepage. The map helps identify missing sections and incorrect matches before launch.
The URL has moved permanently.
A permanent move calls for a permanent redirect to a corresponding page. Check that the destination works and serves the same purpose. This is not a promise that rankings will stay unchanged.
Check the old-to-new mapping, the final response and unnecessary redirect chains.
Understand permanent and temporary redirects
A redirect is a server response that sends a browser or crawler to another URL. Status codes 301 and 308 indicate a permanent move. Codes 302 and 307 are used for temporary redirection. The choice communicates whether the page has moved for good or whether its original address is expected to return to ordinary operation.
A permanent migration generally calls for a direct server-side redirect to the corresponding final page. Temporary redirection suits a temporary situation, and search engines treat its URL-selection signal differently. Canonical has another role: it identifies a preferred version of similar content and does not send visitors elsewhere. It should not be treated as a replacement for a redirect when a page actually moves.
Check the new website before switching
Make sure its important pages contain the right information, images load, mobile navigation works and forms and checkout pass the agreed checks. Review crawler access separately: temporary restrictions from the staging environment should not accidentally remain on the live website. The staging version should also avoid replacing the working website in search before launch.
Align canonical rules, internal links, Sitemap and language versions with the new structure. Where the domain or primary website address changes, verify ownership in search-owner tools and review the relevant migration tools. Agree recovery responsibilities with development and hosting before launch. This matters particularly for stores that continue taking orders and updating their catalogue during the move.
Check the complete journey after launch
Open old URLs from different page types and check their destinations. A useful journey ends at an available, relevant page without a loop. Investigate chains of several redirects: they complicate the route and can appear when old and new rules overlap. Review dependent URLs whenever a redirect rule changes.
Update links on the new website that still point to old addresses, and provide search engines with an up-to-date page map. Then monitor errors, indexing, organic visits and enquiries. Reprocessing takes time, so the first day after launch is not a complete result. Keeping the old domain available and maintaining its redirects also belongs in the migration support plan.
Prepare for a practical discussion with a specialist
Gather the current and future website addresses, expected launch date, planned changes and important pages. Establish who manages the domain, server, development, analytics and data exchange. Save baseline figures for a suitable period. Passwords are not needed for an initial discussion: the task and the people involved provide a useful starting point.
You can inspect an individual redirect chain with a redirect-checking tool and compare its destination with the visitor’s expectation. Catalogue-wide and domain-wide rules are better reviewed with a developer and SEO specialist. Preparation should produce a URL map, launch plan and verification list. If the site has already moved and traffic changed, these records help find the cause and choose a correction.
Common questions
Can every ranking be guaranteed to stay unchanged?
No. URL reprocessing and website changes can affect search performance. Preparation, correct mappings and monitoring help reduce controllable risks; outcomes need comparable data after launch.
Why not redirect every old page to the homepage?
The homepage usually does not replace a particular product, category or guide. Visitors lose the answer they wanted. Important URLs need suitable replacements; cases without one require a separate decision.
Is a 301 redirect enough after a migration?
Also check destination content and availability, internal links, canonical rules, Sitemap, analytics and affected website workflows. Redirects are one part of a coordinated migration, not the whole process.
Sources and documentation
From understanding to action
Connect the decisions in one plan.
A focused check helps identify a cause. When changes involve structure, development, content and analytics, agree them together with priorities, ownership and verification.
Tell us about your website, priorities and the issue you have observed. We will discuss whether you need a focused stage or coordinated promotion and what the initial scope should include.
Discuss coordinated promotion