Canonical First, Hreflang Second
Google processes rel="canonical" as the primary indexing signal, then layers hreflang on top as a localization signal (Google Search Central, canonical documentation). Every canonical page needs a self-referencing canonical tag, and each language version must canonicalize to itself — routing every locale to one "master" language breaks the model.
Hreflang pairs must point straight at the final canonical URL, never at an address that's still mid-redirect. Get that order wrong and search engines defer judgment on which URL represents the page right after launch — and rankings wobble during that gap.
A Redirect Is a Signal, Not a Setting
A 301 redirect works as a strong signal that the new URL is canonical (Google Search Central, site moves documentation). Google only reassigns the link and ranking signals the old URL accumulated after it re-confirms that redirect several times over, so pulling redirects a few days after launch cuts the signal transfer off mid-way. Google Search Central states explicitly that redirects should stay in place for at least a year.
Build Roadmap and Pitfalls: Designing SEO for a Site Relaunch
Three numbers need to be locked in before planning starts: index-recovery rate, redirect response time, and traffic-loss ceiling. A reasonable target is recovering 95% or more of pre-relaunch indexed pages in Search Console by week four, keeping redirect response under 300 milliseconds, and capping organic session loss at 20%. Without these three numbers, the only thing left after launch is a gut feeling that traffic "seems down."
The most common failure in practice is a canonical chain — page A points to B, B points to C, and Google stops following the chain partway through rather than resolving it to the end. Stacking more than one canonical tag on a single page is just as common a mistake, and when that happens Google discards every declared canonical and picks a representative URL on its own. Both patterns tend to appear when a CMS template quietly replicates the old page structure during a rebuild.
The second failure is hreflang tags still pointing at old URLs mid-redirect. If a language pair resolves to a 301 or 302 response instead of the final destination, the localization signal is invalidated outright. Fix the recovery path in advance: swap the hreflang mapping to the final canonical URL immediately, check the coverage drop in Search Console's indexed-pages report, and pre-document a rollback threshold — if coverage drops more than 5 percentage points, revert to the previous URL structure.
The third failure is certificate trouble. An expired TLS certificate, or a subset of HTTPS pages redirecting back to HTTP, pushes Google to reinterpret signals in favor of the HTTP version. Building certificate-expiry checks and protocol-consistency checks into the launch script catches this before it ever reaches production.
Pre-launch QA runs through three checks in order. First, crawl every new page to confirm a self-referencing canonical is set correctly across the board. Second, verify hreflang pairs return to each other — a one-way tag that isn't reciprocated gets treated as invalid. Third, validate structured data with the Rich Results Test, since a single syntax error can invalidate the entire script. The redirect map needs to cover 100% of old URLs, and 301s stay live for at least a year to let signal transfer finish.
Standard log fields should be fixed before go-live. Logging redirect response code, response time, index status, and hreflang validation results per URL makes it possible to trace exactly which page group lost indexing after the relaunch. Mask anything that could carry PII — query parameters, session IDs — before it ever lands in the log store.
For the first eight weeks after relaunch, review Search Console's indexed-pages and Core Web Vitals reports weekly. When de-indexed URLs climb week over week, bucket the cause into one of four categories — canonical, hreflang, redirect, or protocol — and log it separately in the change log; if the same cause repeats for two weeks running, update the QA checklist itself. Once metrics stabilize past week eight, the review cadence can drop to monthly.
Takeaways at a Glance
Relaunch SEO turns less on content polish than on whether four technical signals — canonical, hreflang, redirects, and protocol — stay consistent. Document the target line before launch (95% index recovery, 300ms redirect response, under 20% traffic loss) along with a rollback trigger at a 5-percentage-point coverage drop, and post-launch ranking swings stop being something you judge by feel.