New researchTechnical SEO & AI Search · 2027Explore the framework

Subdomain to subfolder SEO migration: move URLs without losing pages

Move blog.example.com to example.com/blog/ with a URL map, direct redirects, updated signals and a practical post-launch verification plan.

Part of the Site Migrations series. For the full picture, start with Site migration SEO checklist: crawl before, during and after launch.

Moving blog.example.com/article/ to example.com/blog/article/ looks like a tidy structural change. To search engines and visitors, it is a new address for every article, image and archive you move. The safe way to handle a subdomain-to-subfolder SEO migration is to treat it as a URL migration, not a navigation tweak.

How do you plan a subdomain-to-subfolder SEO migration?

Start with a complete old-to-new URL map. Google’s site move guide recommends collecting important URLs from sitemaps, analytics, links and logs before configuring redirects. Crawl the old subdomain and export every indexable article, category, pagination page and asset that has a public URL.

Old URL New destination Check before launch
blog.example.com/guides/a/ example.com/blog/guides/a/ Same article and intent
blog.example.com/news/old/ Closest updated article, or 404/410 Do not force it to the homepage
blog.example.com/uploads/chart.png New image URL or retained asset Article references and image traffic

A wildcard rule can handle a simple one-to-one path pattern, but only after exceptions are identified. Keep a separate list for renamed articles, merged content, deleted pages, feeds and non-HTML assets. Benchmark search clicks and impressions for the old blog URL group so the post-launch comparison is meaningful. For the wider process, use the site migration checklist.

Which redirects and page signals need changing?

Each moved URL should return a direct permanent redirect to its corresponding new URL, normally 301 or 308. Google’s site-move guidance says to avoid long chains and irrelevant many-to-one redirects. Test the mapping before launch, then verify the live response and final page, not just that a redirect exists. Our redirect mapping guide covers the spreadsheet and QA in depth.

The destination page should return 200, be indexable when intended, and self-canonicalize to the new URL. Remove staging noindex rules. Update the XML sitemap, internal article links, navigation, breadcrumbs, structured-data URLs and any hreflang annotations that refer to the old host. If images move, update their references too. These are separate checks: a working redirect does not repair an old canonical on the destination.

Do you need Search Console Change of Address?

Do not make it a default step for a subdomain-to-path move. Google’s site-move instructions describe Change of Address for moving from one domain or subdomain to another, and say it is not needed for paths within the same domain. A move from blog.example.com to example.com/blog/ crosses a host boundary but ends at a path on an existing host, so check the tool’s current eligibility for your exact verified properties instead of promising it will accept the move.

The core signals do not depend on that tool: working redirects, updated links and canonicals, a new sitemap, and observation of both the old and new URL sets. Verify the old subdomain and destination property in Search Console so you can see crawl and performance data on each side.

How do you test the move before and after launch?

Before launch, crawl a staging copy of the new /blog/ section if possible. Check title, content, canonical, robots directive, status, internal links and structured data on representative pages. Confirm the new blog is reachable from the main navigation and that there is no accidental duplicate copy left indexable on the old host.

After launch, re-crawl the complete old URL list with redirects enabled. Flag old URLs that return 200, 404 unexpectedly, redirect to unrelated pages or pass through multiple hops. Then crawl the destination section and inspect a sample in Search Console. Google’s guide notes that visibility can fluctuate while the move is processed; a single day’s dip is less informative than whether the mapping and indexing trends are healthy.

Monitor the old and new URL groups together. Old-host impressions should eventually give way to the new paths, while total relevant traffic is the business measure. Watch server errors, excluded destination pages, canonical mismatches and links still pointing at the subdomain. If traffic drops persistently, use the migration traffic-drop diagnosis to separate migration defects from other causes.

Subdomain to subfolder migration checklist

  • Inventory old blog pages and important assets from crawl, sitemaps, logs and analytics
  • Map each old URL to an equivalent new URL or an intentional removal
  • Test direct permanent redirects, including unusual slugs and non-HTML files
  • Update internal links, navigation, canonicals, schema URLs and sitemaps
  • Confirm destination pages are accessible and indexable on mobile and desktop
  • Verify both host properties and submit the new sitemap
  • Re-crawl old and new URL sets; monitor errors, indexing and combined performance
  • Keep redirects long-term and replace old links under your control

The successful move is not the one with the shortest redirect rule. It is the one where every valuable old page still has a clear destination and a testable trail.

Frequently asked questions

Will moving a blog from a subdomain to a subfolder improve rankings?

Not automatically. A subfolder may simplify site navigation and management, but the URL change itself creates migration risk. Make the move for a clear site or business reason, then protect the pages and signals already working.

Is a wildcard redirect enough for a subdomain-to-subfolder move?

Only if every old path has exactly the same new path and no exceptions. Build a URL inventory and test top traffic pages, nonstandard slugs, archives, attachments and deleted content individually.

Should I use the Search Console Change of Address tool?

Do not assume it applies to a move into a path on an existing host. Google's site-move guide describes the tool for domain or subdomain moves and excludes path moves within the same domain. Check current tool eligibility for the exact source and destination, and rely on URL redirects and monitoring regardless.

How long should old subdomain redirects remain?

Google recommends keeping redirects for as long as possible, generally at least one year. Keeping them indefinitely is often best for users and old external links, while updating links you control to the new URLs.

· Founder, Crawlens

Dien builds Crawlens, a desktop crawler for technical SEO audits, and writes about the checks it runs: crawling, indexing, rendering and Search Console data.

Audit your own site with Crawlens

Crawl, run 70 checks, and see them next to Search Console and Core Web Vitals data.

Download free for Windows