Why this technical decision affects GEO ROI
“Should our blog live at blog.company.com or company.com/insights/?”
A seemingly pure-engineering question that directly affects how concentrated your GEO signals are. Years of blog content, media backlinks, third-party endorsements — whether those count toward your main domain or get scattered across subdomains can mean a 30–50% gap in main-domain authority by year five.
A common mistake we see: a decade of accumulated blog posts living at blog.company.com with almost no cross-linking to the main site — leaving AI engines unable to see that depth when they evaluate “how substantive is this company’s content.”
Below we break down four architectures and the criteria for choosing.
Architecture 1: Subdirectory — Highest signal concentration (recommended default)
Structure
example.com/
├── /insights/ ← blog
├── /docs/ ← documentation
├── /pricing/ ← pricing
├── /about/ ← company info
└── /zh/ ← multilingual variants
Why GEO signal concentration is highest
To search engines and AI, the whole site is one entity:
- Domain age is shared across all paths (
/insights/inherits the main site’s 5 years of age from day one) - External backlinks point at the root domain; every path benefits from that authority
- Internal linking is most natural within the same domain (
/insights/post-1→/products/abcreads as topical interlinking to AI, not cross-site references) - schema.org
Organizationis declared once and covers the entire site
What this means concretely for GEO
- Content citability / E-E-A-T: blog authors’ bylines feed straight into the whole-site E-E-A-T assessment
- Off-site visibility: media coverage of
example.com/insights/postand ofexample.com/products/abcboth accrue to the same domain - Wikipedia alignment: the official-site link on your Wikipedia entry points at
example.com, and every path benefits
When it fits
95% of sites should use this. Unless you have a specific strong reason (see the architectures below), default to subdirectory.
Engineering considerations
Implementation can be slightly more involved than subdomains:
- A reverse proxy (Nginx / Apache) is needed to route
/insights/to the blog service - CDN cache rules need care
- Some cross-path permission handling under the same-origin policy
These are solvable engineering problems. They shouldn’t drive an architectural decision.
Architecture 2: Subdomain — Fragmented signals, only for specific needs
Structure
example.com ← main site (product / about / pricing)
blog.example.com ← blog
docs.example.com ← docs
support.example.com ← support
zh.example.com ← Chinese variant
How Google / AI view subdomains
Google’s stance on subdomains has shifted over time:
- 2007–2015: subdomains computed PageRank independently (effectively separate sites)
- Post-2016: Google leans toward treating subdomains as part of the same site (Matt Cutts has clarified this multiple times)
- AI citation era: training crawlers (GPTBot / CCBot) still treat subdomains as relatively independent — they evaluate at the registered domain level for host-level assessment
Conclusion: for GEO, subdomains are more independent than Google thinks they are. Authority accumulated by blog.example.com does not fully transfer to example.com.
When subdomains make sense
Case A: the subsite is a separately incorporated business
- Subsidiaries with independent brand identities
- Each brand has its own contracts / customers / revenue
- Each brand has (or could have) its own Wikipedia entry
→ A subdomain accurately reflects the fact that this is a genuinely separate entity.
Case B: distributed deployment is unavoidable
- Main site on Cloudflare, docs on ReadTheDocs (auto-hosted on their subdomain)
- Status page on a third-party service (forces their subdomain)
→ Engineering reality. Acceptable.
Case C: independent regional / language operations
us.example.comis run by an autonomous US team with different content, pricing, and services- It’s not a translation — it’s a different market entity
→ The subdomain reflects reality.
When subdomains DON’T make sense
The most common misjudgments:
❌ “A standalone blog subdomain looks more professional” — pure aesthetic preference, no real GEO benefit
❌ “Putting docs on a subdomain makes team ownership cleaner” — internal org problems shouldn’t shape your external architecture
❌ “I see big companies using blog.company.com” — big companies can afford fragmented signals; you might not
❌ “Language subdomains are the proper way” — subdirectory + hreflang is better for GEO
Architecture 3: Separate sites — Only when entities are genuinely different
Structure
brand-a.com ← fully independent Brand A
brand-b.com ← fully independent Brand B
company.com ← holding company (if any)
When it fits
- A group operating multiple genuinely different brands (e.g. P&G running Tide, Crest, Head & Shoulders on entirely separate domains)
- Each brand has non-overlapping target customers, product lines, market positioning
- Each brand has (or could have) its own Wikipedia entry / media coverage history
What GEO looks like here
Every independent site needs a full GEO roadmap:
- Its own Organization schema
- Its own authority accumulation
- Its own Wikipedia notability story
→ Engineering load is N× the subdirectory option (N = number of independent sites).
When it DOESN’T fit
❌ One company running small sub-brands as experiments — neither the budget nor the time is enough
❌ Diverse product lines — these should live under the same domain via /products/ subdirectories
❌ Multi-region market — most cases are better off with subdirectory + hreflang
Architecture 4: Hybrid — Avoid
Anti-pattern
example.com ← main site
blog.example.com ← blog on subdomain
example.com/products/ ← but products on subdirectory
zh.example.com ← Chinese on subdomain
example.com/en/ ← but English on subdirectory
shop.example.com ← but shop is a subdomain again
Why this is the worst
Hybrid layouts usually come from:
- Different teams making different decisions at different times
- Acquisitions without integration
- “We’ll deal with it later” technical debt accumulation
GEO damage:
- Signals fragment beyond recovery: the path of authority propagation becomes unpredictable
- AI deprioritises “whole-site coherence” scoring: inconsistent architecture often correlates with org dysfunction
- Cross-platform alignment becomes ambiguous: which domain should Wikipedia / LinkedIn / media coverage point at?
Fix
Converge on one architecture — pick a path (subdirectory by default) and migrate everything to it.
Migration cost (short-term SEO/GEO dip + engineering re-org) is usually lower than the cost of perpetual chaos.
Multilingual sites: a special decision
Multilingual sites have extra considerations. Three options:
Option 1: Subdirectory (recommended)
example.com/zh/page
example.com/en/page
example.com/ja/page
- Paired with
<link rel="alternate" hreflang="..."> - Main-site authority concentrates on
example.com - Fits most cases
Option 2: Language subdomains
zh.example.com/page
en.example.com/page
ja.example.com/page
- Paired with hreflang
- Each language crawled independently
- Fits when each language has an independent team and substantially different content
Option 3: Country-specific top-level domains (ccTLD)
example.com ← global / US
example.com.tw ← Taiwan
example.co.jp ← Japan
example.de ← Germany
- Paired with hreflang
- Fits when there’s genuine country-level localisation, separate legal entities per country
Decision criteria
| Your situation | Recommendation |
|---|---|
| Languages are mostly translated versions of each other | Subdirectory |
| Each language has its own team and content strategy | Language subdomain |
| Each country has independent legal / business entities | Country ccTLD |
| All of the above apply but you have a 5-person team | Subdirectory (cut your cloth) |
4 common decision-making mistakes
Mistake 1: Deciding by “look at what big companies do”
“Google uses blog.google, so we should too” — you are not Google. Google can afford to maintain authority across many independent domains; you might not.
Mistake 2: Deciding by “what’s convenient for the current backend”
“WordPress is on this server, the main site is on that server — let’s just put it on a subdomain so deployment is easy.” This is the textbook case of engineering convenience overriding GEO signals. Slightly harder engineering is worth it to get the architecture right.
Mistake 3: Worrying that a subdirectory dilutes the blog’s identity
“The blog covers topics different from our main business — a subdomain keeps users from getting confused.” This is a psychological illusion. Users on example.com/insights/ aren’t confused, and AI isn’t either. If anything, blog.example.com weakens the topical connection between blog and main site.
Mistake 4: Discovering a hybrid mess after the fact
The most painful moment: five years in, 1,000+ posts accumulated, and you realise the architecture is wrong.
→ Prevention: lock in architectural decisions in the first 1–2 years. Be deliberate up front, then commit, to avoid hybrid drift.
Migration: subdomain to subdirectory, technical details
If you’re already on subdomains and need to migrate to subdirectories:
Step 1: build the new paths (without removing the old)
- Open
/insights/on the main site with content mirrored fromblog.example.com - Run both in parallel until you’ve verified content mappings
Step 2: 301 permanent redirects
blog.example.com/post-1 → 301 → example.com/insights/post-1
blog.example.com/post-2 → 301 → example.com/insights/post-2
Each old URL must map 1-to-1. Don’t redirect them all to the homepage.
Step 3: notify Google / Bing
- Submit a Change of Address in Google Search Console
- Same in Bing Webmaster Tools
- Update sitemap.xml
Step 4: wait for re-indexing
- Expect 3–6 months for full effect
- A 10–30% dip in SEO traffic during the transition is normal — set expectations with management in advance
- AI training corpus updates wait for the next model generation (6–18 months)
Step 5: keep the 301 redirects for at least 1 year
- Don’t rush to retire the old subdomain DNS
- Maintain the redirects for at least 12 months to catch long-tail traffic
Step one: audit your current architecture
Run these three checks:
- How many subdomains / cross-domain assets do you have? List them all.
- Do they cross-link with each other? Does your main site footer link to the subdomains? And vice versa?
- What does your official URL look like on media coverage / Wikipedia / LinkedIn? Is it consistent?
If you find a “hybrid mess,” architectural cleanup should come before content production.
👉 Run a GeoWeb health check to see your single-page signals — a health check covers per-page signals, but whole-site architecture problems need a site-wide audit to evaluate.
If you want a full site-architecture diagnosis and migration roadmap (including subdomain consolidation, multilingual architecture choice, 301 redirect strategy, index migration plan), that’s part of our GEO consulting service: contact@geoweb.tw
GEO deep-dive series. Previous: “SSR / SSG / SPA — How your rendering choice decides whether AI can cite you”
