You ask ChatGPT to recommend software in your category.
It names three competitors. Your product is missing.
You try again with slightly different wording. The list changes, but your company still does not appear.
That is worth investigating. It is not enough evidence to conclude that your product has a reputation problem, your SEO has failed, or a competitor has discovered a secret optimization trick.
The useful next step is to turn that missing mention into a set of questions you can actually check:
- Was the answer based on a web search?
- What exactly did the buyer's question ask for?
- Could the relevant search crawler access your public pages?
- Which sources supported the competitor's appearance?
- Does your website clearly explain why your product fits that need?
This guide walks through those checks. It does not claim to reveal ChatGPT's private recommendation formula.
The short answer
A competitor appearing in a ChatGPT answer does not reveal the full reason they were selected.
OpenAI says ChatGPT search ranks results using multiple factors intended to surface relevant, reliable information. It also says placement is not guaranteed.
The practical response is to check discovery, fit, evidence and consistency—not to assume that one missing mention proves a single underlying problem.
Start by saving the answer. Then investigate the specific question and the sources available to support it.
First, check whether you are looking at a search answer
Before investigating why a competitor appeared, establish what kind of answer you received.
Did ChatGPT visibly search the web? Did the response include linked sources? Which mode or interface did you use?
A response with visible web citations gives you sources to inspect. A response without visible citations does not provide the same evidence trail.
Do not assume every answer is a fresh crawl of your website.
OpenAI explains that ChatGPT search may rewrite a user's request into one or more targeted queries and send them to search providers. That means the wording of the question and the context surrounding it are important things to record.
Save:
- The exact prompt
- The date
- The visible mode
- Whether it was a new conversation
- Relevant language or location context
- The full response
- Every visible citation
Without that record, a later comparison becomes guesswork.
Check 1: Does the question actually describe your customer?
Consider these two requests:
“Recommend project management software.”
“Recommend project management software for a five-person design agency that needs client approvals and does not want a complex setup.”
Those are different buying situations.
A product can be suitable for one and unsuitable for the other. Before calling the omission a visibility failure, check whether your product genuinely fits the stated requirements.
Use a simple table.
| Requirement in the prompt | Does our product meet it? | Public evidence |
|---|---|---|
| Suitable for a small team | Yes / No / Unclear | Relevant plan or product page |
| Client approval workflow | Yes / No / Unclear | Documentation or feature page |
| Easy setup | Supported / Unsupported claim | Setup guide or worked example |
| Within the stated budget | Yes / No / Unclear | Current pricing page |
If a requirement is missing from your product, better content will not make that feature exist.
If the feature exists but is poorly explained, you have a useful content improvement to make.
This distinction prevents a common mistake: treating every competitor mention as a problem that marketing must somehow reverse.
Check 2: Can ChatGPT search access the relevant pages?
Start with eligibility before debating writing style.
OpenAI says that allowing OAI-SearchBot helps make content available for discovery, summaries and snippets in ChatGPT search.
Its guidance also recommends checking that the website host or content delivery network permits requests from OpenAI's published searchbot IP addresses.
Ask your developer to review:
- Whether relevant public pages are accessible
- Applicable
robots.txtrules - CDN and firewall behavior
- Bot challenges or login requirements
- Server errors affecting important pages
Allowing access is not a guarantee that your page will be selected. It removes one possible obstacle.
Search access and training preferences are different
Do not treat every OpenAI crawler as the same service.
OpenAI's publisher guidance distinguishes OAI-SearchBot, associated with search discovery, from GPTBot, which publishers can disallow to exclude content from potential training.
If you want to review those settings, use the current official documentation and have the person responsible for your infrastructure check the complete configuration.
Do not copy a generic robots.txt file over an existing production file. You could accidentally change access for unrelated pages or crawlers.
Check 3: Inspect the sources behind the competitor's appearance
When a response includes citations, open them.
Do not stop at the brand names in the answer. Check what the linked pages actually say.
For each source, ask:
- Is it the competitor's own website or a third-party page?
- Does it support the specific statement in the answer?
- Is the information current?
- Does it discuss the same customer type or use case?
- Does it contain original evidence or repeat another page?
- Does your own website provide an equally clear answer?
Use this worksheet:
| Cited source | Source type | Claim it supports | Information gap to investigate |
|---|---|---|---|
| Competitor feature page | Owned product page | Supports a requested workflow | Our workflow explanation is unclear |
| Comparison article | Third-party editorial | Lists tools for the buyer's use case | We have not explained that use case |
| Product documentation | Owned documentation | Confirms an integration | Our integration details are difficult to find |
These are hypothetical examples, not findings from a ZocoPilot study.
The exercise gives you a list of checkable gaps. It does not prove that copying a competitor's page or gaining a mention on one website will change the next answer.
A citation tells you which source is presented as support. It is not a complete explanation of the system's selection process.
Check 4: Does your website explain the product clearly enough?
Read your main product page as if you know nothing about the company.
Can you answer these questions without opening five other tabs?
- What kind of product is this?
- Who is it intended for?
- Which tasks does it support?
- Which important limitations apply?
- What does it cost, or how can a buyer understand the pricing?
- Where can a buyer verify the details?
Compare these two descriptions.
Vague
“Our platform transforms collaboration with an intelligent workspace built for modern teams.”
Specific
“Our project management software helps small agencies assign work, collect client approvals and keep project discussions beside each task.”
The second description gives a reader more information to evaluate.
That does not establish a ranking rule. It is a practical standard for useful product communication.
Google's people-first content guidance similarly asks whether content helps its intended audience achieve their goal and provides clear, trustworthy information.
Clarify limitations as well as strengths
If an integration works only on a certain plan, say so.
If a workflow needs manual setup, explain it.
If your product is designed for small teams rather than a regulated enterprise deployment, do not hide that distinction behind broad copy.
The aim is accurate representation, not appearing in every possible recommendation.
Check 5: Are important product facts consistent?
A buyer might encounter your pricing page, documentation, marketplace listing and an old launch announcement during the same research session.
Check whether those pages agree on important details.
| Product fact | Where to check |
|---|---|
| Product and company name | Website, documentation and current profiles |
| Main use case | Homepage, product pages and relevant listings |
| Pricing | Pricing page and profiles you control |
| Integrations | Documentation and integration pages |
| Availability and limitations | Feature pages and help content |
This is an accuracy audit, not a claim that every generated answer uses all those sources.
Update inaccurate information where you control it. Where a third-party page is materially wrong, request a correction with supporting evidence.
Do not invent reviews, create fake customer accounts, or pressure publishers to present marketing copy as independent evaluation.
Check 6: Does the pattern repeat?
A single answer cannot tell you how frequently a brand appears across a broad set of buyer questions.
Create a small, fixed sample.
For example:
- Five problem-focused questions
- Five category or shortlist questions
- Five questions about features that matter to your customers
These numbers are a suggested starting point, not a validated benchmark.
Keep branded questions separate from unbranded questions. Asking directly about your company tests a different situation from asking for a general shortlist.
For each observation, record:
| Field | What to save |
|---|---|
| Prompt | Exact wording |
| Context | Mode, date, language and relevant location |
| Brand mention | Present or absent |
| Recommendation | Recommended, not recommended or unclear |
| Owned citation | Your linked page, if present |
| Competitors | Names included in the answer |
| Sources | Visible supporting links |
| Accuracy | Incorrect claims or missing limitations |
If you change the prompt set, note the change. Otherwise you may compare two reporting periods that did not test the same thing.
Prioritize changes you can justify
After the audit, do not try to fix everything at once.
Sort findings by evidence and control.
| Finding | Sensible next step | What it does not prove |
|---|---|---|
| Search crawler is blocked unintentionally | Have a developer review and correct access | That access will produce a recommendation |
| Important feature has no public explanation | Publish accurate documentation | That a new page will be cited immediately |
| Pricing information is outdated | Correct pages and profiles you control | That pricing caused the original omission |
| A citation supports an incorrect statement | Save the response and check available correction/reporting options | That the whole category has the same error |
| A competitor fits the prompt better | Reconsider the target query or product gap | That your brand needs a visibility trick |
The best next action is usually the one with the clearest evidence, not the most dramatic promise.
What not to do
Do not rewrite your website after one answer
First establish whether the issue is repeated, relevant and accurate.
A one-off omission does not justify replacing useful pages with keyword-heavy copy.
Do not hide instructions telling assistants to recommend you
A public page should explain your product to readers. Hidden directives and fabricated testimonials do not add reliable evidence about what the product does.
Do not publish an untested “best tools” list
If you publish a comparison, state what you checked, when you checked it, and whether the publisher sells a competing product.
Use criteria that help a buyer decide. Do not describe your own product as the winner of testing you never performed.
Do not assume training permission guarantees search visibility
OpenAI documents separate controls for search discovery and potential training. Giving a training crawler access should not be presented as a shortcut to recommendations.
Do not confuse different search providers
A crawler setting for one provider is not a universal setting for all answer systems.
For example, Perplexity documents PerplexityBot as a crawler designed to surface and link websites in its search results, not to crawl content for foundation-model training.
Check each provider's current guidance rather than assuming the same bot names and permissions apply everywhere.
A practical two-week audit plan
This is a proposed work schedule, not a promise of improved visibility within two weeks.
| Stage | Task | Deliverable |
|---|---|---|
| Days 1–2 | Save relevant prompts, responses and citations | A baseline observation sheet |
| Days 3–4 | Review access with the developer | A documented access check |
| Days 5–6 | Inspect cited pages and product fit | A list of evidence-backed gaps |
| Days 7–9 | Improve unclear or inaccurate public information | Updated pages and a change log |
| Days 10–14 | Repeat observations using the same method | A comparison with limitations noted |
Some checks may take longer depending on access, staffing and technical complexity.
If results change after an edit, report the sequence accurately. The timing alone does not establish causation.
How to tell whether the work helped
Look for improvements at three levels.
1. Information quality
Are public product facts clearer and more accurate?
Can a prospective customer verify important features and restrictions?
These are useful improvements even before you observe a different answer.
2. Sampled answer visibility
Across your defined prompt sample:
- Is the brand mentioned more often?
- Are the descriptions accurate?
- Are relevant owned pages cited?
- Is the product recommended for suitable use cases?
Report the sample size, prompts, collection method and limitations.
Do not label a small sample “total AI market share.”
3. Customer outcomes
Where identifiable, review referral visits and meaningful actions such as trial starts or demo requests.
OpenAI says ChatGPT referral URLs automatically include utm_source=chatgpt.com, which can help publishers identify inbound traffic in analytics.
A recorded visit is not automatically a qualified lead. Keep visibility, traffic and conversion reporting separate.
Frequently asked questions
Can I pay OpenAI to guarantee an organic recommendation?
The cited OpenAI search documentation provides no method for guaranteeing an organic recommendation. It explicitly says placement is not guaranteed.
Treat third-party promises of guaranteed organic placement cautiously.
Does blocking GPTBot also mean blocking OAI-SearchBot?
They are separate user agents with different documented purposes.
Review your actual robots.txt and infrastructure settings rather than assuming one rule determines both.
Will publishing more articles make ChatGPT recommend my company?
Not necessarily.
Publishing volume alone does not establish usefulness or eligibility. Start with information that is missing, inaccurate or insufficient for the customer's decision.
Should I ask ChatGPT why it omitted my company?
You can ask for clarification, but do not treat the resulting explanation as an audit log or proof of hidden ranking factors.
Use accessible sources, recorded responses and your own page checks to investigate specific claims.
How quickly will changes affect recommendations?
There is no responsible universal timeline.
Crawler access, discovery and answer selection are different steps. Correcting a problem does not guarantee a recommendation.
Start with the missing evidence
When a competitor appears and you do not, resist the urge to look for a secret prompt or a magic file.
Save the answer. Check whether the question fits your product. Inspect the cited sources. Verify search access. Improve the information buyers cannot currently find or confirm.
Then repeat the same checks.
That gives your team something more useful than a theory about “what the algorithm wants”: a documented problem, a justified change and a way to observe what happens next.
A practical guide for B2B SaaS teams comparing SEO and GEO, with measurement definitions, a tracking worksheet, and a four-week action plan.
Explore ZocoPilot's available features and decide whether they fit the way your team wants to investigate and report search visibility.
Explore ZocoPilot
