Picture someone on your team typing in a question your pipeline depends on. The assistant assembles a confident answer citing three sources, and it dawns on them that none of the three is you and that nobody had ever checked. This article exists to create that moment on purpose.
Most marketing teams can hand you a healthy list of buyer questions. Ask which of them AI assistants actually answer, with citations, in a way a vendor could show up in, and things get quiet. That gap separates a question bank from a target list, and closing it takes maybe three hours of genuinely fun work.
You don't have to take the buyer behavior on faith anymore. Casual threads asking "do you use ChatGPT before buying something" fill up with people describing exactly this consult-the-assistant habit, for everything from cars to software.
Do you use ChatGPT before buying something?
Started doing this a few months ago and I cannot believe how much time it saves me. Instead of spending two hours reading reviews that may or may not be fake, watching YouTube comparisons, and still feeling unsure, I just describe exactly w...
So the questions are being asked. To find the ones worth winning, you harvest and test, then filter and shortlist, and finally wire the shortlist into a weekly loop.
Step 1: harvest candidates, widely and fast
By the end of this step you want 80 to 150 candidate questions in a sheet, with verbatim phrasings kept and sources noted. It should take an hour, not a week, and nothing gets judged yet.
Go where buyer language actually lives. Start with your last twenty sales calls and demo requests, then the support tickets phrased as questions. The community threads where your category gets argued about deserve a pass, and so do the prompt-shaped strings in Search Console. Then run your five core buying queries through the assistants' own suggestion machinery and collect every related question they offer.
Don't clean the phrasing up, because the awkward wording is data. The seven-surface inference method covers this step in full. Inside the funnel, breadth beats rigor, since the next step does the judging.
Step 2: the answerability test
Most teams skip this step, which I find strange, because it's the one where you use the products your buyers use. Run each candidate logged out in two or three assistants: ChatGPT and Perplexity at minimum, plus Gemini or AI Mode if your buyers skew Google. Then sort what comes back into four buckets:
| Bucket | What comes back | What it means |
|---|---|---|
| Substantive with citations | A real answer citing real pages | Core target class: there's an answer, it has sources, and sources can be replaced |
| Product shortlist | A recommendation list of tools or vendors | Highest stakes: appearing here is close to appearing on the buyer's shortlist |
| Hedged non-answer | The assistant equivocates, generalizes, or answers a different question | Real demand plus a thin answer equals an open lane; the first genuinely good source frequently becomes the answer |
| Refused or deflected | Compliance-adjacent or too personal | Drop it; no content strategy fixes a refusal |
The hedged bucket is often the most interesting one. For each question, log the bucket and the cited domains, and note whether you or a competitor appears.
Three hours of this gives you a map nobody else in your category probably has. A keyword tool tells you what people search, while your sheet shows what the machines answering them actually do.
26 content formats. Published on your domain. Matched to your brand.
Guides, comparisons, listicles, case studies, and more. RankControl generates content that gets cited by ChatGPT, Perplexity, Claude, Gemini, Grok, and Google AI Mode.
Step 3: three filters
Three filters turn the tested list into a shortlist, and you apply them in order.
Buyer proximity comes first: would a real buyer plausibly ask this in the week they're choosing? Comparisons and alternatives pass. So do integration, pricing and migration questions, plus anything phrased around heavy constraints. Encyclopedic curiosity mostly doesn't, however satisfying it would be to win. When in doubt, check which questions your closed-won deals actually raised.
Winnability is where your step-two citations pay off, so read them like a competitive lineup. If an answer cites editorial pages, comparison articles, docs or honest reviews, you can win it by publishing better versions of those pages. If it cites only giant incumbents' brand pages, or only licensed news content, that's a longer campaign. Keep one or two as reach targets, but I wouldn't build a quarter on them.
The last filter, citation-shape match, asks whether you can realistically produce the kind of page being cited. If every citation is a hands-on benchmark and you can't run benchmarks, that question belongs to someone else this year. Think of it as sequencing: the same question often has an adjacent phrasing whose citations are pages you could build this month.
Step 4: shortlist to a tracked set
Score the survivors and cut to roughly 50, the number that keeps a weekly review readable. Balance the set on purpose. Comparisons and alternatives are the shortlist-formers, and integration and capability questions are the quiet compounders. Pricing and cost questions have revenue breath on them, and a handful of hedged-answer open lanes are your cheapest future wins.
Every query on the final list carries two annotations: the bucket it tested into, and the page, existing or planned, that's supposed to win it. The second one is where your list meets production. Unanswered queries become titled articles on the calendar, with titles that match the question's phrasing, and weakly answered ones become rewrites of the pages that should have won.
A worked pass: twelve candidates, one afternoon
To make it concrete, take a fictional client-portal SaaS and push twelve candidates through, following the real proportions these passes tend to produce. Suggestion machinery gives you "best client portal software," and the support tickets give you "how to share files with clients without email chains." A sales call supplies "[competitor] alternatives for small agencies," Reddit adds "is client portal software worth it," and eight more of varying specificity make up the dozen.
The answerability test sorts them fast:
| Candidate | What the engines did | Call |
|---|---|---|
| "best client portal software" | Product shortlist in every engine, citing two review sites and a listicle | High stakes; winnable via the third-party layer plus a comparison page |
| "how to share files with clients without email chains" | Substantive cited answer from two how-to guides, neither excellent | Winnable directly |
| "is client portal software worth it" | Hedged both-sides essay, one citation | Open lane, flagged |
| Two others | Refused or personal-finance-cautious | Dropped |
| Three near-duplicate phrasings | Collapsed into one cluster | Cleanest phrasing kept |
The filters then do their quiet work. A prestige question citing only enterprise analysts fails citation-shape and moves to the reach pile, and a delightful but idle curiosity question fails buyer proximity despite a beautiful open lane. Seven survivors join the tracked set, each annotated with its bucket and page. It all takes one afternoon, and those seven carry more strategic information than the original hundred-row keyword export ever did.
Step 5: wire it to the loop
The shortlist becomes your weekly per-engine tracking set, because a list nobody re-tests is a snapshot of a moving system. The weekly rows are step two on repeat: which engines answer, whom they cite, and whether your share is rising, per question, with dates.
Read them beside your publish log and the funnel closes. The harvest found the demand and the testing proved the venue. The filters picked your battles, and the tracker now grades every content decision against the exact question it was made for.
Your competitors are getting cited by AI. You're not.
Every day without citation tracking is a day your competitors pull ahead in ChatGPT, Perplexity, and Claude.
Keeping the list political-proof
Target lists attract opinions. The answerability data is your defense against the loudest voice in the room: if an executive's favorite topic fails the test, with refused answers, unwinnable citations or zero buyer proximity, the sheet says so with screenshots. The conversation then moves from taste to evidence in one meeting. It cuts the other way too, because the same sheet is what gets an open lane funded when nobody glamorous asked for it.
Keep the test artifacts next to the conclusions. Six months from now the screenshots are the institutional memory of why the list looks the way it does, and whoever defends it then may not be the person who built it.
The failure modes
This goes wrong in four ways in practice, all cheap to avoid.
Testing once and believing it is the classic. Answers churn between weeks, so a single test is a photograph of a coin flip. The weekly loop exists because the system you're measuring regenerates constantly, and only trends deserve belief.
Testing logged in is sneakier. Personalized answers reflect your history rather than your market's, so use logged-out, clean sessions every time, ideally with a second tester on another network for anything decision-critical.
Then there's chasing phrasings instead of intents. Forty variants of one question are one question. Test the cluster's best phrasing and track that, and let one deep page serve the whole cluster instead of sprawling into stubs.
The last is filtering by search volume. The constraint-heavy questions that decide B2B deals often show zero volume in keyword tools while people ask them, in full sentences, inside assistants every day. Volume can help you schedule, but it should never decide whether a question that passed the answerability test makes the list.
What the funnel buys you
The whole cost is three hours of testing and one sheet. Run honestly, the process swaps the oldest guess in content marketing, "what should we write about," for an evidence chain that runs from real buyer language and observed assistant behavior to competitive citation lineups and a weekly scoreboard. Your next quarter of content stops being a bet and becomes a schedule.
Teams that run it stop producing content that was never going to be retrieved, for questions nobody asked. They also start noticing the open lanes their category leaves unattended, and in a discipline this young, that's still most categories.
200+ SaaS teams already track their AI citations.
They know exactly when ChatGPT mentions their brand, and when it stops. Do you?
