01
Inventory the pages and workflows that matter
Before redesign approval, gather current URLs, relevant organic landing pages, backlink destinations where available, service content, and lead integrations. This identifies what has value beyond the current visual layout. A page omitted from the new menu may still serve an important customer question. We compare the proposed structure with that inventory and flag content or workflow decisions requiring approval. Missing analytics access should be noted as a limitation rather than assumed to mean a page has no value.
02
Map each retired destination to a relevant answer
A permanent redirect should lead a visitor to the closest appropriate replacement. Sending every old page to the homepage can erase the service context they expected. The map also needs checks for chains, loops, duplicate variants, and links still pointing to old paths. Canonicals and sitemap entries should agree with the new permanent destinations. Where there is no suitable replacement, the response should be deliberate and documented instead of disguised with an unrelated redirect.
03
Make release checks broader than appearance
Phone actions, contact forms, booking transitions, analytics events, and page rendering need comparison before and after release. We check that staging restrictions do not persist and that important content is available to crawlers. A domain change adds further requirements for redirects and verification; it should not be confused with a redesign on the same host. Implementation responsibilities and rollback options should be clear before launch, especially when several vendors are involved in the release.
04
Monitor changed page groups with realistic expectations
Search engines need time to process new content and redirects, and visibility can fluctuate during a transition. A careful plan reduces avoidable mistakes but cannot guarantee zero traffic loss. Monitoring looks for unexpected exclusions, broken destinations, missing service content, and changes in received inquiries. Page-group comparisons are often more useful than reacting to every daily movement. We document what changed so the team can separate an implementation problem from normal recrawling or unrelated search changes.
Questions worth asking.
Can you promise no ranking loss during a redesign?
No. Planning reduces preventable risk, but search engines may reassess changed content and URLs.
When should we involve migration planning?
Before the final content and URL structure are approved. After launch, missing destinations can be harder to recover cleanly.