A redesign changes more than colours and layout. It can alter URLs, headings, navigation, page content, images and technical signals that search engines already understand. SEO protection must be part of the rebuild plan before the new design is launched.
Inventory the current search footprint
Export indexed URLs, landing pages, titles, descriptions, backlinks and organic traffic before development starts. Identify pages that generate enquiries, sales or important assisted conversions.
A low-traffic page may still support a valuable service page through internal links or external references, so decisions should not rely on visits alone.
Keep valuable URLs where possible
If a page still serves the same purpose, keeping its URL is usually safer than changing it for style. When a change is necessary, map each old URL to the closest new equivalent.
Avoid redirecting every removed page to the homepage. Irrelevant redirects confuse users and weaken the relationship between old and new content.
Preserve content intent and hierarchy
Record H1 headings, important sections, FAQs, product or service details and internal links. A visually cleaner page should not accidentally remove the information that explains the service.
Improve wording and structure while keeping the user question and search intent clear. Decorative text cannot replace useful detail.
Rebuild metadata and structured data
Create unique titles and descriptions for each important page. Restore canonical tags, hreflang for language pairs, Open Graph data and valid structured data that matches visible content.
Do not copy one title or description across the whole site. Test rendered HTML, not only template variables.
Protect images and media signals
Use descriptive filenames, alt text, dimensions and modern formats. If image URLs change, update internal references and consider redirects for images that receive search traffic or backlinks.
Do not replace meaningful portfolio or product visuals with generic decorative graphics that provide less context.
Test the staging site before launch
Crawl staging for broken links, duplicate metadata, missing headings, blocked resources, mixed language and accidental noindex rules. Validate mobile layouts and Core Web Vitals on representative pages.
Prevent staging from being indexed, but ensure the production launch removes every temporary block. A forgotten noindex or robots rule can erase visibility quickly.
Monitor after migration
Submit the sitemap, inspect critical URLs and monitor 404s, redirects, index coverage, rankings and conversions. Keep the old URL map available so new issues can be corrected quickly.
Expect temporary movement, but investigate sustained losses by page type rather than assuming every decline is normal.
