Troubleshooting
Why ChatGPT recommends your competitor instead of you
Investigate why a competitor appears in ChatGPT answers. Check the questions, sources, crawler access and content gaps, then choose evidence-led improvements.
Seeing a competitor recommended in ChatGPT can feel like a verdict on your business. Treat it first as a finding to investigate. You have observed one answer to one question under particular conditions. The next step is to work out whether the pattern repeats and which public information could help explain it.
No outside observer can reconstruct every reason a system selected an option from a single response. You can still make useful progress by checking the question, the answer’s sources, your website and the accuracy of the comparison. This guide gives you a practical order for that investigation.
Start with the exact customer question
Save the prompt before doing anything else. Identify the customer type, product category and constraints it contains. A question about low-cost tools for freelancers may reasonably surface different options from a question about enterprise procurement. Decide whether the question describes a customer you actually serve.
Check whether the wording already supplies the competitor’s name or an attribute closely associated with its offer. If it does, classify the response as a branded or constrained comparison. Do not treat it as an unprompted discovery result.
Then write a small set of related questions using language from genuine enquiries. Keep each one independent and avoid adding your brand just to persuade the answer to mention it. The goal is to understand a buying situation. If the competitor consistently fits that situation better, the useful decision may concern positioning or product scope rather than a website fix.
Confirm that there is a pattern
Repeat the agreed questions in separate conversations and retain the full responses. Record the interface, date, language, visible model, relevant personalisation settings and whether search was observed. A fresh conversation may still have account-level context, so write down the settings you can see and mark unknowns.
If you want a search-based comparison, ask for current sources and inspect the resulting search activity. OpenAI’s search documentation explains how search results and citations appear when that tool is used. An answer with no observed search should be labelled accordingly.
Define the comparison before scoring it: mentioned, recommended, own website cited and factual accuracy. Keep failed attempts in the log and report the denominator. “The competitor was recommended in eight of twenty completed answers” is a reviewable observation. “ChatGPT always prefers them” is a much stronger claim that the sample does not support.
Inspect what the cited pages say
Open the sources linked in the relevant answers. Note which pages support the competitor’s inclusion and what information they contain. Useful distinctions include a vendor’s own documentation, a directory entry, an independent review and a publisher’s comparison.
Check the relationship between each claim and its citation. Does the source support the stated feature or price? Is it current enough for the question? Does it refer to the same company? A citation can be a useful investigation lead without being adequate proof of the statement beside it.
Record visible differences without pretending they reveal the platform’s full decision process. If a competitor’s page clearly explains an integration that your own site barely mentions, that is an information gap worth reviewing. It is not proof that the integration paragraph alone caused the recommendation. Keep observations and possible explanations in separate columns.
Rule out a basic access problem
Ask your developer to check the public URLs most relevant to the question. Confirm that they return the intended content, have consistent canonical URLs and are not accidentally restricted. Review broken internal links, login requirements and hosting rules that could prevent retrieval.
For ChatGPT search, OpenAI’s crawler guidance identifies OAI-SearchBot as the relevant search control and recommends allowing its published IP ranges. Training controls for GPTBot are separate. Correct the specific access issue you have identified rather than changing every bot rule without understanding it.
An accessible page is a foundation for discovery, not a promise of inclusion. Verify the deployed page after a change and keep the date in your log. A successful local test says the code works in that environment; it does not establish that the production firewall, redirect or indexing directive has also changed.
Check whether your offer is easy to verify
Read your relevant page without relying on knowledge you have as the owner. Does it explain the service, the intended customer, supported features and any important exclusions? Can someone verify your claims through documentation, a product demonstration or a clearly attributed example?
Replace vague claims with accurate detail. “Built for busy teams” says little about whether the product supports recurring appointments. A short explanation of how recurring bookings work, which plans include them and where the limitations sit gives a buyer more useful information.
Zenith Cite’s own audit page, for example, publishes a €750 one-time price including taxes. That gives a reviewer a specific fact to check in a branded answer. The founder profile supplies an identity and contact route. These are verifiable website facts; they are not evidence of a recommendation advantage over another agency.
Review information beyond your website
Make a list of the external pages actually observed in your answer sample. Check for old business names, outdated prices, incorrect categories or descriptions that omit an important service. Prioritise corrections where you can document an error and identify the page owner.
If an independent article accurately describes a competitor’s strength, use it to understand the buyer’s comparison criteria. Do not assume you are entitled to inclusion or that a paid listing will change an AI answer. Any outreach should offer verifiable information relevant to that publisher’s audience.
Focus first on profiles and listings your business already controls. Keep the business name, website and factual description consistent. Where you cannot change an external page, record the limitation and make your own current information clear. Avoid inventing reviews, customer quotations or results to imitate the appearance of stronger evidence.
Turn a comparison into a testable task
Illustrative scenario: a fictional cleaning-business booking tool is absent from several comparison answers. A competitor appears with a citation to a guide about recurring appointments. Your product supports that feature, but its public page does not describe it. This is an invented example of the investigation method, not a customer result.
The immediate task is to verify the feature with the product owner, write accurate documentation, link it from the relevant page and check that the public version is accessible. The reason for doing this is clear: potential customers currently cannot verify an important capability.
After publication, repeat the original questions and record any changes. Keep exploratory follow-ups separate. If the company appears more often, report that observation alongside the small sample and other changes during the period. If it remains absent, the documentation can still help buyers, while the recommendation hypothesis remains unconfirmed.
Choose the next step by evidence strength
Use three priority groups. First, fix confirmed errors such as an inaccessible service page or an incorrect public price. Second, improve information that clearly matters to the buying question. Third, investigate less certain opportunities, such as whether an additional comparison guide would help the intended audience.
Give each task an owner, an affected URL and a completion criterion. Record the evidence that justified it so the next review can assess the decision. Avoid making a dozen simultaneous changes just to obtain a better screenshot; that makes later interpretation difficult and can consume a small team’s whole content budget.
If you want a broader comparison, read how GEO and SEO measurements fit together. Our GEO services follow the same practical sequence: establish the starting point, agree useful work and review the evidence afterwards. You cannot control every recommendation, but you can make the information behind your business more accurate and useful.
Start with your business.
Bring your website and the customer questions that matter to you. A free AI visibility snapshot is a practical starting point for discussing your current presence and useful next steps.
Book your free snapshot ↗