The Help Center Pivot
by Ethan Smith • CEO at Graphite
An SEO veteran with 18 years of experience, Ethan specializes in SEO and programmatic SEO strategies. He is the CEO of Graphite, a leading agency helping companies like MasterClass and Webflow build scalable growth channels.
🎙️ Episode Context
Ethan Smith joins Lenny to decode the rapid shift from traditional SEO to Answer Engine Optimization (AEO). They explore how LLMs and RAG (Retrieval Augmented Generation) are changing search behavior, why 'share of voice' in citations matters more than ranking number one, and provide a tactical playbook for influencing AI answers through Reddit, YouTube, and help centers.
Problem It Solves
Captures the massive 'long tail' of specific feature/integration questions (25+ words) that users ask LLMs but rarely search for in Google.
Framework Overview
Transforming the product help center from a support archive into a primary AEO acquisition channel by restructuring technical content to answer specific 'Can you do X?' questions.
🧠 Framework Structure
Subdirectory Migration: Move the help...
Internal Graphing: Implement aggressi...
Tail Gap Analysis: Mine sales calls a...
Community Extension: If an official a...
When to Use
For complex B2B products with many integrations, features, or technical nuances that users query via chat.
Common Mistakes
Leaving the help center on a subdomain or only writing articles for high-volume keywords, ignoring the zero-volume long-tail queries that LLMs thrive on.
Real World Example
Ethan's own search for 'Which meeting transcription tool integrates with Looker?' yielded no results initially; a company using this strategy would create a specific help page or community thread for that exact integration path.
If you map out all of the questions that people ask... the size of the tail is larger [in chat]... and there's probably questions that have never been asked before and questions that have never been searched before.
— Ethan Smith