Key takeaways
- In ChatGPT's chat answers, software recommendations come from a citation pool led by GitHub (1.2% of software citations), learn.microsoft.com (0.98%) and G2 (0.73%), per Promptwatch Data for Sep 28 to Oct 4, 2026.
- Coding agents work differently. They read files, run commands and search the web, so what they recommend depends on your repo, your docs and what they can fetch, not only on what a chat model remembers.
- Documentation and GitHub presence are the strongest overlap. Both surfaces reward clear, crawlable docs and a live repo.
- Review sites like G2 and Capterra matter for chat answers, and probably much less for agents mid-task. That second part is my inference, not measured data.
- Nobody has published solid data on coding-agent tool choice yet. Treat any claim that you can "rank first in Claude Code" with suspicion.
The short answer
Partly. The same tools win when both surfaces lean on documentation and public code. They diverge when a user asks a buying question in chat versus when an agent is halfway through building something and needs a library, an API or an SDK.
I should be upfront about the evidence. We have good first-party data on what ChatGPT cites for software prompts. We do not have a comparable dataset for what coding agents like Claude Code, Codex or Cursor pick. So this guide separates what is measured from what is reasoned.
What is the difference between prompting and an agent
A chat prompt produces text. You paste code in, you get code out, and you carry it back to your editor yourself. An agent uses tools. It reads files, runs commands, searches the web and calls APIs, then loops on its own results. A Medium explainer from February 2026 frames it exactly that way: prompting can only generate text, while an agent uses tools.

The Neuron's podcast on the topic suggests a sensible ladder: start with a simple prompt, move to structured prompts, then projects, and only reach for a full agent when the simpler options fail. Their episode dates from August 2025 and the hosts themselves note that model choice advice is partly outdated after GPT-5, so use the framework rather than the specifics.

