Perplexity citation tracking breaks when it ignores the model picker
On this page
Quick Answer
Perplexity can cite different domains for one prompt depending on model and search mode, so a tracker sampling only the default setting reports a source share many Pro users never see.
The fix is boring, which is good news. Log the model, mode and session with every run, and test fewer prompts across more settings. Ethan Smith of Graphite, on Lenny Rachitsky's podcast, files control groups under measuring results, and that is where a Perplexity trend starts earning trust.
Key Points
- When Perplexity launched its Sonar Pro API in January 2025, it said the tier returns double the number of citations per search as standard Sonar on average.
- Prashant Lalwani's research guide notes the Perplexity Pro plan, at $20/month, unlocks unlimited Pro Search plus GPT-4o and Claude models, so Pro users can read answers a default sample never sees.
- One developer marketing agency's seven-day Perplexity view showed its brand on May 5, 7 and 9, 2026, about every other day, so a single weekly snapshot can miss half the picture.
Same prompt, different setting, different sources.
Here's the thing: Matt Paige, writing on Substack in March 2026, describes Perplexity Computer as a system that "coordinates up to 19 AI models at the same time," and most citation reports still photograph exactly one of them. Pick the default setting, run the prompt, log the domains, and you have measured the room with the lights already on. Fine. Your Pro buyers may be sitting next door.
The variance is not a rumor. On a 2025 episode of the Ecommerce Coffee Break podcast, Dr. Jonathan Snow described a visibility index built on the top 60 beauty brands and one shared prompt set, scored by how often each brand was mentioned for each prompt in each model. His verdict was blunt: "every model is very different."
That finding is about engines. Inside Perplexity, the same logic applies to the model picker and the search mode, yet most tracking guides still treat Perplexity as one answer per prompt.
One answer. Per prompt. For a product with a model menu.
We track whether ChatGPT, Claude, Perplexity and Google AI Overviews name our clients, so this is not an academic gripe. It decides whether a report earns its invoice.
Below, I walk through which settings change the cited domains, why a stable prompt set still produces a shaky trend, and how to sample so the line on your chart reflects buyers rather than defaults.
Perplexity is not one answer engine. It is several engines sharing one logo. Vivedha Elango, who teaches retrieval systems on Substack, flags a second trap: a model "might cite [1] for a claim that didn't actually come from [1]," so a counted citation is not always a page that shaped the answer.
Blunt, yes. Also fixable. When we check whether an AI answer named a client, Perplexity is the engine where "did it cite us?" always needs a second question attached: cited in which setting?
Pristren's 2026 guide to the Sonar API shows the split from the developer side. It positions sonar-pro for complex multi-source synthesis, technical deep dives and legal analysis, which is a different job from quick question answering. Different job, different retrieval.
Different retrieval, different domains on the source list.
Here is why that matters to anyone paying for proof. Our guarantee says clients get named in AI answers across their target question set, with no contract and the freedom to cancel anytime, and a promise like that only means something when the measurement samples the answers buyers actually read. Which puts the spotlight on the settings themselves, starting with the toggle most trackers never touch.
Is your Perplexity report measuring the answers your buyers see?
AEO Content is run by founders who built LiveHelpNow into an Inc. 5000 inductee (#84) and bring a combined 40+ years of SEO and content infrastructure experience to AEO.
Pristren lists four Sonar models, each built for a different job. One default sample cannot speak for all four. We track whether ChatGPT, Claude, Perplexity and Google AI Overviews name our clients, engine by engine. For Imagine Dental Arts, AI-referred new patients rose 900%, from about 5 a month to 50.
Which Perplexity settings change the domains it cites?
Four settings reshape Perplexity's source list for one prompt: the retrieval mode toggle, the model picker, the source focus, and whichever API model tier a tracker calls.
Before you trust any Perplexity trend line, check four things on your tracker:
- Retrieval mode: does it run standard search or Pro Search?
- Model: is the default answering, or a model a Pro user would pick?
- Source focus: is it searching the open web, academic sources or social threads?
- API tier: if it samples through the API, which Sonar model does it call?
Start with the toggle. Standard search makes a single pass over the web. Pro Search runs multi-step reasoning across dozens of secondary sources, and the switch between them sits right next to the submit button, where any user can flip it without reading a manual.
The API tells the same story with numbers. In 2025, The Decoder reported that Sonar Pro runs multiple searches per query and typically produces about twice as many source citations as standard Sonar. Perplexity pitched that doubling as a selling point in its own launch materials. Fair enough. A feature for developers is a headache for anyone counting citations.
Then there is the model picker. Prashant Lalwani's research guide notes that the Pro plan, at $20/month, unlocks unlimited Pro Search plus GPT-4o and Claude models. The same guide describes Academic Focus, which restricts sources to PubMed, arXiv, Semantic Scholar and academic publishers, and a Reddit Focus that surfaces user experiences instead of official pages. On the developer side, four Sonar models are positioned for different jobs, from fast Q&A to multi-hop research, and a domain filter can whitelist or block up to three domains per call.
The common assumption is that "Perplexity" names one engine. It names a menu.
A comparison of 5 sources shows the same pattern: every switch changes the pool of domains eligible for a citation. Your brand can sit comfortably in one pool and be absent from the next. The research section below walks through what each switch does to the source list.
This matters to us for a practical reason. AEO Content promises clients they are named in AI answers in 100 days, or we work free until they are, so we care a great deal about which configuration did the naming. Our approach to research-driven content built on evidence starts from the same discipline: know exactly which answer you are measuring before you celebrate it.
Ask your vendor one blunt question: when a Pro user picks Claude instead of the default model, does your tracker ever see that answer? Logging the mode, model and focus beside each sample costs almost nothing. Skipping it is what lets a perfectly stable prompt set produce a trend line that wobbles for reasons nobody can name.
Does a default-setting sample show the Perplexity your buyers see?
Perplexity's own developer guide includes a warning most citation reports never mention: collect the search results the wrong way, and real sources start to look invented.
The page on streaming citations explains that API calls pick an effort level. The "fast" level usually runs one search. Multi-step levels such as deep research run many, returning one batch of results per search, "all sharing a single citation id space." Then comes the warning: "If you keep only the first batch, most [N] references in the text won't resolve and citations will look hallucinated."
For source share, that bug does double damage. Perplexity appears to invent sources, and domains from every search after the first go uncounted, so the share comes from a partial list.
Trackers lean heavily on Perplexity. In an r/AskMarketing thread in January 2026, an agency commenter wrote that tools claiming to track AI mentions "are mostly scraping Perplexity's web results since those are somewhat visible." We track Perplexity for clients too, so we checked what its documentation and close observers say about its settings.
Start with depth. When Perplexity launched its Sonar Pro API in January 2025, it said the tier returns "double the number of citations per search as Sonar on average." The Decoder's launch report gave the reason: the Pro version "runs multiple searches for each query." The consumer app splits the same way. A tutorial on the YouTube channel Automate This describes standard search as "a single pass scan of the web," while Pro Search uses multi-step reasoning across "dozens of secondary sources."
| Setting | Where | Searches behind one answer | What comes back |
|---|---|---|---|
| Standard search | Consumer app | One pass over the web | Not stated |
| Pro Search | Consumer app | Multi-step reasoning | Dozens of secondary sources |
| Sonar | API | Simpler, faster queries | The baseline citation count |
| Sonar Pro | API | Multiple searches per query | About double Sonar's citations per search, on average |
| Fast effort | API | Typically one | Built for quick, citation-rich answers |
| Deep research effort | API | Many, one result batch each | All batches share one citation ID space |
Source share is a fraction, and its denominator moves with every setting. One citation in a single-search answer and one in a multi-search answer represent very different shares.
The app and the API are also separate. A pricing guide from the automation platform Activepieces, published in October 2026, notes that "A consumer Pro or Max subscription is a separate account from an API balance." A tracker calling the API works in a different product from the one buyers type into, and a report should say which it sampled. Free accounts are not purely single-search either: the Automate This tutorial says the free plan includes "a limited number of multi-step pro searches each day."
Hold every setting still and the answers still change. The same tutorial warns that "Running the exact same prompt twice can yield slightly different wordings or sources," and blames shifting web indexes and probabilistic sampling. One developer marketing agency's seven-day Perplexity view of one prompt cluster showed its brand on May 5, 7 and 9, 2026, about every other day, though the agency said it ranked first for one prompt in that cluster. One agency's week cannot establish a rate, but it shows how a single run can catch a good day or a bad one.
Three layers in every Perplexity sample
- Surface and tier: app or API, Sonar or Sonar Pro. Changes how many citations each search returns.
- Search depth: standard or Pro Search, fast or deep research. Changes how many searches feed one answer.
- Run to run: same prompt, same setting, another session. Can change the wording and the sources.
A default-only sample captures one point on the first two layers and still carries all of the third.
One thing we could not find is a public measurement of the model picker on its own. An April 2026 how-to guide says the Pro plan "unlocks unlimited Pro Search, GPT-4o and Claude models." No source we found compared cited domains across those models with mode and depth held constant. The documented differences concern how many searches run and how many sources come back. Whether the model alone changes which domains get cited remains unanswered.
So a default-setting report is a real measurement of one Perplexity configuration, usually one that runs few searches, with ordinary run-to-run noise included. Buyers who switch on Pro Search, or whose questions trigger deeper research, read answers built from a larger pool of sources. The checks below show how much of that your report covers.
- Ask your vendor, or check your own script, whether it samples the consumer app or the API, and which mode, effort level or Sonar tier each sample used.
- Compare citation counts only within one tier. Sonar Pro averages about double Sonar's citations per search, so switching tiers produces a jump unrelated to your content.
- Ask whether any samples run in Pro Search. Even free users get a limited number of multi-step searches each day, so some buyers see the deeper version.
- If your tracker uses a multi-step effort level, open a saved answer and confirm every [N] marker resolves to a URL. Markers with no URL point to the first-batch collection bug.
- Before reporting a gain or a loss, run each core prompt at least three times in clean, separate sessions.
How we checked this
Our sources were Perplexity's developer documentation and its Sonar Pro launch post, a news report on that launch, a YouTube tutorial, a third-party how-to guide, a pricing guide from an automation platform, a Reddit discussion among marketers, and one agency's walkthrough of its own tracking dashboard. None of the figures here come from our client data. The claim that Sonar Pro returns about double the citations is Perplexity's own average, and no one has verified it independently. The alternate-day pattern comes from one agency, one prompt cluster and one week, so it shows that variation happens without showing how much. The Reddit comment is anonymous. We sell answer engine optimization and track Perplexity for clients, so we have a stake in how tracking is done. Still unknown: whether the model picker alone changes which domains are cited, and how far deeper search changes the domains cited as well as the number of citations.
- Perplexity, developer guide on streaming citations, undated.
- Perplexity, Sonar Pro API launch announcement, January 21, 2025.
- The Decoder, report on citations in the Sonar API, January 22, 2025.
- Automate This, YouTube tutorial on Perplexity research audits, November 13, 2026.
- Femi Adegoke, Activepieces, Sonar API cost guide, October 25, 2026.
- Prashant Lalwani, guide to Perplexity research tips, April 21, 2026.
- r/AskMarketing, thread on tracking brand mentions in AI answers, January 1, 2026.
- A developer marketing agency's YouTube walkthrough of its Perplexity tracking dashboard, May 11, 2026. Not named or linked because the agency offers overlapping services.
Why does a fixed prompt set still produce an unreliable Perplexity trend?
A fixed prompt set holds the question steady but not the answer machine. When mode, model and search depth go unrecorded, a trend line mixes configurations and calls the blend a movement.
Look at how most teams track today. A commenter in an r/AskMarketing thread on AI brand mentions described the standard routine: run the same queries weekly or monthly, then record whether the brand appeared, where it ranked in the response, and how it was described. The same commenter called it tedious but actual data. Fair. It is also missing a column.
Nobody in that routine writes down whether Pro Search was on. Or which model answered. Or how many searches ran behind the scenes.
Here's the thing about that missing column. Once it is gone, you cannot tell a real change in citations from a change in who was asking, and how.
A developer marketing agency showed what this looks like in its own dashboard. In its pitch, the agency claims a first-position ranking in Perplexity for one prompt, yet its 7-day history shows Perplexity mentioning the brand only on alternate days: 5, 7 and 9 May. First place, every other day. That is a weird kind of first place.
The agency read that as a pattern to bank on. I read it as noise nobody has explained yet, and a missing configuration log is the first suspect I would question.
The API side has its own trap. Perplexity's developer documentation warns that multi-step effort levels, such as deep research, run many searches and emit one search_results batch per search, all sharing a single citation id space. If a parser keeps only the first batch, the docs say, most numbered references will not resolve and citations will look hallucinated. So a tracker built for single-pass answers does not just undercount deep answers. It quietly mislabels them as broken.
Multiply that across a prompt set and the problem compounds. Brand indexes that do this well already split mention rates by prompt and by model, on the view that every model behaves very differently. Splitting by model is a good start. Splitting by mode and depth inside Perplexity is the step most reports skip.
None of this makes a stable prompt set useless. It makes it necessary and insufficient, which is a less exciting thing to put on a slide.
If you want the plain-language basics on how engines pick sources before you rework a tracker, our AEO FAQ on AI search optimization covers the ground. Then comes the practical part: deciding what a trustworthy sample actually has to record, run by run.
How should a B2B team set up Perplexity citation tracking so the trend can be trusted?
Treat each Perplexity configuration as its own engine. Our AEO Rank standard already tracks ChatGPT, Claude, Perplexity and Google AI Overviews separately; Perplexity's settings deserve the same split.
Some context on why I am comfortable saying that. We have run 26,577 AI-visibility audits against the AEO Rank standard, which scores every site on 53 criteria across 5 pillars, and the audit base covers 11,000+ domains across 15 sectors and 28 categories. Engine-by-engine reporting is the default there because blending engines hides which one actually moved. Configuration inside one engine is the same problem at a smaller scale.
Here is the sampling design I would put in place this week:
- Pin and log the configuration on every run. Record retrieval mode, model, source focus and search depth beside each answer. No log, no data point.
- Sample the modes your buyers use. If prospects research with Pro Search, run both standard and Pro Search for every prompt, and report them as separate lines.
- Capture citations from every search batch. Multi-step answers run several searches; a parser that reads only the first one undercounts and mislabels.
- Repeat each prompt in clean, separate sessions. One run is an anecdote. Several runs give you a rate.
- Separate a brand mention from a cited domain. Perplexity can name you while citing someone else's review page, and the reverse.
- Hold back a control group of prompts. Leave a few untouched by any content work, so you can see drift that has nothing to do with you.
That list costs more effort per prompt. It also lets you cut prompts. A big prompt library run in one setting tells you less than a lean one run across the settings that matter, which is honestly the most counterintuitive budget advice I give.
The measurement this unlocks is the one most reports cannot produce today: the share of cited domains that differ between Perplexity settings for the same prompt. We have not published that figure. Once your log carries configuration, you can calculate it yourself, and it will tell you how much of your current trend is mode mix rather than movement.
Plumbing matters here too. Our team includes a full-stack engineer and content infrastructure architect with 20 years of building enterprise systems, and the unglamorous lesson from that background is simple: a field you do not capture at write time is gone forever. You cannot backfill the mode of a run from last March.
One more hygiene rule. If you also run paid placements, such as sponsored listings that AI engines cite, tag those pages separately in your log. Otherwise a paid lift and an organic lift land in the same column, and your next quarterly review turns into a debate about which one did the work.
What should change in your Perplexity tracking before the next report?
Audit the citations first. This week, open five saved answers, click through each citation to your domain, and confirm the page actually states the claim its marker sits on.
I expect model tier and retrieval mode to become required fields in any tracker worth paying for. Before you renew a tracker, ask for one prompt's cited domains shown model by model, not blended, and watch whether the vendor can produce it.
The raw material already exists. A LibreChat feature request on GitHub notes that Perplexity returns citations by default in a top-level citations array, while the answer text points to sources only through numeric markers like [1][3]. Store the array. Store the setting. Now the line on your chart means something.
We hold our own work to that standard, because a guarantee about getting clients named across their target question set is only as good as the answers sampled to prove it.
So, this week: open last month's Perplexity report and check whether each row says which model and mode produced it. If it does not, you own a trend line, not a trend.
Summarize This Article With AI
Open this article in your preferred AI engine for an instant summary.
Frequently Asked Questions
What else do people ask about Perplexity citation tracking?
Most questions come back to one issue: Perplexity's answers vary by run, mode and model, so every tracked citation needs its setting and session recorded alongside it.
Does Perplexity give the same answer every time?
No. The Automate This tutorial on Perplexity warns that running the exact same prompt twice can return slightly different wording or sources, because web indexes shift and the model samples tokens probabilistically. Expect drift. Plan for it.
How many times should I run each prompt?
Run each core prompt at least three times, in clean, separate browser sessions, before you trust the result. One run is an anecdote, and I would not put an anecdote in a board deck.
Does Pro Search cite more sources than standard search?
It works differently. Standard search does a single pass over the web, while Pro Search uses multi-step reasoning across dozens of secondary sources, so the source list can change shape entirely.
Can I choose which model Perplexity uses?
Yes. Pro subscribers pick a model in the app, and API users choose a Sonar tier per request, with the option to specify which sources Sonar searches. Each choice is a separate configuration to log.
What is the difference between a brand mention and a citation?
A brand mention is your name in the answer text. A citation is your domain in the source list. Perplexity can name you while citing a third-party review site, or cite your domain without naming you, so track them separately.
Should I track through the API or the app?
Both, labeled. The API hands back citations as a structured list, which is easy to store; the app shows what buyers actually see, including a source filter for web, academic papers or social discussions.
Can Perplexity see my traffic or ad spend?
No. It reads public web index data, so it cannot pull private analytics, traffic volumes or advertising spend. Your citation data has to be collected from the answers themselves. For help setting that up, reach the team at aeocontent.ai/contact.
Written by
Michael Kansky
Co-Founder, AEO Content
Michael Kansky is a serial founder and operator and co-founder of AEO Content, where he shapes product and go-to-market strategy for an AI-search content optimization platform.
Connect on LinkedIn


