Exactly. A subdomain is treated as a separate root domain by search engines. Moving content from /blog to blog.example.com means you're effectively starting from scratch on authority unless you've built up the subdomain's own link profile over time.
The drop happens because all the internal link equity, topical relevance, and crawl budget that accumulated under the subdirectory path gets severed. Even with proper 301 redirects, you're asking Google to re-evaluate the new location against a near-empty trust score. that's a reset, not a migration.
If you have to move, the playbook is:
- 301 each old subdirectory URL to the exact new subdomain URL - no wildcards, no homepage dumping.
- Update internal links site-wide to point to the new subdomain.
- Submit both old and new URL patterns in GSC and use the Change of Address tool if the subdomain is the new canonical home.
- Expect a 4-8 week volatility window while the subdomain builds its own authority. The parent domain's strength won't transfer automatically.
A colleague once ran a test: moved a 200-article blog to a subdomain, kept all redirects, and saw a 40% organic traffic dip for three months before it recovered. The subdomain had zero external backlinks of its own. That's the reality.
Skipped: detailed redirect map generation script. Add when you have more than 50 URLs to move and need to verify redirect chains programmatically.
