Should you really redirect each URL individually when moving a site?

Why does Google emphasize individual redirects?

When a site relocates—changing domains, structural redesign, HTTPS migration—Google needs to understand where each old URL leads. A redirect to the homepage sends a vague signal: has the content disappeared? Has it been moved? The search engine cannot guess.

1:1 redirects maintain thematic consistency between the old page and the new one. Google then transfers PageRank, relevance signals, and ranking history to the correct destination. It's the difference between keeping your positions or starting from scratch.

What happens if everything redirects to the homepage?

Google treats these redirects as soft 404s—pages that technically exist but whose content no longer matches the original search intent. The engine eventually de-indexes the old URLs without transferring their authority. Result: your ranking pages disappear from the index.

Users land on a generic homepage when they were searching for specific content. The bounce rate skyrockets, time on site plummets—disastrous behavioral signals that further degrade your ranking. It's a vicious cycle.

Does this rule apply to all types of migrations?

Yes, without exception. Whether you're changing domain names, switching to HTTPS, restructuring your architecture, or migrating to a new platform—the rule remains the same. Each indexed URL that changes address must point to its exact equivalent on the new site.

The only case where a redirect to the homepage is acceptable: when the page is genuinely removed without an equivalent. Even then, a 410 Gone or 404 response may be more honest than a misleading redirect. Google prefers transparency.

• Individual 301 redirects: they transfer PageRank and relevance signals to the corresponding new URL
• Group redirects to the homepage: treated as soft 404s, they lead to a gradual loss of ranking and organic traffic
• Propagation delay: Google can take several weeks to recrawl all your redirects—a rigorous mapping is essential
• Thematic consistency: the old page and its new destination should cover the same topic to avoid contradictory signals
• Post-migration monitoring: monitor 404 errors, traffic drops, and ranking variations to quickly fix any missing redirects

Is this recommendation truly applied in practice?

In theory, everyone agrees. In practice? Shoddy migrations are common. Many sites redirect 80% of their URLs to the homepage out of laziness or technical ignorance. They observe a traffic drop of 30 to 60% in the following months and then panic.

The cases where I've seen successful migrations without notable loss all had one thing in common: comprehensive URL mapping before the move, tested in preproduction, with daily server log monitoring for 3 months. It's not glamorous, but it works.

What nuances should be added to this absolute rule?

Google never specifies how long redirects should remain active. The standard response is “at least a year,” but on high-authority sites, I’ve observed complete transfers in 2-3 months. On weaker sites, it can take 6 months. [To be verified] according to your crawl profile.

Another point: Are all URLs worth redirecting? If you have 50,000 pages, and 45,000 generate no traffic and have no backlinks, redirecting each one individually is fetishism. Focus on the pages that matter—those with traffic, backlinks, or rankings on strategic queries.

In what cases can this rule be relaxed?

Never for strategic pages. But for outdated content, empty categories, or purely technical pages without SEO value, a clean deletion (404 or 410) may be healthier than an artificial redirect. Google will appreciate honesty.

Chained redirects (A → B → C) are a classic trap during successive migrations. Google only follows up to 5 hops before giving up. Result: your PageRank dilutes at each step. Audit your previous migrations and flatten the chains—make A point directly to C.

What should be done concretely before moving a site?

Establish comprehensive mapping: export all indexed URLs via Google Search Console, cross-reference with your XML sitemap and server logs. Identify each page that generates traffic or has backlinks. Create an Excel file with 3 columns: old URL, new URL, HTTP code (301 in 99% of cases).

Test this mapping in preproduction. Ensure that each redirect points to a functional page (not a hidden 404). Use Screaming Frog or OnCrawl to crawl your test environment and spot chained redirects, infinite loops, or configuration errors.

What mistakes should definitely be avoided when going live?

NEVER deploy a migration on a Friday night. Schedule the move at the beginning of the week so you can monitor in real time. The first 48 hours are critical—that's when you detect server configuration problems, poorly written .htaccess rules, or CDNs that cache old versions.

Avoid the trap of “we'll see how it goes.” Prepare a rollback plan: complete backup, ability to restore the old site in under an hour if the new one crashes. I've seen migrations where the new site was inaccessible for 12 hours—Google completely de-indexed the domain.

How can you verify that the migration is going well?

Monitor the Search Console like a hawk. Check for exploding 404 errors, valid pages dropping, impressions plummeting. Compare organic traffic week by week—a drop of 10-15% is temporarily normal, but beyond 25% there’s a structural issue.

Analyze your server logs to confirm that Googlebot is crawling the new URLs. If the bot is stuck on the old addresses or not following your redirects, that's an alarm signal. Force a recrawl via the Indexing API for priority pages.

• Export all indexed URLs and those with backlinks before migration
• Create a 1:1 mapping between old and new URLs, without exception for strategic pages
• Implement server-side 301 redirects (Apache, Nginx, IIS)—never in JavaScript or meta refresh
• Test the mapping in preproduction with a crawler to detect chains, loops, and errors
• Monitor Search Console, Analytics, and server logs daily for at least 90 days
• Keep redirects active for at least 12 months to ensure complete PageRank transfer