SEO problems during a redesign usually come from lost signals, not the new color palette. The control is a migration plan that exists before templates are rebuilt.
Before the build
Crawl every indexable URL and capture status, title, description, H1, canonical, robots directives, internal links, schema, images, and organic performance. Identify pages with links, impressions, conversions, or distinct intent. Give every old URL a named outcome: unchanged, improved, merged, redirected, removed, or never public.
During the build
- prevent test environments from being indexed;
- keep one self-referencing canonical per public page;
- preserve meaningful content and descriptive internal links;
- render important content without fragile browser scripts;
- use schema only when visible content supports it;
- generate robots and sitemap files from canonical routes;
- use direct, relevant permanent redirects and remove chains.
Before launch
Crawl the release as if it were production. Test every redirect, canonical, sitemap URL, robots rule, important image, and navigation path. Search for accidental noindex, development hosts, HTTP canonicals, broken fragments, and orphan pages. Google’s migration guidance recommends changing one major thing at a time where possible and monitoring the move.
After launch
Verify the live response—not just the build. Crawl production, compare the deploy manifest, submit the XML sitemap, and monitor Search Console by page group and query intent. Diagnose losses before rewriting: redirects, indexability, internal links, changed demand, and irrelevant legacy traffic can look similar in a topline chart.
Do not launch until URL mapping, redirects, canonicals, sitemap, robots, metadata, schema, analytics, forms, backup, and rollback have named owners and passing evidence.
