How to Get Cited by ChatGPT and Perplexity
Improve your chances of AI citations with verified crawler access, strong source material, a repeatable tracking record, and clear diagnosis steps.
To improve your chances of being cited by ChatGPT or Perplexity, give the system an accessible, relevant page with information worth using. Then check whether the resulting answer links to the right URL and preserves the facts that matter.
There is no publishing checklist that guarantees a citation. Search access is necessary for some discovery paths, but it does not make a page the best source for a particular answer. A cleanly formatted article can still be generic, inaccurate, or unrelated to the reader's decision.
For founders, marketing teams, and agencies, the most reliable process has four parts: verify access, improve the source material, test a defined question set, and investigate the results. This guide provides a crawler comparison, a documentation example, and a copyable tracking record.

A conceptual workflow for improving and monitoring citation opportunities. This diagram does not describe a proprietary ranking algorithm.
First, define what you want to appear
“We want AI visibility” is too broad to brief a writer or diagnose a problem. Choose the outcome:
- Your guide is linked as support for a named explanation.
- Your product is described accurately in a relevant comparison.
- Your business is included in a local or industry recommendation.
- Someone follows a source link and reaches a relevant destination.
Each outcome calls for different proof. A pricing comparison needs current, public offer details. A technical explanation needs an accurate procedure or reference. A local recommendation needs verifiable location, availability, and service information.
Write the customer question in their language. Include the conditions that change the answer: business size, use case, location, budget constraints, or an existing system. A vague question produces a vague test.
Keep brand mentions, source citations, factual accuracy, and referral visits as separate fields. You can be mentioned without a link, linked without being recommended, or recommended with an incorrect description.
Verify the right crawler, not every AI agent
OpenAI and Perplexity document different agents for different purposes. Allowing a training crawler is not the same decision as allowing a search crawler.
| Agent | Documented purpose | Check to run |
|---|---|---|
| OAI-SearchBot | OpenAI search discovery | Check robots rules and verified network access if you want search inclusion |
| GPTBot | OpenAI model training | Make a separate training policy decision |
| ChatGPT-User | Visits triggered by user actions | Do not treat it as the automatic search crawler |
| PerplexityBot | Perplexity search discovery | Check robots rules and the vendor's published IP ranges |
| Perplexity-User | User-requested page access | Review this separately from automatic crawling |
The roles above come from OpenAI's crawler documentation and Perplexity's crawler documentation, checked October 8, 2026. User-triggered fetch behavior differs from ordinary crawling; consult the current documentation before making policy changes.

The page distinguishes OAI-SearchBot from other agents; it does not promise citations for accessible pages. Source: OpenAI.

Search crawling and user-requested access are different roles. Source: Perplexity.
Ask your technical owner for a short access record:
- The exact URL being checked.
- Its response status and whether the important content is available.
- The relevant robots rule and any authentication requirement.
- Verified crawler requests in server or firewall logs, where available.
- The applicable firewall decision and the date of inspection.
Perplexity's documentation recommends combining user-agent matching with IP verification for firewall rules. A user-agent string alone is not proof that a request belongs to the vendor. Do not broadly disable protection because a page has not earned citations.
A bot visit demonstrates access, not selection. If the page can be reached, move on to the information it supplies.
Give the answer a verifiable source worth citing
An article should resolve something the reader needs to know. Generic claims such as “automation saves time” do not explain the task, conditions, or tradeoffs. A documented feature limitation or a worked comparison can be much more helpful.
Consider the WordPress REST API posts reference. It names fields and allowed values. Its status field distinguishes publish, future, draft, pending, and private. That level of detail helps a reader answer a concrete publishing question.

This is documented behavior, not an API operation we executed. Source: WordPress.org.
An original explanation based on that reference could say:
A WordPress publishing workflow needs an explicit post status. Creating a draft and publishing a post are different outcomes, so verify the stored status and the public URL separately.
The first sentence describes the documented model; the second is our recommended acceptance check. The paragraph does not claim that a particular integration was tested or that the page has been cited by an AI engine.
Use that distinction in your own articles. Separate what the documentation says, what you observed, and what you recommend. If you did test a product, record the version, task, setup, and outcome before calling the section a test.
Build complete answer sections
A section can be concise without being incomplete. Use four elements when the reader needs a decision or procedure:
Answer: State the conclusion in ordinary language.
Proof: Attach the source, demonstration, or calculation that supports it.
Conditions: Explain what would change the answer.
Next step: Show what the reader should verify or do.

