Community-Led Programmatic Content Engine
Convert real customer questions into discoverable, intent-specific pages
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 7
- Confidence
- 96%
Gather authentic questions from community discussions, review sites, support conversations, and other customer-language sources. Use AI to normalize and cluster those questions by intent, then identify specific mid- and bottom-funnel needs that conventional keyword tools may report as having no volume. Prioritize clusters where the company has a useful, credible answer and create focused landing pages, comparison pages, guides, or FAQ modules. The purpose is not to publish hundreds of superficial variants; each page must resolve a materially distinct question with accurate evidence and natural customer vocabulary. This creates a broader surface area for conversational and AI search, where users express far more varied queries than they did through traditional keyword search. Performance data and new community conversations continuously refine the content map.
Origin
Jesus Raka at Sanity described scraping community conversations and turning recurring product questions into pages designed for both customer discovery and AI search.
Core principles
- 01Start with questions customers actually ask
- 02Prioritize specific mid- and bottom-funnel intent
- 03Use community language rather than keyword-tool abstractions
- 04Create pages that answer materially different needs
- 05Treat zero reported search volume as inconclusive
How to run it
- 1
Collect authentic questions
Export relevant community threads, support questions, reviews, sales conversations, and search queries. Retain the original phrasing and surrounding context.
Pro tip Include negative and comparative discussions, not only enthusiastic community posts.
Watch out Respect platform terms, privacy obligations, and customer confidentiality.
- 2
Extract and normalize intent
Use AI to identify explicit and implicit questions, merge close variants, and preserve meaningful differences. Label the buyer stage and desired answer for each question.
Pro tip Keep representative verbatim wording alongside every normalized question.
Watch out Aggressive clustering can erase distinct use cases.
- 3
Create intent clusters
Group questions by problem, audience, environment, alternative, and decision stage. Separate informational curiosity from commercially relevant evaluation intent.
Pro tip Prioritize mid- and bottom-funnel clusters where specific answers influence action.
Watch out Do not use reported search volume as the only evidence of demand.
- 4
Prioritize answerable opportunities
Score clusters by frequency in customer data, strategic relevance, competitive coverage, and the company's ability to provide a credible answer. Select only clusters that warrant distinct content.
Pro tip Look for recurring questions competitors have not addressed clearly.
Watch out A unique query is not automatically worth a new page.
- 5
Generate useful content
Build a page or FAQ module that directly answers the question with product facts, examples, limitations, and supporting evidence. Use the community's vocabulary naturally.
Pro tip Choose the lightest format capable of resolving the intent.
Watch out Do not mass-publish near-duplicate pages with swapped keywords.
- 6
Apply editorial quality control
Review each output for factual accuracy, distinct value, internal links, tone, and suitability for indexing. Consolidate pages that do not deserve independent treatment.
Pro tip Require a human owner for claims involving competitors or product limitations.
Watch out Unreviewed programmatic content can create misinformation and search-quality risks.
- 7
Measure and refresh
Track discovery, assisted conversions, engagement, and the questions that lead users to each page. Update the clusters and content as the community's needs change.
Pro tip Use new support and sales questions as a continuous feedback stream.
Watch out Traffic alone may overvalue broad informational pages that do not help customers decide.
In the wild
A marketing team scrapes discussions around its product, identifies common questions, and generates focused pages that answer what community members are already asking. The pages make those answers easier to find on the website and more available to AI search systems.
→ Authentic community demand becomes a scalable, discoverable content roadmap.
A software company extracts recurring questions and concerns from product reviews, clusters them by buyer intent, and creates evidence-backed FAQ sections for the most commercially important topics.
→ The site addresses niche evaluation questions that traditional keyword research overlooked.
Common mistakes
Generating thin page variants
Pages that differ only by wording create little customer value and can damage overall content quality.
Trusting keyword volume alone
Specialized questions may matter to real buyers even when traditional tools report no measurable volume.
Ignoring community context
Extracting a question without its surrounding situation can lead to an answer aimed at the wrong audience or intent.
Is it for you?
Best for
It is best for products with active communities, substantial support data, reviews, or recurring customer questions.
Not ideal for
It is not ideal for sites lacking authentic question data or the capacity to quality-control many generated pages.
From the transcript
“he's scraping community conversations that happen around their product uh and using that to essentially create landing pages”
“you know from looking at your community data that people are actually talking about this stuff.”
“it gives you a leg up based on what you know your own community cares about”
From the episode
9 ChatGPT Use Cases from the Top 1% of Marketers