How to preserve SEO signals during a website redesign
A new design is not a migration plan. Preserve existing search value with a URL map, redirects, a content inventory, and post-launch checks.
AT A GLANCE
Before a redesign, inventory existing URLs, content, internal and external links, and available measurement data. Every valuable retired URL needs a relevant new destination and a server-side permanent redirect. At launch, verify canonicals, hreflang, sitemaps, robots rules, noindex directives, structured data, and internal links, then monitor crawl errors and performance.
- Create a page-by-page old-to-new URL map before development.
- Do not redirect unrelated retired pages in bulk to the homepage.
- After launch, verify response HTML, redirects, and indexability.
Inventory the current site before redesign begins
Collect every indexable URL from the sitemap and CMS and, where available, analytics, server logs, and Search Console. Mark pages that receive traffic, have external links, generate enquiries, or contain important guidance. Include image and download URLs when other pages depend on them.
The goal is not to preserve every old sentence unchanged. Identify the search intent and user task each page serves and decide where the new site will handle it. When measurement data is unavailable, use content, links, and business purpose to make a cautious decision. A visual design alone is not a reason to delete a URL.
Give every old URL a documented decision
For each old address, state whether it remains unchanged, moves, is consolidated into another page, or is genuinely retired. A moved page needs a relevant destination. Redirecting many unrelated pages to the homepage does not preserve their purpose and does not take visitors to the information they expected.
Use a server-side permanent redirect between the old and new locations. Avoid redirect chains: the old URL should point directly to the final destination. Update internal links to use the final new URL so neither visitors nor crawlers take an unnecessary detour.
Preserve content and technical signals
The new page title, main heading, copy, and internal links should still answer the same important question. When consolidating pages, the destination must cover the retained topic substantially rather than mention it in passing. Verify language relationships, canonical targets, and URLs inside structured data.
A staging environment may be noindex, but that directive must not remain after production launch. The same applies to restrictive robots rules or authentication. Search engines should receive the main content, title, description, and navigation in the final HTML rather than only after a client-side state change.
Use a launch verification checklist
Fetch important old and new URLs after launch. Check the HTTP status, redirect destination, canonical, robots meta value, unique title and description, main heading, language alternates, and structured data. The sitemap should contain only final indexable URLs.
Test enquiry paths and measurement too. An indexable page is not a successful handover if the form fails or the analytics journey disappears. Use a sample covering priority landing pages, language pairs, images and files, and a few deliberately invalid addresses.
Reindexing requires time and observation
Temporary fluctuation can occur after significant URL changes while search engines recrawl old and new addresses. Submit the new sitemap, retain permanent redirects for the long term, and monitor broken URLs, selected canonicals, indexation, and priority landing-page performance.
Do not judge the migration from one day of ranking data. Compare meaningful periods. If an important old URL disappears or reaches the wrong destination, correct the mapping and content relevance before hiding the problem behind another generic redirect.
Sources and further reading
- Site Moves and MigrationsGoogle Search Central · Checked: 2026-10-31
- How to specify a canonical URLGoogle Search Central · Checked: 2026-10-31

