Ethan Smith runs Graphite, the agency behind Webflow’s answer-engine program. Ask him for the highest-leverage topic in AEO and he picks help centers. After his Lenny’s Podcast episode aired, he surveyed around 50 LinkedIn connections on what to cover next, and help-center optimization came back as the number one request (Ethan Smith, interview with Niklas Buschner). Fifty practitioners looked at the whole field and asked about the support docs.
The mechanics explain the enthusiasm. An answer engine building a response to a narrow question needs a citation for it. Smith’s example from the Lenny’s episode: which transcription tool integrates with Looker. Whoever wrote the one page answering that question wins the whole answer. No authority contest. No backlink budget. The page has to exist, and yours is the only one that does.
Your help center is a pile of pages like this. Support wrote them to keep customers off the phone line, which means each one is a narrow question and a direct answer, written by someone with no interest in adjectives. Ticket deflection and answer-engine material turn out to be the same genre.
Then you put all of it on help.yoursite.com, where crawlers treat it as a separate, weaker site, and forgot it existed.
Why does a help center win AI citations?
Because retrieval favors pages that answer one specific question, and a help center is hundreds of them. Smith’s on-site doctrine holds that a page competes for hundreds of questions through follow-up coverage: answer every follow-up in the cluster, and the subtopic nobody else covers earns the citation. A homepage fights ten rivals for “best meeting transcription tool.” A help article on exporting transcripts to Looker fights nobody.
Redundancy compounds the win. For “what meeting transcription tool integrates with Zoom,” Smith points out that Otter shows up with a help-center page, a feature page, a how-to article, and pages on Zoom’s own site (interview). His prescription: “Have multiple takes at answering this particular question.” Four pages aimed at one question is four draws from the citation pool.
What should you change first?
Move the help center from a subdomain to a subdirectory. Smith’s checklist runs four moves:
- Subdomain to subdirectory. help.yoursite.com becomes yoursite.com/help, so the articles inherit the main domain’s authority instead of building their own from zero.
- Cross-link the articles. Help centers ship as isolated dead ends. Linking related articles turns them into a cluster engines can traverse.
- Write the tail. Obscure integration questions, edge-case configurations, “does X work with Y” for every Y you support. Each article costs an afternoon and can be the only answer on the internet.
- Get partners publishing. Smith’s cheapest off-site play: have every integration partner publish a page about your integration, “and then you’ll show up twice” (interview).
Can a company with no domain authority win this?
Yes, and this is where AEO breaks from SEO. Smith’s advice to early-stage companies on Lenny’s: skip classic SEO, which takes years of authority building, and do AEO, where you can get cited tomorrow. One Reddit thread. One tail article answering a question nobody else bothered with. The moat that protects incumbents in Google rankings does not protect them from a startup writing the only page about a Looker integration.
Smith also concedes he has not mastered help-center AEO yet (interview). The person who named it his most exciting topic calls it open ground. An unusual market condition: the acknowledged best play in the field, unclaimed, available to whoever ships articles this quarter.
Keep the spend proportional. Smith’s caveat for seed-stage companies in the same interview: AEO might be their fifth most important channel, worth a light investment on a small number of prompts, and 10 to 15 tracked questions is enough for a small brand. The help-center play fits inside that budget. A batch of tail articles per week, each of which earns its keep as support content whatever the engines decide to cite.
The ten-minute version: pick five questions your buyers ask about integrations and setup, then check whether your help center answers them on your main domain. Our free scan runs five buyer questions through a live engine and shows the citations verbatim, including whether any of them are yours: run it. If your help center is absent from every answer, you now know which afternoon to spend.