Does Google really treat subdomains as separate sites?

Mostly. Google's official position is nuanced — they 'understand the relationship' between subdomains and the main domain. In practice, ranking signals don't flow as freely between them as they do within a single host. The consolidation effect is real and measurable, especially for commercial-intent terms close to the ranking threshold.

Will I lose backlinks pointing at the subdomain?

No. 301 redirects pass essentially all link equity. The links continue to count for SEO; they just point to URLs that now resolve to the main domain via redirect.

What if my subdomain runs on a fundamentally different platform?

The reverse-proxy pattern (Pattern A in the engineering section) lets you consolidate without re-platforming. It adds ongoing infrastructure complexity but lets you capture the SEO benefit without rebuilding the CMS.

Are there cases where subdomains rank better than subfolders?

In some niches, especially when the subdomain has been heavily resourced and the main domain hasn't, subdomains can outrank subfolder competitors. But this is the exception, not the rule, and it usually means the main domain isn't being given enough attention — not that subdomains are inherently better.

How long should the consolidation project take end-to-end?

Pattern A (reverse proxy): 2–4 weeks. Pattern B (CMS migration): 6–14 weeks depending on content volume. Pattern C (static export): 1–2 weeks but only viable for low-cadence blogs.

What about consolidating in the other direction — subfolder to subdomain?

Almost never the right answer for SEO. The only legitimate reasons to move a subfolder to a subdomain are technical (separate stack required, distinct audience justified by intent) or organizational (different teams, different governance). Don't do it for SEO reasons — you'll lose equity, not gain it.

Subdomain → Subfolder Consolidation: A Canadian SEO Migration Guide (2026)

The migration in one paragraph

Google treats subdomains as semi-separate sites. A blog at blog.yourdomain.ca accumulates topical authority that doesn't fully consolidate with yourdomain.ca's authority on commercial pages. Moving the blog to yourdomain.ca/blog/ — with proper redirects and consolidated internal linking — typically lifts rankings on commercial-intent pages within 60–90 days. The migration is technically simple but operationally risky if the subdomain is on a separate stack (different CMS, different hosting, different team). Consolidate when the equity benefit clearly outweighs the engineering cost.

When consolidation is worth doing

Your blog has strong topical authority but the main domain doesn't
Most common situation. Years of content investment in blog.yourdomain.ca have built domain authority that isn't flowing to your commercial pages. Consolidation lets it flow.
Your subdomain is on the same brand
blog.yourbrand.ca makes sense to consolidate. status.yourbrand.ca (a status page) doesn't — different audience, different intent.
You're rationalizing infrastructure anyway
If the subdomain is being replatformed, consolidation is a natural part of the work. If everything else is stable, the engineering cost is harder to justify.
The main site has stronger backlink profile
If main domain has 10x the authoritative backlinks of the subdomain, consolidation amplifies the subdomain's content reach. Reverse case: consolidation may dilute the subdomain's standalone strength.

When to leave the subdomain alone

The subdomain serves a clearly distinct audience
developers.yourbrand.ca for technical docs, support.yourbrand.ca for help articles. Audience separation is a feature, not a bug.
Engineering cost is high and SEO upside is modest
If the subdomain runs on a separate stack and the consolidation requires re-platforming, the SEO benefit needs to be substantial to justify it.
The subdomain is geographically separated
ca.yourbrand.com vs us.yourbrand.com — these are intentionally separate for hreflang and market reasons.
Risk tolerance is low and the site is mission-critical
Any migration carries risk. If the site can't afford a 14-day transient ranking dip, defer until you have a low-traffic window or the project owner can absorb the variance.

The engineering plan

Three architecture patterns work. Pick based on the subdomain's tech stack and your team's appetite for ongoing complexity.

Pattern A: Reverse proxy at /blog/
Main site continues running. Add a reverse-proxy rule (Nginx, Cloudflare Workers, Vercel rewrites) that fetches blog content from the existing subdomain backend but serves it under yourdomain.ca/blog/. Lowest engineering cost; preserves the existing CMS.
Pattern B: Migrate the CMS into the main site
Move WordPress/Ghost/Webflow content into the main site's CMS. Highest engineering cost; cleanest long-term operation.
Pattern C: Static export and re-host
Export the blog as static HTML, drop it under main-site /blog/. Loses CMS editing capability — only viable if blog cadence is low or you accept publishing through dev-pipeline.

Redirect strategy

Every blog.yourdomain.ca URL needs a 1:1 redirect to yourdomain.ca/blog/{matching-path}. The mapping is typically straightforward (the slugs don't change), but the implementation has to be at the DNS/server level so it's bulletproof.

Implement at the subdomain's web server
Nginx or Apache 301 rules that catch every URL and rewrite the host. Don't rely on application-level redirects — they're slower and easier to break in deploys.
Preserve query strings and fragments
blog.yourdomain.ca/post?ref=newsletter should redirect to yourdomain.ca/blog/post?ref=newsletter, not just yourdomain.ca/blog/post. Test this.
Keep the subdomain's redirect rule active for 12+ months
Long after Google has re-crawled, you'll still see traffic from old bookmarks, social shares, and email links. Remove the rule too early and you orphan all of it.
Update sitemaps
Remove the subdomain's sitemap. Add the new URLs to the main site's sitemap. Submit both changes to GSC.

Internal-linking consolidation

The whole point of consolidation is internal-link equity flow. Audit and rebuild:

From blog content to commercial pages
Blog posts that mention services should link to /services/{service}/. Where appropriate, work in CTAs that drive readers from informational to commercial intent.
From commercial pages to blog content
Service pages should link to relevant blog posts where they add depth. This is now equity-flowing both ways within a single domain.
Across blog content (related posts)
Use the migration as a chance to clean up orphan posts — pages that no other page links to. Add at least 2 internal links to each from related posts.
Update top-50 high-value backlinks if you control them
Author bios, partner sites, syndication feeds. The 301 will preserve equity, but a direct link is always slightly stronger.

Consolidation works because it lets one strong signal carry to many pages instead of two weaker signals competing.

— Martin Vassilev, founder, Toronto SEO

The 60-day measurement window

Don't expect dramatic week-1 impact. Consolidation pays off as Google re-crawls, reassigns equity, and updates internal weights. The pattern we see consistently:

Window	Expected behaviour
Days 0–7	Volatility on both old subdomain and new subfolder URLs. Some short-term ranking dips on blog content. Normal.
Days 8–30	404s drop as Google completes re-crawl. New subfolder URLs start ranking where the subdomain previously did.
Days 30–60	Commercial-intent pages on main domain often see 5–20% ranking improvement on terms they were close to ranking for. The consolidation effect.
Days 60–90	Stabilization. Compare your top 50 commercial-intent keywords vs pre-migration. If consolidated equity helped, this is when it shows up cleanly.