See the exact searches ChatGPT runs, then target them
Ask an assistant one question and it does not go searching for your sentence. It breaks the request into several concrete queries in its own wording, runs those, and writes the answer from what comes back. Google names the same mechanism in its documentation: query fan-out.
Those intermediate queries are what your page is really matched against, and they are visible. Open the browser's network tab while the model works and the queries read as plain text inside the request and response payloads.
So you can stop guessing at what the assistant wanted and copy what it asked for instead. Expect the volume tools to report zeros against these phrasings: no human types them, so nothing records them.
What you get
The literal search queries ChatGPT issues behind an answer in your niche — a keyword list no tool exports — and pages aimed at them.
Steps
- Open chatgpt.com in a desktop browser and open developer tools (F12), Network tab.
- Ask a buying-intent question from your niche with web search enabled.
- Read the request and response payloads that appear: your one prompt fans out into several concrete search queries, readable in the traffic. Copy each query out. Endpoint names change; the queries stay readable.
- Repeat for your three to five money prompts and collect every fan-out query into one list.
- Deduplicate the list. What you are holding is how assistants actually search, in their words rather than your buyers'.
- Check volumes if you like, but expect zeros: these are machine-phrased queries that volume tools barely record.
- For each fan-out query you can honestly serve, publish or retitle a page that answers it head-on: the phrase in the title, the answer in the first sentence.
- Re-ask the original prompts in two to four weeks and check whether your pages entered the citations.
How to verify it worked
- Your page appears among the citations when the original prompt is re-asked in a fresh session.
- Search Console shows impressions for unusually long query strings; filter with the regex .{75,} to surface them.
Why it works
You are aiming at the query the machine wrote, not the one the user typed. Everyone else is optimizing for the visible question, and the visible question is not the string that retrieval ran on.
Evidence
Practitioner report, 2026-08: the capture method — browser developer tools' network tab open while prompting, fan-out queries copied from the payloads.
Google's AI-features documentation (reviewed 2026-09-01) states that AI Overviews and AI Mode use "query fan-out" — the same mechanism, named by the vendor.
Last reviewed: 2026-09-01. A play whose evidence stops holding up is rewritten or retired.
SEO Plays