Write for customer questions because people increasingly ask full, specific questions in Google’s AI search, ChatGPT, Gemini and Perplexity, and those systems break the question into subtopics before searching — so a page built around one real question is the unit that gets retrieved, selected and cited. Keyword research is not dead: keywords still tell you which topics are worth covering and in what order. What changed is that keywords scope the topic, and questions define the page. Building the brief is a four-step procedure: collect questions from support tickets, sales calls, reviews and forums, dedupe them into intent boundaries, assign one page per question, and structure each page answer-first.
What changed in how people search?
Google describes the shift in its own words. In its May 2025 guidance on succeeding in AI search, John Mueller writes that “users are asking longer and more specific questions — as well as follow-up questions to dig even deeper” (Google blog, 2025-05-21). The practical consequence: the unit of search is moving from short keyword phrases to full-sentence questions, and AI surfaces answer those questions by fanning them out into several subtopic searches at once.
Google’s AI Mode support page (undated, live — accessed 2026-10-29) describes the mechanism: AI Mode uses “query fan-out,” dividing your question into subtopics and searching for each one simultaneously across multiple data sources, with responses “supported by high quality web content to improve factuality.” That is the same mechanism our how AI answers are generated post walks through stage by stage: one user question becomes several retrievals, each one matched against citable pages in the index.
Practitioners describe the same shift in plainer terms. In an August 2026 r/localseo thread, “writing for keywords instead of customer questions” is listed as mistake number one in content strategy: “People are asking full questions in Google’s AI Mode, ChatGPT, Gemini, Perplexity, Maps. Content built around a keyword instead of a real question is optimized for a search behavior that’s disappearing.” That is forum reporting, not a measurement — but the primary-source half of the claim (longer, more specific, follow-up questions) is Google’s own, as above. Practitioners also report AI Mode queries running roughly three times longer than classic search; that figure has no primary source, so treat it as directional, not as data.
Why do keyword lists fall short?
A keyword list answers a real question — which topics to cover, in what priority order — and that job is still the job of keyword research: volume, seasonality and intent data decide the sequence in which you build. What a keyword list cannot tell you is what any single page is. Several different people type the same keyword with different needs, and one page cannot serve two different needs at full depth. A page’s identity has to come from a question, because a question names the asker’s intent boundary.
The rule this method rests on is the one our own posts follow: one page, one intent, one H1. A keyword can map to several intents — “pricing” means what does it cost, is it free, and how do you negotiate — while a real customer question maps to exactly one. Derive pages from a keyword list and the two failure modes are predictable: one page stretched across several intents at half depth, or two pages targeting the same intent, which is keyword cannibalization and the reason that post’s whole fix exists.
Google’s creating helpful content documentation contains the question this method exists to pass: “Do you have an existing or intended audience… that would find the content useful if they came directly to you?” Its warning sign is the failure mode of the keyword list: “Are you writing about things simply because they seem trending and not because you’d write about them otherwise for your existing audience?” A keyword with no question behind it is exactly a trending topic. And Mueller’s same May 2025 post points at the remedy — “Focus on making unique, non-commodity content” — because commodity content is what you get when ten briefs are generated from the same keyword list.
How do you build a brief from real questions?
You build the brief from questions you can actually hear, copied verbatim. The four reliable sources for a business are support tickets (what customers ask your team), sales calls (what prospects ask before buying), reviews (of your product and of competitors’), and forum questions (Reddit, Quora and niche communities, where the question is typed the way a stranger would type it). A local shop has the same four in different forms: phone calls, Google reviews, neighborhood and category forums. Nothing else is needed to start.
| Step | What to do | Notes |
|---|---|---|
| 1. Collect questions verbatim | For a few weeks, copy the actual phrasing of real questions from tickets, sales calls, reviews and forums into one list. | Verbatim matters: the phrasing is the intent. “How do I cancel my subscription?” and “is there a monthly plan?” are different intents wearing the same topic. |
| 2. Draw the intent boundary | For each question, write one sentence: who is asking, what a complete answer covers, and where it stops. | Two phrasings with the same boundary collapse into one question. One phrase with two boundaries splits into two pages. This is the dedupe step — do it once, before writing. |
| 3. Assign one page per question | One intent boundary = one page. Before writing, check your own site: if a page already owns the boundary, update it instead of publishing a new one. | This step is what prevents keyword cannibalization: the brief enforces one page per intent before the content exists, instead of cleaning up after. |
| 4. Structure the page answer-first | Bold lead states the answer in 1–3 sentences; H2s are question-shaped; each section opens with its direct answer before it expands. | This is the structure this site’s posts follow — and the reason in the next section, not decoration. |
Two practical notes. First, the list is a sampling of the business’s real question stream, not a research artifact — if a source is empty, that is information too (nobody asks you about that thing, so you probably don’t need a page). Second, keyword research comes back at the end of the list, not the start: once the question is chosen, the keyword data tells you demand and priority, so the question that has both real askers and real volume gets written first.
How do you write a question-shaped page?
A question-shaped page leads with the answer to its question in a bold first paragraph, uses question-shaped H2s for each sub-question it owns, keeps every entity name consistent throughout, and puts examples, evidence and detail after each direct answer — never before it. The structure exists for extraction, not style: when an answer engine retrieves a page, it often works from one or a few passages, so each section has to be self-contained, and the sentence the reader actually needs is never buried under throat-clearing. The mechanics of extractable passages are covered in what makes content AI-citable; the point here is that the brief — written from a question — is what guarantees there is one answer to front-load.
Entity consistency is the machine-readable half of the same discipline. Name the product, the company and the key terms identically everywhere the page appears — headings, prose, tables, structured data — so the page’s subject is unambiguous to a system binding a claim to a source. A page that keeps saying three different things about the same thing is a page a model cannot confidently cite.
What about FAQ schema? Question-shaped markup (FAQPage structured data) no longer earns a visual result on Google. The timeline: on August 8, 2023, Google restricted FAQ rich results to well-known authoritative government and health sites (Google blog); in May 2026, FAQ rich results were removed for all sites. The May 2026 removal is third-party corroboration rather than a primary announcement we could verify — but the state of Google’s documentation is directly checkable: the FAQ structured-data doc page is now a 404, and Google’s structured-data gallery (last updated 2026-10-16) no longer lists FAQ. The practical read: question markup no longer buys a visual result, but question-shaped content still serves people and retrieval. That is the direction the tooling was always a shortcut toward, not a substitute for.
Does writing for questions guarantee AI citation?
No — and nothing in this method should be read as a promise. Google’s guardrail is explicit in its AI features documentation: “There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary.” Question-shaped content is not a special optimization; it is ordinary content work done from a better starting point. It makes each of your pages a better candidate — unique, specific, non-commodity, answering a named need, which is what Google says it wants to show (“Google wants to show content that fulfills peoples’ needs,” Mueller, May 2025) — but the citation is a selection decision made against every other source retrieved for the same subtopic, and no on-page technique alone guarantees it. The honest framing: writing for questions is what you should be doing for your customers anyway; AI retrieval is where that work pays, not a guarantee you can buy from the method.
Where to start
Pick the ten questions your business was actually asked this week, run them through the four steps, and publish one question-shaped page — the one with the clearest intent boundary and the most real askers. One prerequisite before any of it: the page has to be reachable and readable in the first place, so confirm the technical floor with the nine-item technical SEO hygiene checklist before the content work starts. Then place it in its cluster: one page per question, linked up to a pillar, as in content clusters for topical authority. If you want the whole system — the question capture, the briefs, the cluster map, and a baseline of where AI surfaces currently stand so you can tell afterward whether it worked — that is what we run end to end, and the process is in our methodology.