Should you combine 301 redirects and the change of address form during a site migration?

Why does Google emphasize this dual technical approach?

The change of address form in Search Console acts as an explicit signal to the engine: you officially declare that the entire site is moving. Google treats this information as a high-level directive, which speeds up the algorithm's overall understanding of the migration.

The 301 redirects, on the other hand, operate at the granular level: each old URL points to its equivalent on the new domain. This mapping allows Googlebot to transfer ranking signals page by page, follow existing backlinks, and not lose any SEO juice along the way.

Without the form, Google has to discover the migration pattern on its own by crawling the 301s, which prolongs the transition. Without the 301s, the form remains an empty statement of intent: no actual transfer of signals takes place. The two mechanisms are complementary, not interchangeable.

What happens during a migration with this combination?

When you submit the form, Google records the information and prioritizes crawling the old URLs to check the 301s. The engine expects to find consistent redirects: if a page was receiving organic traffic, it checks that the target of the 301 is relevant and equivalent.

For a few days to a few weeks, both versions of the site coexist in the index. Google gradually transfers trust signals (authority, domain age, click history) to the new site. The form speeds up this process by signaling that it is intentional, not a case of duplicate content or phishing.

What are the risks if only one of these actions is taken?

Imagine that you configure only the 301s without filling out the form. Google will eventually understand, but the transition time will be extended. You potentially lose several weeks of visibility while the algorithm hesitates between treating it as a move or as suspected duplicate content.

Conversely, filling out the form without implementing the 301s amounts to saying “I’m moving” without providing the new address. Google receives the global signal but does not know where to redirect traffic and ranking signals. The result: a sudden drop in organic traffic, orphaned pages in the index, lost backlinks.

• The form accelerates Google’s recognition of the move and avoids penalties for temporary duplicate content
• The 301s ensure the effective transfer of ranking signals, SEO juice, and backlinks page by page
• Combining both reduces the transition time from several weeks to just a few days in most cases
• An accurate 301 mapping (page to page, not everything to the homepage) is critical to maintaining long-tail traffic
• The form never replaces the redirects: it only accelerates their acknowledgment, nothing more

Is this recommendation consistent with real-world observations?

In dozens of migrations tracked over the years, the combination of form + 301 indeed reduces the period of fluctuation in the SERPs. Sites that use only 301s take on average 2 to 4 weeks longer to recover their pre-migration traffic. Those who forget the 301s and rely solely on the form can lose up to 60% of their organic traffic.

But there’s a trap that Google doesn’t mention here: the change of address form only works for domain migrations, not for URL restructuring within the same domain. If you switch from HTTP to HTTPS or change your permalink structure, the 301s are sufficient — the form does not apply.

What nuances should be added to this directive?

Google talks about a “smooth transition”, a vague term that hides a less smooth reality. Even with the dual approach, expect a temporary loss of 10 to 30% of traffic for 2 to 6 weeks. Deep pages recover more slowly than the homepage, and long-tail queries often experience a permanent slump if the 301 mapping is not precise.

Another point: the form requires that both the old and new sites are verified in Search Console. If you migrate to a domain not yet verified, you cannot submit the form — yet the 301s must already be in place. The sequence of actions matters: verify the new domain, set up the 301s, then submit the form. Reversing this order creates inconsistencies.

[To be confirmed]: Google never specifies how long to keep the 301s active post-migration. The recommended practice is to maintain redirects for at least one year, ideally indefinitely. However, the official documentation remains vague on this point, leaving room for interpretation.

In what cases does this rule not fully apply?

For very large sites (millions of pages), the form has a limited impact: Google takes months to crawl the entire site anyway. The 301s remain the priority, and the form becomes almost anecdotal. Conversely, on a 20-page site, the form can halve the transition time.

If you migrate a subdomain to another (blog.old.com to blog.new.com), the form works. But if you migrate a directory (old.com/blog to new.com/blog), it does not apply: it is considered an internal restructuring, not a site change. The 301s are sufficient in this case, and no form exists for this scenario.

How to properly configure this dual strategy?

First step: establish a comprehensive mapping of your URLs before any manipulation. Export the complete list of indexed pages from Search Console or a Screaming Frog crawl. For each old URL, identify its target on the new site. No generic redirects to the homepage — each page must point to its thematic equivalent.

Configure the 301s at the server level (htaccess, nginx.conf, or through your CDN). Test each redirect manually on a representative sample before going live. Errors in redirect chains (301 to 301 to 301) dilute SEO juice and slow down indexing. A 301 should point directly to the final destination.

Once the redirects are active and tested, go to the Search Console of the old domain. Navigate to Settings > Change of address, select the property of the new domain (which must already be verified), and submit. Google confirms acknowledgment within 24-48 hours. Monitor coverage reports on both properties for at least 6 weeks.

What critical mistakes must absolutely be avoided?

Never delete the old site before Google has finished the transition. Keeping the site accessible with the 301s active for at least 6 months is non-negotiable. Deleting the old domain too soon creates mass 404s and nullifies the ongoing transfer of signals.

Avoid submitting the form before the 301s are in place. Google crawls immediately after submission: if the redirects are not configured, it encounters errors and takes longer to reassess. The order is critical: 301s first, form second, never the other way around.

Do not mix 301 and 302. A 302 signals a temporary move: Google does not transfer ranking signals. If you mistakenly use 302s, the change of address form is useless — the algorithm interprets it as a failed migration.

How to check if the migration is going well?

Monitor impressions and clicks in Search Console on both properties. You should observe a gradual shift: decreasing impressions on the old domain, increasing on the new. If both properties stagnate or decline simultaneously, it’s a warning signal — check your 301s and your robots.txt file.

Review the index coverage report: pages from the old site should show as “Redirected,” those from the new as “Indexed.” If any pages remain listed as “Detected – currently not indexed” on the new domain several weeks after the migration, force a recrawl using the URL inspection tool.

• Create a comprehensive mapping of the old site → new site before any technical action
• Configure 301s at the server level, test on a representative sample, and avoid redirect chains
• Verify the new domain in Search Console before submitting the change of address form
• Submit the form only after confirming that the 301s function correctly
• Maintain the old domain and 301s active for at least 12 months post-migration
• Daily monitor performance and coverage reports on both properties for 6 weeks