Redesign changes appearance, but migration changes the way the service works and is found. Lost addresses, deleted content, misdirection or blocked indexing can cause visual drops when a new page is launched. Safe migration requires inventory of the old service, decision on any valuable subpage and tests even before changing the domain or system. SEO is part of a technical project here, not an amendment made after publication.
Inventory and redirection map
Before designing you need to collect addresses from the site map, CMS system, analytics, search engine tools and external links. For each address you should save status, traffic, visibility, links and business goal. This way, the team knows which content to move, connect, correct or consciously withdraw.
Each changed, valuable address should receive a 301 redirection to the most similar counterpart. The directing of all old pages to the main page does not retain their importance and makes it difficult for users to reach the information. The route map must be unambiguous, without loops and long chains.
Content, metadata and test environment
The new layout cannot accidentally remove headers, service descriptions, structural data and internal linking. It is worth comparing the old and new version in terms of the intention of each subpage. The content can be improved, but the relevant information and the topic of the website should remain legible for the recipient and search engine.
The test environment should be protected from indexation, and during publication removes the locks only from the production version. The test includes canonical, robots, site map, response status, language versions, images and forms. Automatic check of addresses helps you catch errors that are hard to notice manually.
Publication and post-migration monitoring
The moment of implementation should have a responsibility plan and the possibility of rapid technical withdrawal. After publication, you need to re-scan the addresses, send a new site map and check the most important redirections. Analyses and conversions should work from the first visit so that there is no data gap.
For the next weeks it is worth to observe indexing errors, pages not found, organic movement, key queries and conversions. Some fluctuations are natural, but the sudden decline of the entire section requires a reaction. Server logs and search engines help distinguish between the technical problem and the usual change in demand.
SEO migration checklist
- Full list of old addresses and their values.
- Map one to one for changed URLs.
- Comparison of content, headers, meta and link.
- Test canonical, robots, sitemap and HTTP status.
- Control forms, analytics and conversion.
- Scan the site immediately after publication.
- Monitoring errors, traffic and indexing for several weeks.
Separate page address from record number
The transfer of content to the new CMS may change its internal identifier, but it does not need to change the public URL immediately. In the plan it is worth saving both elements: the material in the old system and the address at which the recipient should find it after implementation.
This allows you to organize the data without accidentally depending on the way the new database works. Changing public addresses should be undertaken consciously and separately.
Include decision-making options
In addition to the main list, there may be old aliases, file links and addresses written in advertising material. Not every variant means separate content. Before preparing rules, you need to recognize its role and current behavior.
It is worth keeping a list of exceptions, instead of hiding them in a general rule that redirects everything into one place.
- Does the address have an actual counterpart?
- Is the material connected to another?
- Is the file still needed and up-to-date?
- Does the existing redirection remain valid after the change?
Compare content after reaching the destination
The test should check not only the server's response, but also the final topic of the subpage. The active redirection to the wrong service does not meet the migration goal. With more addresses you can combine automatic check with a review of representative and unusual cases.
Save the record of the executed operation
The final address map and the result of the check will help you later diagnose the old link reports. They should be available to people maintaining the service, along with information which cases required an informed decision.
We write about the preparation of the test transition in migration planning guidebook. Modernisation is safer when control covers the importance of material, public address and how to store it in a new system.
The most common questions
Can I change all addresses?
You can, but any change increases the extent of migration and risk. If the current addresses are correct, it is often better to keep them.
How long do you maintain the redirection?
In practice, it is worth maintaining them long-term, especially when old addresses have links or still appear in the company's materials.
Is migration always followed by a decline?
There may be short fluctuations, but careful preparation reduces the risk and allows you to quickly detect irregularities.
Summary
Secure migration combines data, editorial decisions, redirections, tests and monitoring. This way, the new look and technology do not destroy the value built by the previous version of the service.
