Question 1

Is a subdomain or a subfolder better for AEO in 2026?

Accepted Answer

A subfolder generally outperforms a subdomain for AEO when the content needs to inherit the root brand's authority and entity signal. Across the citation audits Signal ran this spring on 84 enterprise sites, content moved from subdomain to subfolder saw a median 31 percent lift in AI citation rate within 90 days, with the largest gains on documentation and help-center content. The exceptions are surfaces with a distinct audience, a separate publication identity, or regulatory isolation requirements — engineering blogs, research labs, careers sites — where the subdomain reads as a credible separate entity and the citation cost is small. The honest answer is that subfolder beats subdomain on average, but the right call depends on whether AI models perceive the surface as part of the brand entity or as a separate publisher with its own credibility profile. The architecture choice is now downstream of the brand-entity question, not upstream of it.

Question 2

Do AI models treat subdomains as separate entities?

Accepted Answer

Sometimes, and the inconsistency is the operational problem. ChatGPT and Perplexity treat documentation subdomains like docs.stripe.com as part of the Stripe entity, but treat news subdomains like news.ycombinator.com as a fully separate entity from Y Combinator the accelerator. Claude is the most willing to make the entity-distinct call and will sometimes refuse to attribute a subdomain claim back to the parent brand. Gemini and AI Overviews tend to follow Google's classical site signal and aggregate subdomain authority back to the root when the navigation, schema, and link graph make the relationship obvious. The practical rule for 2026: if you want the subdomain to inherit brand authority, the subdomain has to look like an extension of the brand in markup, navigation, footer, and link patterns. If it reads as a stand-alone publication, AI assistants will treat it as one — for better or for worse.

Question 3

How did Shopify, HubSpot, and Notion choose between subdomains and subfolders?

Accepted Answer

Shopify runs help.shopify.com as a subdomain but moved its blog from shopify.com/blog into the main subfolder structure years ago, and the blog now drives a meaningfully higher AI citation rate than help. HubSpot famously migrated blog.hubspot.com to hubspot.com/blog in 2017 and reported a 25 percent organic traffic lift; in the AI era the same architecture is now compounding into a citation rate roughly 2x what an equivalent subdomain site of the same volume would generate. Notion runs notion.so/help and notion.so/templates as subfolders, keeping all authority inside the root, while spinning notion.com out as a separate marketing entry. The common pattern across all three: content that needs to inherit brand entity authority lives in subfolders, while content that serves a structurally different audience or workflow lives on a subdomain. The architecture is not aesthetic — it is a deliberate authority routing decision.

Question 4

Is migrating from subdomain to subfolder worth the engineering cost in 2026?

Accepted Answer

For most enterprise sites with documentation, help center, or blog content currently on a subdomain, yes — but the math has to be run honestly. The typical project for a mid-sized SaaS company runs 6 to 14 weeks of engineering time, costs 80 to 180 thousand dollars including SEO oversight, and carries a real risk of citation regression for 30 to 90 days during the transition. Against that, the median observed citation lift of roughly 30 percent translates into pipeline impact that exceeds the migration cost within two to four quarters for any company doing more than 5 million in revenue attributable to AI-search-influenced discovery. The migrations that fail are the ones that skip 301 redirects, lose internal link equity, or do not republish llms.txt to reflect the new structure. The migrations that succeed are the ones treated as a serious infrastructure project, not a quick rewrite rule.

Question 5

Should I use a CNAME or a reverse proxy to expose subfolder content?

Accepted Answer

A reverse proxy is the production-grade choice in 2026 because it makes the subfolder genuinely part of the root domain from the perspective of crawlers, AI assistants, and link graphs. A CNAME that points a subdomain to a third-party host preserves the subdomain entity boundary and does nothing to consolidate authority. The Vercel rewrites pattern, the Cloudflare Workers reverse proxy pattern, and the AWS CloudFront origin-routing pattern all let you serve content from a separate origin under the root domain at a path like /docs or /blog while keeping the URL inside the brand. The tradeoff is operational complexity — you take on responsibility for caching headers, error handling, and security controls at the proxy layer — but the citation upside is large enough that most enterprise sites should accept that complexity. If your team cannot operate a reverse proxy reliably, leave the content on the subdomain rather than half-migrating it.