SEO during a website redesign: preserving indexation
A technical redesign checklist covering URL mapping, redirects, canonicals, robots, sitemap, metadata, and post-release search monitoring.

Capture the current site map
Before changing structure, export live URLs, response codes, canonicals, titles, descriptions, and known inbound links. Mark pages that already earn impressions, visits, or inquiries.
This inventory becomes the migration baseline. Without it, useful pages can disappear, distinct intents can be merged, and redirect chains can emerge unnoticed.
Map old addresses to new ones
Every changed useful URL needs a permanent redirect to the closest relevant destination. Redirecting the entire old site to the home page loses meaning and creates a poor user journey.
Keep an existing address when it is clear, stable, and still matches the content. A visual redesign does not require a URL change.
Verify indexing signals
Production pages need self-referencing canonicals, correct language, unique titles and descriptions, crawlable primary text, and a coherent heading structure. The sitemap should include only canonical indexable URLs returning 200.
Robots rules must not block resources needed for rendering. Administrative areas and private APIs should remain excluded from crawling and indexing.
Monitor after release
After deployment, verify redirects, sitemap, representative templates, and real error logs. Then submit the sitemap to Yandex Webmaster and request recrawl for priority URLs.
Search changes are not immediate. Track excluded pages, crawl errors, impressions, and query movement over time instead of drawing conclusions from one day.
Questions and answers
Does a redesign require new URLs?
No. Keep clear addresses that still match the content. Change a URL only for a justified structural reason and provide an exact permanent redirect.
When should the new sitemap be submitted?
Submit it after production verification confirms canonical pages return 200, redirects work, and robots rules allow the important content.
.webp&w=1920&q=85)