“A redesign is a migration project: protect discoverability first, then improve the experience.
Diagnosis
A new interface can quietly break established URLs, internal links, or the content Google uses to understand a listing. Treat the redesign as a site move when URLs change, not as a purely visual launch. A second risk is mobile parity: Google uses the mobile version for indexing, so a desktop-rich listing paired with a thinner mobile page can weaken what search systems see.
Decision framework
Before design approval, inventory every important old URL and map it to its closest new destination. Decide which URLs genuinely need to change; where they do, use permanent server-side redirects, update internal links, and submit the new sitemap. Keep essential text, images, structured page meaning, and metadata available on mobile. Stage the change, test representative pages, and monitor indexing rather than relying on launch-day impressions.
Explicitly hypothetical property example
Implementation and measurement
Build a redirect and URL inventory before release; crawl old and new addresses in staging. After launch, inspect redirect chains, mobile rendering, sitemap processing, indexed-page coverage, and organic landing pages. Compare like-for-like periods only after allowing the migration to settle, and log every changed URL so a sudden drop can be investigated rather than guessed.
Put it to work
- Export old URLs and assign one closest destination to each.
- Test redirects and mobile content on representative listing templates.
- Monitor indexing, sitemap processing, and organic landing pages after release.
Sources and visual credits
- Google Search Central: Site moves and URL changes
- Google Search Central: Mobile-first indexing best practices
Illustrative photograph: Overhead desktop workspace (Unsplash). It does not depict the hypothetical example. Jeff Sheldon ugmonk · CC0 · Wikimedia Commons