That distinction matters for tool visibility. A chat user asking "what is the best CRM for a small team" gets an answer built from retrieved web pages. An agent asked to "add payments to this app" mostly reads your package manifest, your existing code and whatever docs it fetches.
What ChatGPT cites for software prompts
Promptwatch Data looked at organic software prompts in ChatGPT from Sep 28 to Oct 4, 2026. The most cited domains, as a share of all software citations, were:
| Domain | Share of software citations |
|---|---|
| GitHub | 1.2% |
| learn.microsoft.com | 0.98% |
| G2 | 0.73% |
| AWS docs | 0.41% |
| Google Cloud docs | 0.35% |
| Gartner | 0.34% |
| Capterra | 0.32% |
| Intercom | 0.28% |
| Zapier | 0.24% |
The full list is in Promptwatch's software citation report. A few things stand out to me.
First, the shares are small. The top 23 domains together earn only 7.89% of software citations. This is a long-tail market, and no single site owns it.
Second, docs and help centers are the biggest source type at 2.64%, followed by vendor sites at 2.01%. Review sites and analysts (G2, Gartner, Capterra, Software Advice combined) earn 1.57%. Promptwatch's own read is that vendor pages and docs together earn about three times as much as review sites.
Third, by company, Microsoft earns 1.35% across three domains, Google 0.98% across four, AWS 0.69% across two and OpenAI 0.42% across two. Platform owners cite themselves, in effect, because their docs are what developers search for.
Which content types win
Across all classified ChatGPT citations in the same week, product pages led at 22.4%, then landing pages at 16.8%, listicles at 13.6%, how-to guides at 8.7% and documentation at 7.5%.
The mix shifts with intent:
| Prompt type | Top formats |
|---|---|
| Commercial ("best CRM") | Product pages 26.0%, landing pages 20.6%, listicles 15.0%, comparisons 7.9% |
| Informational | Product pages 19.1%, landing pages 13.9%, listicles 13.6%, how-tos 10.7%, docs 8.5% |
| Branded | Product pages 23.3%, landing pages 22.8%, reviews 5.6% |
So in chat, a buyer comparing software mostly sees vendor pages and listicles. A developer asking a how-to question sees more docs and tutorials.
How coding agents pick tools
Here the honest answer is: we do not have the data. I found no published, verified dataset of which tools Claude Code, Codex, Cursor or similar agents choose. Claims floating around, like "Claude Code leads on complex coding" or "Codex is cheaper and faster for lean builds", come from opinion pieces and I could not verify them, so I will not repeat them as fact.
What we can reason from is how agents work.
- They start from context. The repo, the lockfile and existing imports strongly shape what gets suggested. If a project already uses Stripe, the agent will most likely keep using Stripe.
- They fetch docs when they need to. Clear, crawlable documentation gets read. Docs hidden behind JavaScript walls or login screens do not.
- They lean on training data for defaults. When there is no context, the model's memory of what was popular decides. That favors tools with years of public code and tutorials.
- They follow instructions. Rules files, README guidance and explicit prompts override everything else.
This is reasoning, not measurement. But it points to a real split: chat answers are shaped by the open web at query time, while agent choices are shaped by the project in front of them plus training data.
Where the winners overlap
Documentation
Docs rank high in ChatGPT citations, and agents read docs directly when they get stuck. Good docs are the one asset that helps on both surfaces. Plain HTML, stable URLs, copy-pasteable examples and a clear quickstart are worth more than another landing page.
GitHub
GitHub is the top cited domain in ChatGPT software answers. It is also where agents find code, issues and examples. A maintained public repo with a decent README is a rare signal that feeds both surfaces.
Platform vendors
Microsoft, Google, AWS and OpenAI all earn citations in chat, and developers building on those platforms will see their SDKs recommended by agents too. If you build on a big platform, expect the platform's own docs to outrank your tutorials.
Where they split
| Factor | ChatGPT chat answers | Coding agents |
|---|---|---|
| Primary input | Retrieved web pages at query time | Your repo, fetched docs, model memory |
| Role of review sites | Real but small (1.57% of software citations) | Likely minor mid-task (inference) |
| Role of product pages | Highest cited type (22.4%) | Low, unless the agent browses to evaluate options |
| Role of docs and GitHub | Strong | Strong, often decisive |
| Switching cost | None, the user decides | Existing project dependencies create lock-in |
| Measurement | Citation tracking is possible | Little public data |
The lock-in point is the one I find most interesting. In chat, every answer is a fresh vote. In an agent session, the first dependency choice tends to stick for the rest of the project. Winning at the moment of the first choice is worth more.
Why chat versus agent also matters to users
A Reddit thread in r/vibecoding asks why anyone pays for a coding agent when they could prompt in chat and paste code. The poster describes a workflow of describing the project in chat and pasting results. It works, until the project grows and the copy-paste loop becomes the bottleneck.
G2's comparison of GitHub Copilot and ChatGPT lands in a similar place: ChatGPT is better for explaining code, debugging errors and generating logic or scripts from scratch, while Copilot works best inside the editor. That is a useful rule of thumb. Chat for thinking, agents for doing.
One more caution from a Medium writeup comparing ChatGPT and Claude on identical prompts: both tools will confidently produce code that looks correct and sometimes is not. Whichever surface you use, run the tests.
What software vendors should do
If you sell a developer tool or an API, treat chat and agents as two channels with one shared foundation.
- Fix your docs first. Make them server-rendered, fast and example-heavy. Docs and help centers are the biggest source type in ChatGPT software citations.
- Keep a live GitHub presence. Public repos, sample apps and a clear README help both surfaces.
- Keep review profiles current. G2 and Capterra still earn citations in chat, even if they are a smaller slice.
- Publish comparison and how-to content. Commercial prompts show listicles and comparisons at over 22% combined.
- Check what crawlers can read. If AI bots are blocked or hitting errors, none of the above matters. The AI crawler data from Promptwatch shows how much verified bot traffic now exists across OpenAI, Anthropic, Google, Perplexity and Mistral.
- Add agent-friendly guidance. An llms.txt file and clear setup instructions cost little. One caution: Promptwatch Data found markdown files make up just 0.05% of AI search citations, so markdown serves agents, not AI search. Do not expect it to move chat visibility.
Keep in mind that citation patterns shift quickly. News pages lose half their citations in about five weeks, while landing pages and docs hold on for months, according to Promptwatch's content half-life report. Durable pages beat reactive ones.
Tools to measure both surfaces
For the chat side, you can measure real citations. Promptwatch tracks how ChatGPT, Gemini, Perplexity, Google AI Overviews and others mention and cite your brand, and it also tracks how the coding agents Codex, Claude Code and OpenCode recommend tools, SDKs and docs, which is the closest thing to coverage of the agent side. Its AI crawler logs show whether bots actually read your docs.

Other trackers worth a look if you want a second opinion:

To browse more options, the GEO software directory at bestgeosoftware.com lists many of them.
If you want to see how these assistants themselves behave, try asking the same software question in each:
A simple test you can run today
- Write ten prompts a developer might ask about your category, such as "best SDK for X in Python".
- Run them in ChatGPT and note which domains get cited.
- Open a blank project in a coding agent and ask it to build something that needs your category. Note which tool it picks without any hints.
- Compare. If chat cites you and the agent ignores you, your docs or repo are the likely gap. If neither does, start with crawlability.
This is crude, and one run proves little. Repeat it weekly and watch the trend.
So, do the same tools win?
Often, but not for the same reasons. In chat, vendor pages, docs, GitHub and a few review sites split a thin slice of citations. In agents, the project context and the docs the agent can fetch decide, with training-data popularity as the fallback. The shared lever is documentation plus a healthy public repo.
The unknown is agent tool choice at scale. Until someone publishes that data, the defensible move is to make your docs easy to read and your repo easy to trust, then measure what you can.



