BUILD SEARCH FOUNDATIONS
How to review SEO risks before a website redesign
A redesign can change content, URLs and technical behaviour at the same time. Record the useful parts of the existing site before deciding what to replace, then verify the changes against that record.
Establish the baseline you can access
Save the current page inventory, important titles, service descriptions and link structure. If you have authorised access to search data, note useful pages and queries over a comparable period. If you do not, say that traffic evidence is unavailable rather than guessing which pages perform well.
Separate necessary changes
Ask whether an address needs to change or whether the existing URL can serve the improved page. Review useful content before trimming it for a new layout. Keep important downloads and service details in the migration plan rather than treating them as visual clutter.
Inspect the technical plan
Google's migration guidance covers mapping changed URLs, relevant permanent redirects and updated links. Check that canonical URLs and index controls describe the public pages. Keep a record of any intentionally removed content and how its old address will behave.
Test before and after the switch
Use the old URL list to verify destinations after launch. Check that links point directly to the final pages and that the main content is present. Review the public sitemap and the production version, not only a private preview. Keep failed checks visible until they are corrected.
Observe without promising certainty
Search visibility can fluctuate after a migration. Compare the same kinds of pages and queries over sensible periods, noting changes in demand or promotion. Avoid attributing every movement to the redesign or making a guarantee that every ranking will be retained.
A useful project deliverable is a migration record showing what changed, why and how it was checked. If search performance falls, that record helps investigate the cause. Without it, even a visually successful redesign can leave the owner guessing whether a page disappeared, a link changed or demand simply shifted.
Sources and further detail
Technical references checked on 8 October 2026. Provider features can change.
Practical guidance with illustrative examples. Read our editorial standards or send a correction.