A website redesign is where many teams suddenly realize they’ve treated SEO like the folding chair in the garage. It’s technically still there, but it was never part of the real plan. If redirects, internal links, canonicals, and indexation checks wait until launch week, the redesign may come with an avoidable traffic drop.

Google’s site migration guidance recommends mapping old URLs to their new destinations, implementing permanent redirects, updating internal links, checking canonical tags, and submitting an updated sitemap. Complete and test these tasks before launch. Launch day is too late to discover that valuable pages were removed or redirected somewhere irrelevant.

The Redirect Map Isn’t Optional

The part teams keep trying to skip is the redirect map. That’s usually because it’s boring, tedious, and full of spreadsheet energy. It’s also one of the main things standing between a smooth relaunch and a meeting titled, “Why did half our high-intent pages disappear?”

Every important old URL needs an appropriate destination. An old service page should redirect to its closest replacement, not automatically to the homepage. Google warns that redirecting many old pages to one irrelevant location can confuse users and may be treated as a soft 404.

Redirect chains should also be avoided. If an old URL redirects to another old URL before reaching the final page, users and crawlers have to follow unnecessary steps. Redirect each old URL directly to its final destination whenever possible.

Google recommends server-side permanent redirects, such as 301 or 308 redirects, for permanent URL changes. Internal links should also be updated so they point directly to the new URLs instead of relying on redirects.

Canonical Tags Can’t Replace a Migration Plan

Canonical tags are important, but they aren’t a substitute for redirects. Google’s documentation on canonical URL signals describes both redirects and rel="canonical" annotations as strong signals. However, they solve different problems.

A canonical tag helps Google determine which version of a duplicate or nearly identical page should appear in search results. A permanent redirect sends users and crawlers from a retired URL to its replacement.

If a redesign permanently removes or changes a URL, use a redirect. Don’t leave the old page accessible and assume a canonical tag will clean everything up. The safest approach is to keep the signals consistent: redirects should lead to the preferred URLs, new pages should use self-referencing canonicals, internal links should point to the new URLs, and the sitemap should list only the preferred versions.

Staging Noindex Rules Can Follow You Into Production

Then there’s the classic staging mistake: a development restriction makes its way onto the production site and quietly kneecaps the launch.

Teams commonly use noindex directives or robots.txt rules to keep staging pages out of search results. That’s reasonable during development. The problem starts when those controls aren’t removed before launch.

Google’s documentation on blocking indexing with noindex explains an important catch. Googlebot must be allowed to crawl a page before it can see its noindex directive. If robots.txt blocks the page, Google may never discover the noindex instruction.

This can create confusing and contradictory signals during a migration. Before launch, crawl the production-ready site and check:

• Robots.txt rules
• Meta robots tags
• X-Robots-Tag HTTP headers
• Canonical URLs
• HTTP status codes
• Internal links
• XML sitemap URLs
• Redirect destinations and chains

SEO checks shouldn’t begin after the new site is public. They should be part of staging approval.

Domain Moves Require Additional Steps

If the redesign includes a move to a different domain or subdomain, Google says the Change of Address tool should be used after the new site is live and the redirects are working.

The tool isn’t needed for every redesign. Don’t use it for:

• Moving pages to new paths on the same domain
• Switching from HTTP to HTTPS
• Moving between www and non-www versions
• Changing hosting providers without changing public URLs

For a same-domain URL cleanup, keep the process focused. Build the redirect map, update internal links and canonicals, submit the new sitemap, crawl the site, and confirm that important pages still exist where users and search engines expect them.

Redesigns don’t lose visibility because Google dislikes new layouts. They lose visibility when teams treat launch day as the beginning of technical quality assurance instead of the deadline for finishing it. Getting qualified SEO help before the redesign is usually far less expensive than spending the next six weeks diagnosing a preventable traffic drop.