TL;DR
Technically correct redirects don’t guarantee traffic preservation. Redirects tell Google where content moved, but Google independently decides whether the new URL deserves the old URL’s rankings. Signal transfer is partial, not complete. Intent mismatch between old and new URLs, redirect chain latency, and user experience degradation on landing pages all cause traffic loss despite working redirects. The fix requires auditing intent alignment, consolidating redirect chains, and analyzing user behavior signals on the destination pages.
The Conversation
Kenji, dev lead at a SaaS company after site migration: We migrated our site three months ago. Every redirect is in place and working. I’ve verified them all with Screaming Frog. But traffic is down 35% and not recovering. I don’t understand how correctly implemented redirects can lose traffic.
SDC SEO Brain: Technically correct redirects are necessary but not sufficient for traffic preservation. Redirects tell Google where content moved. They don’t obligate Google to rank the new location the same as the old one. What exactly changed in the migration?
Kenji: We redesigned the site, restructured the URL hierarchy, and updated all the content. The redirects map every old URL to its equivalent new URL.
SDC SEO Brain: There are at least three problems embedded in that description. Let’s unpack them. First, redesign typically changes page templates and layout. Second, restructuring changes URL signals. Third, content updates change the page itself. Google now sees three differences, not just a location change.
Kenji: But 301 redirects pass link equity, right?
SDC SEO Brain: 301s pass most link equity, not all. Google has confirmed that redirects pass “full value” but practical observations suggest 90-95% transfer in real-world scenarios. That’s a 5-10% signal loss just from the redirect mechanism. Multiply that across your entire site and it compounds.
Kenji: So we lost 35% traffic from redirect signal loss?
SDC SEO Brain: No, 5-10% signal loss doesn’t explain 35% traffic drop. The redirect mechanics are one factor. The more significant factors are likely intent mismatch, user experience changes, and restructuring effects.
Kenji: Explain intent mismatch.
SDC SEO Brain: Before your migration, Google ranked your old URLs for specific queries because they satisfied user intent for those queries. After migration, Google sees different pages at the new URLs. Even if the topic is similar, the content, format, and structure are different. Google reevaluates whether the new content satisfies the same intent the old content satisfied.
Kenji: But the content is better now. More comprehensive, better written.
SDC SEO Brain: “Better” in your judgment isn’t the same as “better for the specific query.” If your old page ranked for “quick setup guide for X” and your new page is a comprehensive deep-dive, you might satisfy a different intent. The users who wanted “quick” now bounce because they got “comprehensive.”
Kenji: How do I check if that’s happening?
SDC SEO Brain: Compare user behavior metrics before and after. In GA4, look at engagement rate and average engagement time for your top landing pages. If engagement rate dropped or time on page dropped for the migrated pages, users aren’t finding what they expected. That’s intent mismatch.
Kenji: I’ll check that. What about the restructuring you mentioned?
SDC SEO Brain: URL restructuring changes your internal link architecture. Old internal links pointed to old URL paths. Even if you updated all internal links, the distribution of internal link equity changed. Some pages that were deeply linked in the old structure might be less emphasized in the new structure.
Kenji: We tried to maintain the same site architecture.
SDC SEO Brain: Same architecture in terms of navigation levels, maybe. But internal link patterns are more granular. Did you preserve the exact internal linking between content pages? If a blog post previously had 30 internal links pointing to it and now has 15, that page lost internal link equity regardless of redirects.
Kenji: I didn’t audit that specifically.
SDC SEO Brain: That’s worth checking. Export your internal link graph from Screaming Frog before and after migration. Compare inlinks per page for your top organic landing pages. Significant drops indicate internal link equity loss.
Kenji: What about redirect chains? We tried to avoid them but might have some.
SDC SEO Brain: Check for chains where Old URL A redirects to New URL B, but New URL B redirects to New URL C. Each hop loses some signal and adds latency. Googlebot will follow chains but deprioritizes them. More importantly, users experience slower page loads.
Kenji: Our site is faster than before. We optimized page speed.
SDC SEO Brain: Overall site speed might be faster, but redirect latency is additive. If old bookmarks or external links hit the redirect chain, users experience the redirect delay before experiencing your fast page. Check your redirect response times specifically.
Kenji: How do I check that?
SDC SEO Brain: In Chrome DevTools, network panel, filter by your domain, and hit an old URL that should redirect. The first request shows redirect time. If you’re seeing 200-500ms per redirect hop and you have two-hop chains, you’re adding half a second before the page even starts loading.
Kenji: What about the user experience changes from the redesign?
SDC SEO Brain: This is often the hidden cause of post-migration traffic loss. New designs mean new layouts, new navigation patterns, new content organization. Users who knew how to find information on your old site now can’t find it on your new site.
Kenji: But the new design is cleaner and more modern.
SDC SEO Brain: Clean and modern doesn’t mean usable for returning visitors who had learned your old patterns. CLS issues on new templates, different button placements, removed navigation elements that users relied on, or new friction points all create engagement problems.
Kenji: How do I audit user experience post-migration?
SDC SEO Brain: Heat mapping tools like Hotjar or Clarity show where users click, how far they scroll, and where they struggle. Compare behavior patterns on your highest-traffic pages before and after. Session recordings show specific friction points. Pay attention to navigation clicks and exit pages.
Kenji: We didn’t have heat mapping before migration.
SDC SEO Brain: Then use Search Console’s page experience report and Core Web Vitals as proxies. Compare CLS, LCP, and INP before and after. If your new design introduced CLS issues (layout shifts while loading), that directly affects rankings in mobile results.
Kenji: Core Web Vitals are actually better than before.
SDC SEO Brain: Then the issue is probably content and intent alignment, not technical UX. Let’s return to that. Pull your top 20 organic landing pages from before migration. For each, identify the primary keyword it ranked for. Then compare the old page content to the new page content. Are they addressing the same user intent?
Kenji: I can do that. What am I looking for specifically?
SDC SEO Brain: Look for format changes (guide became article, article became video page), length changes (comprehensive became summary or vice versa), focus changes (how-to became about, or specific became general), and structure changes (list became prose, FAQ became narrative). Any of these can trigger Google to reevaluate intent match.
Kenji: Some pages did change format. We consolidated some similar pages into single comprehensive guides.
SDC SEO Brain: Consolidation during migration is a common mistake. You merged pages that ranked for different keywords into one page that might not satisfy any of those keywords well. Google now has one URL to evaluate instead of three, and the intent signals are muddled.
Kenji: Should I have kept them separate?
SDC SEO Brain: For migration, yes. The safest migration preserves the old structure exactly and redirects 1:1. Consolidation, restructuring, and redesign should happen after migration stabilizes, as separate projects with their own timelines.
Kenji: Too late for that. What do I do now?
SDC SEO Brain: Prioritize your highest-value pages that lost traffic. For each, evaluate whether the new content matches the original ranking intent. If not, consider reverting the content approach while keeping the new URL. Then systematically work through lower-priority pages.
Kenji: Is recovery possible?
SDC SEO Brain: Recovery is possible but not guaranteed. Some sites recover fully within 6-12 months. Some stabilize at a lower baseline. The key is diagnosing whether the issue is technical (redirect signal loss, chain latency) or content-based (intent mismatch, consolidation problems). Technical issues are faster to fix. Content issues require more extensive rework.
FAQ
Q: Why do redirects not preserve all traffic?
A: Redirects tell Google where content moved, but Google independently evaluates whether the new URL deserves the old rankings. Signal transfer is partial (90-95%), intent may mismatch if content changed, and user experience differences on new pages affect engagement signals.
Q: What is intent mismatch after migration?
A: When your old page ranked for a specific query and your new page, despite covering the same topic, doesn’t satisfy that query the same way. A quick-start guide becoming a comprehensive deep-dive serves different intent, causing users to bounce.
Q: How do I audit intent alignment post-migration?
A: Compare engagement metrics (engagement rate, time on page) before and after for top landing pages. Compare content format, length, and focus between old and new versions. Look for format changes (guide to article), length changes (comprehensive to summary), and focus changes (specific to general).
Q: Do redirect chains cause traffic loss?
A: Yes. Each redirect hop loses some signal and adds latency. Chains of two or more redirects can add 200-500ms of delay before the destination page loads. Consolidate chains to single-hop redirects pointing directly to final destinations.
Q: Should I consolidate pages during a migration?
A: No. Safest migrations preserve the old structure exactly with 1:1 redirects. Consolidation, restructuring, and content changes should happen after migration stabilizes, as separate projects. Doing everything at once makes diagnosing problems nearly impossible.
Q: What’s the typical recovery timeline after a migration traffic drop?
A: 6-12 months for full recovery if issues are diagnosed and fixed promptly. Some sites stabilize at a lower baseline if fundamental intent or content problems aren’t addressed. Technical issues (redirect chains, internal link loss) recover faster than content issues (intent mismatch, consolidation).
Summary
Working redirects don’t guarantee traffic preservation. Redirects are location signals, not ranking signals. Google independently evaluates whether destination pages deserve the source pages’ rankings.
Signal transfer is partial, not complete. 301 redirects pass 90-95% of signals in practice. Redirect chains compound the loss. Each hop adds latency visible to users.
Intent mismatch is the hidden killer. Content updates during migration often change what intent a page satisfies. If your new page serves different intent than your old page, rankings drop regardless of redirect quality.
Consolidation during migration is dangerous. Merging pages that ranked for different keywords into one page muddies intent signals. Google can’t determine which queries the consolidated page should rank for. Keep migration and consolidation as separate projects.
Diagnose before fixing. Check engagement metrics for intent mismatch. Check internal link graphs for equity loss. Check redirect timing for chain latency. Different causes require different solutions.
Sources
- Google Search Central: Site move with URL changes documentation
- Google Search Central: 301 redirect signal transfer confirmation
- Core Web Vitals: Page experience metrics documentation
- Screaming Frog: Migration audit capabilities