An original editorial framework. Apply it where the reader needs an explanation or action; do not turn every paragraph into the same template.
For a comparison page, include the same criteria for every option. For an implementation guide, show the expected state after each important step. For a benchmark, explain the sample and the measurement. For an offer, keep material limits beside the benefit.
Good screenshots should demonstrate the point being discussed. A documentation screenshot can support a statement about available fields. It cannot support a statement that your team successfully published through the API. A generated dashboard cannot stand in for account data.
Give important image content a text equivalent. Readers should not have to enlarge a screenshot to learn the essential step, and key facts should not exist only inside an infographic.
Keep your public facts consistent
An answer can draw information from more than your blog. Review the pages that establish your identity and offer: product or service pages, pricing, locations, support documentation, company details, and relevant third-party references.
Use a simple correction list:
| Fact | Primary public source | Other places to check | Owner |
|---|---|---|---|
| Product or service name | Your current offer page | Documentation and profiles | Marketing |
| Availability | Location or service page | Relevant listings | Operations |
| Price and conditions | Current pricing or quote policy | Old comparison articles | Commercial owner |
| Capability | Current product documentation | Help articles and sales pages | Product owner |
| Proof of results | Approved case record | Summaries and promotional assets | Case owner |
This is a maintenance workflow, not a claim that consistency is a known citation ranking factor with a measurable weight. It reduces contradictions and helps people verify what you offer.
Earn outside coverage through relevant expertise, research, partnerships, or relevant participation. Do not invent reviews, manufacture customer results, or seed communities with promotional answers solely to influence an AI response.
Run a repeatable citation check
Choose a small set of questions that represent customer decisions. Include informational, comparison, and brand-specific questions if each is relevant. Use the same questions over time rather than changing them until your brand appears.
For every observation, save the exact question, date, platform, visible mode, any relevant conversation context, and the answer's source links. Record an absence as an absence. If web search was unavailable or no sources were shown, preserve that distinction.
Question ID and customer task:
Exact question:
Platform, visible mode, and date:
Conversation context or clean session:
Web sources shown: yes / no / unclear
Brand mentioned: yes / no
Our URL cited, if any:
Other cited URLs:
Important facts correct: yes / no / unclear
Error and supporting primary source:
Observable referral or business event:
Follow-up action and owner:Repeat selected checks to see whether an observation persists. Compare like-for-like sessions as far as the product permits. Label the results as your sampled observations; they are not a measurement of every user conversation.
If you buy a tracking tool, ask about its question library, coverage, location and language settings, response collection method, and definitions. A tool that counts brand mentions and one that counts linked domains may tell different stories while both work as designed.

Measure each stage separately. A citation count alone does not establish referral traffic, lead quality, or revenue.
Review observable AI referrals in your web analytics and connect visits to defined business events where your measurement setup allows. Some journeys lose attribution or include later visits, so report what you can observe instead of labeling every unattributed conversion as AI-influenced.
Diagnose the result before choosing the fix
| Observation | Investigation | Response |
|---|---|---|
| No citation and confirmed access failure | Which rule, response, or restriction prevents access? | Resolve the technical problem |
| Accessible page, but other sources answer the question better | What decision information do those pages provide? | Add a supported explanation or demonstration |
| Your brand is mentioned with the wrong details | Which current primary page resolves the error? | Correct outdated public information and retest |
| Your page is cited but receives few attributable visits | Does the answer already satisfy the task? Is the destination helpful? | Review the role of the page and the next step |
| Visits increase but inquiries are poor | Are the question and offer aligned? | Refine targeting and the destination |
Avoid the leap from “not cited” to “blocked.” Equally, avoid the leap from “cited” to “successful campaign.” Both diagnoses need more data.
Use AI to audit claims, if it helps
This prompt helps organize a review. It does not verify facts on its own. Supply the draft and sources you have checked, then review the output against those sources.
Review this draft for the stated reader task.
Use only the attached source extracts as the factual basis.
For each important claim, return:
claim / supporting extract / missing condition / recommended edit.
Mark unsupported claims as unverified.
Flag invented experience, results, or product testing.
Identify questions the reader still cannot answer.
Do not add statistics, quotes, citations, or capabilities.
Draft and verified extracts:Where to start this week
Choose one important page and five customer questions. Verify access, inspect the sources that appear, and improve the clearest gap your business can credibly answer. Record the change and repeat the check.
You are building a better source and a more reliable measurement process. Citations remain an outcome to observe, with the platform, question, and context attached.
