Help Center Optimization for the Tail
Turn your support docs into the citation source for obscure use-case questions
- Difficulty
- Easy
- Time to result
- ~weeks to results
- Steps
- 3
- Confidence
- 85%
Because chat users ask specific 'can your product do this?' questions about features, integrations, and use cases, the help center becomes a powerful and underused AEO surface. Three fixes unlock it: move the help center from a subdomain to a subdirectory, cross-link help pages heavily, and fill the long tail of obscure use-case questions your docs don't currently cover — often making you the only citation for that question.
Origin
Ethan Smith calls this his most exciting under-discussed AEO topic; support/help-center content is normally ignored by SEO teams.
Core principles
- 01Chat surfaces feature/integration/use-case questions that map directly to help content
- 02Subdomains underperform subdirectories for whatever reason
- 03Internal cross-linking of help pages is usually missing and worth fixing
- 04The obscure tail of use cases is often uncovered by anyone — win it by being the sole citation
How to run it
- 1
Move the help center to a subdirectory
Relocate help content from a subdomain (help.example.com) to a subdirectory (example.com/help) because subdomains don't perform as well.
Watch out Most help-desk tools default to subdomains, so this often requires a deliberate migration.
- 2
Cross-link help pages
Add strong internal links from help-center page to help-center page, since these are typically poorly linked.
- 3
Fill the long tail of use-case questions
Identify obscure but non-zero use-case questions from sales calls and support, then create help articles for them; optionally open the help center to community questions so users populate the tail themselves.
Pro tip Opening it to the community lets anyone ask anything, which fills the tail faster than you can alone.
Watch out These use cases are obscure, so justify them by being the only citation rather than by volume.
In the wild
Ethan searched for a meeting tool that integrates with Looker; none does directly, but Otter plus a Zapier integration into BigQuery then Looker works. No help-center article existed for this obscure-but-real workflow.
→ A company that documented this tail question could become the sole citation and win that answer.
Common mistakes
Ignoring the help center as an AEO surface
SEO teams rarely target support docs, yet chat users constantly ask capability/integration questions that help articles are perfectly suited to answer and get cited for.
Is it for you?
Best for
B2B SaaS growth/support teams whose products have many features, integrations, and niche use cases
Not ideal for
Simple products with few use cases or companies without the resources to maintain a deep help center
From the transcript
“the most exciting topic which is help center optimization and support”
“it's frequently on a subdomain. For whatever reason, subdomains don't work well as subdirectories. So move it to a subdirectory”
“link from help center page to help center page”
“you could be the only citation for this and then win that uh tale of questions”
From the episode
The ultimate guide to AEO: How to get ChatGPT to recommend your product
Ethan Smith (Graphite)