Engineering guides / Angular applications and AWS infrastructure
By Arte Soft engineering · 24 October 2026
Website migration SEO: preserve meaning as well as URLs
A website migration can change addresses, templates, hosting and content at the same time. Search problems become difficult to diagnose when there is no record of what moved. The first useful deliverable is an old-to-new URL map with a reason for every decision. Preserve the purpose of important pages instead of redirecting everything to a convenient home page.
Inventory before changing the site
Combine the current crawl, sitemap, analytics landing pages and Search Console evidence where access is available. Include PDFs, campaign URLs and linked media that a navigation crawl might miss. Mark pages to keep, combine, replace or retire. A page with little recent traffic may still serve an active customer or contain a contractual document. Record titles, canonicals and key content for important pages before migration. This baseline helps separate an intended editorial change from an accidental publishing defect. It also makes the scope discussable before developers begin rewriting route rules.
Map each destination deliberately
A permanent redirect should lead to a genuinely relevant replacement. If there is no replacement, a proper missing or removed response can be clearer than sending users to an unrelated page. Avoid redirect chains and update internal links to the final destination. Preserve query parameters only where they still have a defined purpose. Decide how trailing slashes, old domains and language variants behave. Deliver the mapping file in a format that can be reviewed by both editorial and engineering owners, then turn it into executable checks. The URL map is a business document as much as a server configuration.
Rehearse the public response
Before launch, test the old URLs against the proposed rules and check new pages without relying on browser rendering. Verify status codes, canonical addresses, robots directives and sitemap entries. Protect staging from accidental indexing while ensuring those protections do not reach production. Confirm that analytics and consent behavior still reflect the intended setup. Acceptance includes a sample of high-value journeys, not only a successful deployment command. Keep rollback instructions and the previous release available. A cache may continue serving old output after a correct build, so inspect the public response after propagation rather than assuming origin changes are sufficient.
Preserve a machine-readable record of the old addresses and expected destinations after launch. It helps a future maintainer understand why a redirect exists instead of deleting it as apparently obsolete configuration during a later cleanup or redesign.
Observe without promising a ranking outcome
Submit the new sitemap and monitor crawling, indexing, broken links and conversion journeys after launch. Search engines may take time to process moves, and ranking changes are possible even when implementation is careful. Arte Soft’s own product sites provide examples of ongoing web publishing, not evidence that migrations have no search risk. Bring the old domain, proposed structure and available search data. A scoped migration engagement can produce the URL map, release checklist and post-launch monitoring plan. Keeping a migration technically controlled is achievable; guaranteeing a particular position or immediate AI recommendation is not.
Relevant Arte Soft work
Cloud Calendars — our own product is our own product or engineering project. It provides context for the work we discuss here; it is not a claim of identical results for every client deployment.
Sources and further reading
Need help with Website migration planning?
Send the current app, system or brief, the behaviour you need and your constraints. We can agree a discovery, implementation or repair scope with concrete acceptance criteria.
Discuss this with Arte Soft