Field guide · technical workflow
Plan a subdomain-to-subdirectory move around real URLs
Moving articles from blog.example.com to example.com/blog/ sounds like a simple prefix rewrite. That approach can miss old query parameters, media paths, language routes or articles that were already consolidated. The safest first unit is a complete old-to-new mapping table.
Who this is for: Help a multi-domain marketing lead preserve important blog or help-centre pages when consolidating a subdomain into the main website.
Editorial preview — facts, worked examples and publication approval are still being checked.
The practical problem
A practical plan a subdomain-to-subdirectory move around real urls exercise: Export real subdomain pages, attachments and historical redirects. The outcome is a documented decision backed by map each old path to a relevant owned folder destination. The final check is to verify old-host redirects and destination HTML on the final hostname.
What you will be able to check
- Export real subdomain pages, attachments and historical redirects.
- Map each old path to a relevant owned folder destination.
- Verify old-host redirects and destination HTML on the final hostname.
Reproducible scenario
Worked example: Plan a subdomain-to-subdirectory move around real URLs
A hypothetical software company maintains documentation on help.example.com while its marketing site lives on example.com. It wants to move help articles to /help/ so content and brand navigation feel unified. The documentation host has older API guides, images and PDFs, plus some URLs that already redirect. A simple hostname-and-prefix replacement risks losing language routes, media and intentionally consolidated guides.
Starting assumptions
- The old subdomain can continue serving redirects after the content is migrated.
- The intended subdirectory has confirmed routes and approved equivalent articles for the priority documentation topics.
Decisions and checks
Inventory the subdomain independently of its visible navigation
Use existing sitemaps, logs and a crawl to identify old help pages, assets, redirects and regional versions. Record which URLs matter to external users even if the redesigned help menu omits them.
What to verify: A complete priority mapping of actual old host URLs, asset paths and available demand evidence.
Map every retained content purpose to the right subdirectory page
Where an article remains a standalone help topic, preserve that specific destination. Where several outdated guides are consolidated, review that the new content genuinely answers them. Avoid sending all retired help paths to /help/ merely for convenience.
What to verify: A signed route list of source host/path, relevant new /help/ destination, old content owner and intentional exceptions.
Verify old-host redirects and new-host canonical content
Check that requests to help.example.com still return appropriate permanent redirects, and that the new pages use the canonical main domain. Test nested image and PDF links and language routes rather than checking only the help homepage.
What to verify: End-to-end HTTP traces and rendered new pages show appropriate destinations, useful content and working assets after cutover.
Expected output: A credible subdomain consolidation keeps the old host working for redirects while ensuring each important article survives in the right new path. The release owner can explain content merges and any retired assets rather than claiming a simple regex fixed everything. Search visibility outcomes remain subject to real indexing and user behaviour after the move.
This subdomain to subdirectory seo move migration story is hypothetical and is not an observed client cutover or verified ranking result.
Identify more than the visible article list
Collect old subdomain sitemaps, crawls, search landing pages and important downloadable documents. Include article assets, index pages, redirects and any language alternate paths. Check whether the new root site already has competing pages covering the same intent.
Reference: official · 2026-11-07
Decide where each source page belongs
Map each source article to a matching destination with a clear content owner. Where two articles are being merged, record the expected replacement and check that the new page is actually useful to readers arriving from the old URL. A sitewide blanket redirect to /blog/ cannot substitute for those decisions.
Reference: official · 2026-11-07
Check canonical and discovery after the switch
Test the old host's redirect responses and the new folder's self-referencing canonicals, internal links and sitemap entries. After launch, monitor both old and new properties where possible and preserve the source host long enough to serve permanent redirects.
Reference: official · 2026-11-07
Decision aid
Decision table: Move a blog subdomain into a folder: SEO QA
| Legacy issue or URL class | Relevant decision | Real evidence required |
|---|---|---|
| Legacy documentation article has a direct new equivalent | Map to the same topic under /help/ with a meaningful redirect. | Compare source topic, final content and canonical destination. |
| Two older guides are consolidated into one complete tutorial | Review merged coverage before sending both old URLs to one target. | Keep source outlines and evidence the new guide answers both tasks. |
| Old media file is used by an external integration guide | Maintain access or a suitable replacement without losing the download path. | Check old asset requests, final media response and linked article. |
What a passing test looks like
These checks describe the evidence that should exist after a real implementation. They are not reports of tests already completed on a customer website.
Inventory the subdomain independently of its visible navigation
Expected result: A complete priority mapping of actual old host URLs, asset paths and available demand evidence.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for inventory the subdomain independently of its visible navigation.
Map every retained content purpose to the right subdirectory page
Expected result: A signed route list of source host/path, relevant new /help/ destination, old content owner and intentional exceptions.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for map every retained content purpose to the right subdirectory page.
Verify old-host redirects and new-host canonical content
Expected result: End-to-end HTTP traces and rendered new pages show appropriate destinations, useful content and working assets after cutover.
Keep as evidence: Archive the exact source URL requests, final destination and reviewer signoff for verify old-host redirects and new-host canonical content.
Scope and limitations
The help.example.com addresses and product context are invented. Some hosting providers have different control over cross-host rewrites and canonical headers. The exercise does not validate a real site's assets or localization; it requires actual URLs, old-host access and live monitoring before a production migration can be approved.
Sources and verification
These references explain documented technical behaviour. The worked decisions are illustrative until checked on your own installation.
- official reference — Google recommends preparing mappings and retaining relevant permanent redirects for domain and path changes while monitoring the transition. Recorded: 2026-11-07