Perplexity SEO: How Perplexity Picks the Sources It Cites

Perplexity is an answer engine. You type a question, it runs a search against its own index, reads the passages it retrieved, writes an answer, and attaches numbered citations to the passages it used. That last step is the entire reason a marketer types "perplexity seo" into Google: the citation is a link, the link is traffic, and being one of the five or six sources under an answer is now a distribution channel with its own rules.

The rules are mostly written down. That is the part the pages ranking for this term have not noticed. Ten pages hold the United States top ten for perplexity seo on 2026-09-10, and we scraped all ten before writing a word here. Seven are agency guides or service pages. One is a Reddit thread with zero upvotes. One is a video. One is a forum thread on Perplexity's own community site about using the API for keyword work. Across the eight prose pages, which run from 1,525 to 4,019 words, zero cite the document in which Perplexity describes its retrieval and ranking pipeline, zero mention the source-review labels Perplexity attaches to cited domains, and only two mention PerplexityBot by name. One of those two links Perplexity's crawler documentation and paraphrases it as "updates its index daily", which the page it links to does not say.

So this post does the thing the SERP skipped. It walks Perplexity's own account of how a page becomes a citation, stage by stage, quoting the documents with their dates. It separates the three documents that govern crawling, because they govern different things and are routinely conflated. It puts the three published studies of what Perplexity cites side by side, with their sample sizes and windows, so you can see why they disagree with each other by an order of magnitude. And it ends with an honest table of levers: what is documented, what is correlational, and what has been tested with a control, including the one controlled experiment ever run on Perplexity.ai itself.

Everything here was read at its source on 2026-09-10. Where a page carries an update stamp, the stamp is quoted. Where a number comes from a third party, the third party's method is in the table beside it. Where we have our own measurement, it is our own, and it says out loud what it cannot detect.

Perplexity's own materials describe source selection as a pipeline with five stages. Each is named in a first-party document, and each is a different place a page can be dropped.

1. Crawl and index. PerplexityBot fetches pages into an index that Perplexity's research team described as tracking "over 200 billion unique URLs" on 2025-09-25, and that its CEO put at "450B+ high-quality URLs" on 2026-09-09. An ML model decides which URLs to index and when.
2. Parse into units. A content-understanding module with self-improving rulesets extracts the meaningful content from each page and segments it into "self-contained spans, each of which can be individually retrieved and ranked at query time."
3. Retrieve a candidate set. The index is queried "via both modalities", lexical and semantic, and the results are merged, with breadth ahead of precision at this stage by Perplexity's own description.
4. Prefilter and rerank. "Basic heuristics and first-cut filters" remove "clearly non-responsive or stale content", then "multiple stages of progressively advanced ranking" end with "cross-encoder reranker models" doing "the final sculpting of the result set." Scoring happens "at both the document and sub-document levels."
5. Answer and cite. The model reads the surviving passages and, per Perplexity's help center, "each answer includes numbered citations linking to the original sources." A leaked system prompt posted to r/perplexity_ai in June 2026 read, in part, "Your response must include at least one citation."

Three separate documents govern whether your page can enter stage one at all, and they say different things. The crawler documentation describes two bots with different rules. The robots.txt help article describes what a disallow stops and what it does not. The source-labels article describes a domain-level review that sits on top of all of it. We take each in turn below.

The single most common belief on the head-term SERP and in the Reddit threads around it is that Perplexity is a front end for Google or Bing. The position-2 thread for perplexity seo carries a reply asserting that "Google and Bing will be used to determine rankings." An r/SEO moderator opened a widely discussed post in December 2025 with "I asked Perplexity (which is fed by Google)". The belief has a real origin: early Perplexity did use third-party search APIs, and Perplexity says so itself.

The research post that accompanied the Search API launch on 2025-09-25 states: "We experimented with the portfolio of search APIs available in late 2022, and the very first version of Perplexity's answer engine actually incorporated some of these offerings." It then explains why that stopped. The prices were, in its word, "exorbitant", the legacy APIs "prioritized document-level results", and they were "either too stale or too slow". The conclusion Perplexity drew: "making Perplexity even better would require building our own dedicated search infrastructure."

The scale of that infrastructure is stated in the same post, and the numbers are worth quoting exactly because they are the ones nobody on the SERP quotes. Perplexity's production search "processes 200 million daily queries." The index "tracks over 200 billion unique URLs, with capacity to track many hundreds of billions more." The crawler and indexing fleets "collectively comprise tens of thousands of CPUs and hundreds of terabytes of RAM." The system can "process tens of thousands of indexing operations per second."

Twelve months later the index figure had more than doubled. On 2026-09-09, announcing that the Search API had been added to a third-party agent framework, Aravind Srinivas wrote that "Perplexity's index currently includes 450B+ high-quality URLs. Rapidly advancing to a trillion by EOY with high-quality snippets." The developer account's own post the same day said "an index of more than 400 billion URLs." Two first-party figures a few hours apart, 400 and 450, which is a reminder that a round number in a launch post is a round number.

None of this rules out Perplexity reading Google's rankings as one signal among many; the 2024 Reddit reply quoting a Perplexity answer to that effect is a Perplexity answer, not a Perplexity document, and nothing in the 2025 or 2026 first-party posts mentions it. What the first-party record does establish is that the index is Perplexity's own, that it is large, and that it is refreshed on a schedule Perplexity controls. If your page is not in that index, no amount of Google ranking puts it into a Perplexity answer, and the crawler section below is where that is decided.

An index of 450 billion URLs cannot be refreshed uniformly, and Perplexity says as much. The architecture post describes "an inherent tension between completeness and freshness: for a fixed indexing budget, refresh operations for existing pages must compete with indexing operations for new unvisited pages." The way it resolves the tension is the closest thing to a ranking-factor statement Perplexity has published, so here it is verbatim.

On storage tiers: "We use both learned models and tuned heuristics to determine which documents should be kept hot, prioritizing documents from authoritative domains, documents involving undercovered topics, and other categories with outsize potential to enrich our index."

On indexing decisions: "We train an ML model to predict whether any given candidate URL needs to be indexed. The training objective is crafted to ensure that we calibrate our indexing decision to both the importance and likely update frequency of the specific URL. We also rely on ML to tell us precisely when to schedule the indexing operation. For sites with routine publication and refresh cadences, this allows us to defer operations to the point in time that they are likely to be most useful."

Two years earlier, in the 2023-11-29 post introducing its first online models, Perplexity had described the same index in a sentence that agency guides would do well to read: "Our search index is large, updated on a regular cadence, and uses sophisticated ranking algorithms to ensure high quality, non-SEOed sites are prioritized."

Read those three passages together and a picture forms that is neither the "it is all Google" belief nor the "nobody knows, it is proprietary" belief that tops the r/artificial thread on this question. Perplexity says it prioritises authoritative domains, undercovered topics, and pages whose update cadence it has learned. It says it prioritises non-SEOed sites, which is a strange thing for a SERP full of SEO agencies to have missed. And it says the schedule is learned per site, which means a site that publishes on a regular rhythm teaches the crawler when to come back.

The part of Perplexity's pipeline that differs most from a 2015 mental model of search is that the unit being ranked is not the page. It is the passage, a self-contained span the parser cut out of the page and the reranker scores on its own.

The architecture post is explicit: "Our indexing and retrieval infrastructure divides documents up into fine-grained units. These sub-document units are individually surfaced and scored against the original query parameters." And later, on the purpose of good parsing: it "allows us to decompose documents into self-contained spans, each of which can be individually retrieved and ranked at query time."

The parsing that produces those spans is not a fixed ruleset. Perplexity describes "a content understanding module that parses websites and extracts semantically meaningful content using dynamic rulesets." The rulesets are evaluated by "frontier LLMs" on two dimensions, "completeness" and "quality", and the module "formulates a set of proposed ruleset changes to address the most significant error classes" which are validated and deployed to the indexer. The post calls this "an iterative self-improvement loop" fed by "an incredibly rich cross-section of the web in the course of serving millions of user queries hourly."

The embedding models that place those spans in vector space were published in February 2026. The pplx-embed announcement on 2026-02-26 states that "At Perplexity's scale, embeddings are the first stage of our retrieval pipeline, determining which documents from billions of web pages get considered by downstream rankers and language models." It also describes a second model, pplx-embed-context-v1, which "embeds passages with respect to surrounding document-level context", meaning a passage is scored partly on what the rest of the page is about.

What this means in practice, stated without the tactics-list gloss:

• A page is not cited as a whole. A paragraph, a table row, or a definition is retrieved, and the page gets the citation because that unit came from it.
• The unit has to be extractable. Perplexity's parser is good and self-improving, but a claim split across three divs with a marketing interjection in the middle is a worse span than a claim stated in one clean paragraph.
• The surrounding page matters to the passage's score, per the context embedding, so a strong paragraph on an off-topic page carries less than the same paragraph on a page about the same thing.

The retrieval stage is where a page enters the running for a given query, and Perplexity describes it as deliberately generous. "We do not force a choice between lexical and semantic retrieval. Rather, we query the search index via both modalities and merge the results into a hybrid candidate set." The post adds that this stage favours breadth, and that "subsequent stages of the pipeline will optimize for precision."

Two things follow. First, exact wording still matters: lexical retrieval means the words in the query are matched against the words in the index, so a page that never uses the phrase a buyer types is relying entirely on the semantic side. Second, semantic retrieval means a page can be a candidate without matching the phrase at all, which is why Perplexity answers sometimes cite a source that a keyword search would never have surfaced.

The prefilter is short in the description and consequential in effect: "prefiltering stages, in which we apply basic heuristics and first-cut filters to remove clearly non-responsive or stale content from the candidate set." Stale is named as a removal criterion. Perplexity does not publish a freshness threshold, and the API documentation exposes a recency filter that developers can set, so "stale" is at least partly query-dependent.

Then the reranking. "Earlier stages rely on lexical and embedding-based scorers optimized for speed. As the candidate set is gradually winnowed down, we then use more powerful cross-encoder reranker models to perform the final sculpting of the result set." A cross-encoder reads the query and the passage together and scores the pair, which is more expensive and more accurate than comparing two vectors, and it is applied only to the survivors.

The signal that trains these rankers is stated too, and it is the part that a page cannot game directly. Every detail of the ranking stack, the post says, is built on "the rich signal produced by the millions of user requests we serve each hour of the day. The vast majority of this signal is automated, with each generated Perplexity answer providing an empirical datapoint on search quality as used in a live agentic workflow. We combine AI-driven evaluations with live human feedback to enrich the training data for our embedding and ranking models."

A September 2026 engineering post confirms where the compute goes: "Every answer in Perplexity starts with embedding and ranking models picking the most relevant results for the query", as the company put it on X on 2026-09-04, linking a post about serving those models on GPUs.

Once the reranker has produced a result set, a language model writes the answer. Perplexity's help center describes the model options (its own Sonar, plus third-party models a Pro subscriber can select) and describes the citation step in one line: "Each answer includes numbered citations linking to the original sources, allowing you to easily verify the information or explore further."

The model is instructed to cite. In June 2026 a Perplexity user posted what appeared to be the full system prompt after the model echoed it back in a Terraform question. We treat a leaked prompt as a user report rather than as documentation, and note it because it is consistent with everything Perplexity has published. The relevant lines: "You need to use these tools rather than using internal knowledge" and "Your response must include at least one citation."

The Pro Search help article adds the detail that matters for how many sources an answer draws on. Pro Search "conducts multiple searches across the web, drawing from articles, academic papers, forums, videos, and more, depending on your selected focus" and "reads, analyzes, and compiles insights from dozens of sources." Deep Research, per the main help article, "performs dozens of searches automatically, reads hundreds of sources." So the number of retrieval passes, and therefore the number of chances a page has to be a candidate, depends on which mode the user is in.

One number from a third party belongs here because it is the only published count of citations per answer we could find, and it is old: BrightEdge's Generative Parser reported "5.28 citations, on average, per response" in its early-2024 analysis, as relayed by Search Engine Land on 2024-04-03. Treat that as a 2024 snapshot of a product that has changed its modes and models several times since.

Perplexity sells the same retrieval pipeline to developers as the Search API, and the parameters it exposes are a second first-party description of what the pipeline can and cannot do, written as code rather than prose. We read the API guide on 2026-09-10; it is roughly 120,000 characters, most of it examples, and the parameter names are the part that matters here.

The guide documents a search_domain_filter, which restricts or excludes results to a list of domains; a search_recency_filter and date-bounded filters, which restrict results by publication window; a country parameter and a search_language_filter; max_results and max_tokens_per_page, which bound how many results and how much of each page come back; and a search_context_size setting that controls how much retrieved material is handed to a model. The launch post describes the returned shape: the API returns "documents with the most relevant snippets already ranked," because "sub-document units are individually surfaced and scored against the original query parameters."

Three things a site owner can read off that list without any inside knowledge.

First, the pool is filterable by domain, date, country and language at query time, which means "is my page in the index" and "is my page in the candidate set for this query" are different questions. A page can be indexed and excluded by a recency filter the user or developer set. The stale prefilter in the consumer product is the same capability with a default the user does not see.

Second, the response is snippets, not pages. max_tokens_per_page exists because the pipeline hands back a bounded slice of each document, ranked, and a model builds an answer from the slices. A page whose best sentence sits below a long preamble is competing with its own preamble for that slice.

Third, the developer product and the consumer product share infrastructure. The launch post says so directly: "Our API provides access to the same global-scale infrastructure that powers Perplexity's public answer engine." So a test against the Search API is a test against the same retrieval and ranking that produces citations in the app, minus the answering model and its instructions. That is a cheap and repeatable way to see whether your passages are retrieved at all before worrying about whether they are cited, and it is the instrument we would use to build the noise band described later in this post.

Take a question a developer-tool buyer puts to an assistant: which rate-limiting library to use for a Node API. Walk it through the pipeline as Perplexity describes it, and the places a vendor's page can drop out become concrete.

At stage one, the vendor's documentation page has to be in the index. If the docs site sits behind a bot-management rule that challenges unknown traffic, and the rule was never told about PerplexityBot's 8 published prefixes, the page is not in the index and the walk ends here. Nothing downstream can recover it.

At stage two, the page is parsed into spans. A docs page with a clear heading, a two-sentence description of what the library does, and a table of limits parses into clean units. A marketing page whose only description of the product is split across a hero line, three feature tiles and a footer tagline parses into fragments that each say less than the buyer's question needs.

At stage three, both lexical and semantic retrieval run. If the buyer's question says "rate limiting" and the page says "throttling" throughout, the lexical side misses and the semantic side has to carry the match alone. If the page says both, it enters the candidate set twice over.

At stage four, the prefilter drops anything non-responsive or stale, then the rerankers score the survivors as query-passage pairs. A span that states what the library does, for which runtime, with a number, scores as an answer. A span that says the library is trusted by teams worldwide scores as a slogan. Perplexity's 2023 line about prioritising non-SEOed sites and the KDD paper's keyword-stuffing result are two independent descriptions of the same reranker behaviour.

At stage five, the model writes the answer and cites the spans it used. If the buyer is in Pro Search, the model has read dozens of sources, so the vendor's span competes with the Reddit comment where someone benchmarked three libraries, the GitHub README, and the comparison post on a developer blog. In every instrument that has counted, community pages are large sources for Perplexity, so a vendor's presence in those threads is not a separate channel from its own docs; it is another candidate span in the same pool.

Nothing in that walk involves a factor list, a schema type or a freshness window. It involves being indexed, being parseable, using the buyer's words, answering directly, and being present where the buyer's peers answer. That is the whole of what Perplexity has documented, and it is enough to act on.

If a page is not in the index it cannot be cited, so the crawler rules are the first gate. Perplexity publishes three documents that touch this, and most of the confusion in the Reddit threads comes from reading one as if it were the others.

Document one: the crawler page at docs.perplexity.ai. It lists two user agents. PerplexityBot "is designed to surface and link websites in search results on Perplexity. It is not used to crawl content for AI foundation models." Its full user-agent string is published, along with a JSON file of IP addresses. Perplexity-User "supports user actions within Perplexity. When users ask Perplexity a question, it might visit a web page to help provide an accurate answer and include a link to the page in its response." It too has a user-agent string and an IP JSON. And then the sentence that matters: "Since a user requested the fetch, this fetcher generally ignores robots.txt rules."

We fetched both IP files on 2026-09-10. The PerplexityBot file, with a creationTime of 2025-02-07, listed 8 IPv4 prefixes, every one a single /32 address. The Perplexity-User file, with a creationTime of 2025-10-17, listed 4. The page tells operators to "always use the most current IP ranges from the official JSON endpoints" and to "set up automated processes to periodically fetch and update your WAF rules", which is good advice given that the files can change without the docs page changing.

Document two: the robots.txt help article. Last modified 2026-09-10, the day we read it. "Perplexity respects robots.txt directives. Our crawler, PerplexityBot, will not index the full or partial text content of any site that disallows it via robots.txt. However, if a page is blocked, we may still index the domain, headline, and a brief factual summary." The article also addresses the history directly, under the heading "Why have I read that Perplexity's crawlers don't respect robots.txt?": "Previously, users could prompt Perplexity to summarize a specific URL, even if it was blocked by robots.txt... However, this feature has been disabled to prevent misuse." And on third parties: "Perplexity partners with third-party crawlers to help build our search index. We have updated our agreements to ensure these providers also respect robots.txt, particularly for news publisher sites."

Document three: the source-labels article. This one governs neither crawling nor indexing. It governs a shield icon on some citations, and it is the subject of the next section, because it is the only place Perplexity describes a source review process in its own words.

Put the first two together and the practical reading is this. A robots.txt disallow on PerplexityBot stops your page text from being indexed by the search crawler, but Perplexity says it may still index the domain, the headline and a summary, and it says the user-triggered fetcher generally ignores the file. So a disallow reduces your presence in Perplexity answers; it does not zero it. If the goal is to be cited, the relevant question is the opposite one: is PerplexityBot allowed, and are its published IPs allowed through the WAF, since a firewall block is invisible to robots.txt and Perplexity's own docs say to allow both the user agent and the IP range together.

No discussion of Perplexity's crawling is complete without the August 2025 dispute, and the ranking pages either omit it or take a side. Both sides published, so both are quoted.

On 2025-08-04 Cloudflare published a post titled "Perplexity is using stealth, undeclared crawlers to evade website no-crawl directives." Its claims: Cloudflare "created multiple brand-new domains", put a robots.txt on them disallowing all crawlers, blocked both declared Perplexity user agents at the WAF, then asked Perplexity questions about the domains and "discovered Perplexity was still providing detailed information regarding the exact content hosted on each of these restricted domains." Cloudflare's table attributed "20-25m daily requests" to the declared Perplexity-User agent and "3-6m daily requests" to a "stealth" agent presenting as Chrome on macOS, said the undeclared crawler "utilized multiple IPs not listed in Perplexity's official IP range", and stated it had "de-listed them as a verified bot."

The same day Perplexity published "Agents or Bots? Making Sense of AI on the Open Web." Its position: "User-driven agents only act when users make specific requests, and they only fetch the content needed to fulfill those requests. This is the fundamental difference between a user agent and a bot." On the specific numbers: "It appears Cloudflare confused Perplexity with 3-6M daily requests of unrelated traffic from BrowserBase, a third-party cloud browser service that Perplexity only occasionally uses for highly specialized tasks (less than 45,000 daily requests)." And on the diagram: "Cloudflare published a technical diagram supposedly showing 'Perplexity's crawling workflow' that bears no resemblance to how Perplexity actually works."

We are not in a position to adjudicate whose traffic the 3 to 6 million requests were. What both documents agree on is useful on its own. Both agree that Perplexity-User is a user-triggered fetcher operating at tens of millions of requests a day. Both agree that it behaves differently from an index crawler. Cloudflare says user-triggered fetches should still honour robots.txt; Perplexity says they are the user's own request and should not. Perplexity's crawler documentation, read a year later, still says the fetcher "generally ignores robots.txt rules", so the disagreement is about policy, not about what the fetcher does.

For a site that wants citations, the operational consequence is the one already stated: a WAF rule that blocks Perplexity's published IPs blocks the index crawler that would surface you in search results, and a robots.txt disallow does the same for page text. The Cloudflare post notes that when the fetch was blocked, "Perplexity uses other data sources, including other websites, to try to create an answer. However, these answers were less specific and lacked details from the original content." Which is another way of saying the block worked, and the citation went to someone else.

The most recently updated document in this set is also the least discussed. Perplexity's help article "Understanding source labels", last modified 2026-09-09, describes the one part of source selection that is explicitly editorial rather than algorithmic.

"When Perplexity cites a source, some citations carry a small shield icon. The icon marks a domain that Perplexity's source review process has rated, and it comes with one of three labels: Government, Academic, or Trusted."

The unit of review is the domain: "Perplexity rates the whole website a source comes from, not each individual page." The tests are stated as questions: "Does the site correct its mistakes? Does it say who wrote each piece? Does it keep news separate from advertising and opinion?" And then two sentences that answer the question every agency page dances around: "Labels are set by the source review process alone. Perplexity's partnerships, payments, and other business arrangements do not affect a site's label."

The article is equally clear about what the absence of a label means, which is nothing: "Most domains on the web do not have a label. No label does not mean a site is low quality, and it is not a negative judgment. It means the domain has not been rated yet, or there is not yet a clear rating for it."

The three labels, with Perplexity's own examples: Government (nasa.gov, epa.gov), Academic (science.org, journals.plos.org), and Trusted, described as "a broad category for sites that appear often enough in results to receive a label and that publish information within their own area of expertise" (reuters.com, mayoclinic.org).

Read that Trusted definition carefully, because it contains a sequence. A site "appears often enough in results" first, and receives a label second. The label is downstream of being retrieved and cited repeatedly, not upstream of it. For a developer-tool company with a two-year-old domain, the honest reading is that a label is not something to pursue; it is something that may follow if the retrieval pipeline keeps selecting you for a subject you cover.

What the article does not say is also worth stating. It does not say labelled sources rank higher in retrieval. It describes the label as something "you" the reader can see to "judge the source at a glance", and offers a "Rate this source" control for feedback. Whether the label feeds the reranker is not documented, and we are not going to assert it either way.

Because the source-labels article says payments do not affect labels, it is worth being precise about what Perplexity's commercial programmes with publishers do, since "Perplexity pays publishers" gets compressed into "Perplexity cites paying publishers" on the way through a tactics list.

The Publishers' Program, announced 2024-07-30 with TIME, Der Spiegel, Fortune, Entrepreneur, The Texas Tribune and WordPress.com as launch partners, describes revenue sharing tied to advertising: "When Perplexity earns revenue from an interaction where a publisher's content is referenced, that publisher will also earn a share." The same post notes, without detail, "Recently, we updated how our systems index and cite sources."

Comet Plus, announced 2025-08-25, is a subscription that "allocates revenue to our partners based on three types of internet traffic: human visits, search citations, and agent actions." Perplexity described it as a standalone subscription included with Pro and Max, with "all of that revenue" distributed to participating publishers "minus a small portion for Perplexity's compute costs."

Then there are the licensed data sources. On 2026-05-05 Perplexity announced that its products "now connect to premium health sources, starting with NEJM and BMJ Group, with 9 more medical journals and clinical databases on the way," and on 2026-05-06 that "Finance Search is now available in the Perplexity Agent API" with "licensed financial datasets." The Search product page lists "Premium Sources" as a subscription feature.

So there are three different money relationships, and they do three different things. Revenue share pays a publisher after a citation happens. Comet Plus pays publishers for traffic of three kinds and gates subscriber access to their content. Licensed datasets put a source into a specific search mode (Finance, Health) that a user or developer selects. None of the three is documented as a ranking input in the open-web pipeline, and the labels article says explicitly that none of them affects a label. A developer-tool company is not going to become NEJM, and the useful takeaway is narrower: the way into a Perplexity answer for a normal site is the pipeline, and the pipeline's inputs are the crawl, the parse, the passage and the reranker.

Now the measurement side. Three organisations have published large-sample counts of which domains Perplexity cites. Each is a real dataset with a stated method. They do not agree, and the disagreement is the finding.

Profound, in a study first published 2025-06-05 and updated in August 2025, analysed "680 million citations" across ChatGPT, Google AI Overviews and Perplexity from August 2024 to June 2025. For Perplexity, its top-10 share table puts Reddit at 46.7 percent, YouTube at 13.9 percent, Gartner at 7.0, Yelp at 5.8, LinkedIn at 5.3. As a share of all citations in its Perplexity dataset, Reddit was 6.6 percent and YouTube 2.0 percent. Profound's own summary: "Perplexity's Reddit concentration."

Ahrefs, on 2025-06-11, looked at "the top 10 websites cited in Ahrefs Brand Radar" across "~76.7M AI Overviews, 957k ChatGPT prompts, and 953.5k Perplexity prompts for the month of June 2025." Its finding for Perplexity: "YouTube is a clear favorite in Perplexity (16.1%)", Wikipedia at 12.5 percent, and, in its own words, "Reddit and Quora rank high only in AI Overviews. They don't crack the top-10 in ChatGPT or Perplexity."

Semrush, on 2025-11-10, checked "weekly citations for more than 230,000 prompts over 13 weeks" from 2025-07-14 to 2025-10-12 across ChatGPT search, Google AI Mode and Perplexity. Its Perplexity finding: "Perplexity's top sources were Reddit, LinkedIn, NIH, Microsoft, and Google", with the note that "the biggest overall shift on Perplexity was the negative trend for Reddit citations," and Wikipedia holding "near 0.8% on Perplexity."

Same engine, same year, and Reddit is 46.7 percent of the top-10 share in one instrument, absent from the top 10 in another, and the number-one source in a third. The three are not measuring the same quantity. Profound reports share of citations among the top-10 domains over ten months. Ahrefs reports mention share over one month of prompts drawn from its own tracked set, weighted in some views by search volume. Semrush reports the share of prompt responses in which a domain appears, weekly, over a quarter. The prompt sets differ, the windows differ, the unit differs, and Perplexity itself changed its models and modes across the period.

What survives the disagreement is a smaller and more defensible set of statements:

• Reddit and YouTube are large sources for Perplexity in every instrument that can see them, and their relative size depends entirely on what you count.
• Wikipedia is a much smaller share of Perplexity's citations than of ChatGPT's, in both Ahrefs (12.5 versus 16.3 percent) and Semrush (0.8 percent of responses versus a peak near 55 percent on ChatGPT before September 2025).
• Community and professional platforms (Reddit, LinkedIn, YouTube) sit alongside institutional ones (NIH, Gartner) in every top list, which is consistent with a pipeline that retrieves passages rather than ranking domains.

The user side of this is a thread from December 2025 in r/perplexity_ai, 243 upvotes and 124 comments, titled "Using Grokipedia as a source is unacceptable." The poster's objection rests on a premise: "the sight was deeply unsettling, especially because Perplexity is reputed for its curated sources." The source-labels article, read against that thread, explains the gap. The curation is a domain-level label on a minority of domains; everything else in the candidate set is there because the retrieval pipeline scored a passage, and the pipeline does not consult a reputation list for the unlabelled majority. A citation to an AI-generated encyclopedia is what passage-level retrieval over an open index looks like when nobody has rated the domain yet.

Reddit deserves its own section because it is the largest single source in two of the three studies, because Perplexity's "Social" search mode is, per its own users, built on it, and because Reddit sued Perplexity over it in October 2025.

Perplexity's statement of what it does with Reddit content is unusually direct, and it was posted as a Reddit thread. On 2025-10-23, the official u/perplexity_ai account wrote in r/perplexity_ai, in a post that reached 2,387 upvotes and 372 comments: "What does Perplexity actually do with Reddit content? We summarize Reddit discussions, and we cite Reddit threads in answers, just like people share links to posts here all the time." And: "Perplexity, as an application-layer company, does not train AI models on content. Never has." The post frames the lawsuit as "a show of force in Reddit's training data negotiations with Google and OpenAI."

The lawsuit itself, as reported the day it was filed, named Perplexity alongside several scraping vendors. An X post from 2025-10-24 with 436 favourites put it as "Reddit just sued Perplexity and a bunch of scrapers (SerpApi, Oxylabs, AWMProxy)." We have not read the complaint and are not summarising its claims; what matters for source selection is Perplexity's own description above, which is that Reddit threads are summarised and cited, not trained on.

The user-side view of Reddit as a source is mixed, and it is worth reading because it describes the retrieval unit. A feature request in r/perplexity_ai from 2025-10-11 (177 upvotes) opens: "Love that Perplexity mines Reddit gold, but for serious tech or pro questions it too often lifts one lone comment from u/noname123." A reply with 42 points asks for geo-aware social sources. Another with 7 points: "Feels good to know it relies solely on an echo chamber social media to provide me 'opinions' and 'discussions'."

"Lifts one lone comment" is a precise description of passage-level retrieval applied to a forum. The pipeline does not cite r/perplexity_ai; it cites a span, and on Reddit the span is often a single comment. For a developer-tool company, that has a concrete implication that our own earlier measurement supports: the threads where your category is discussed are retrievable units, and a factual, specific comment in one of them is a candidate passage in exactly the way a paragraph on your own site is. Our measurement of 60 live answers on money queries found 91.5 percent of citations pointing off-site, with reddit.com the largest single host at 38 percent of citations. That was measured on a different engine mix and is published on our measurement page, so it is a directional reading rather than a Perplexity figure; the Perplexity-specific studies above point the same way.

The second question every agency page answers with confidence is whether ranking in Google gets you cited in Perplexity. There are two published measurements, eighteen months apart, and they say 60 percent and 28.6 percent.

BrightEdge, via its Generative Parser, reported in early 2024 that "Sixty percent of citations on AI search engine Perplexity overlap with the top 10 Google organic search results," with healthcare highest at 82 percent and restaurants lowest at 27 percent, across nine industries. The figure was relayed by Search Engine Land on 2024-04-03 and sits in BrightEdge's own Perplexity guide, which was last updated 2024-12-26.

Ahrefs, on 2025-08-11, ran a different design: "a dataset of 15,000 prompts" across ChatGPT, Gemini, Copilot and Perplexity, measuring how often cited URLs "overlap with what Google or Bing ranks for the same query." Its headline is that only 12 percent of AI-cited URLs sit in Google's top 10 on average, and its Perplexity finding is the outlier: "Perplexity consistently favors content that ranks well in Google, with 28.6% of its cited URLs landing in the top 10." Ahrefs adds, in the same post, that "unlike Gemini and other AI assistants, Perplexity doesn't draw on Google or Bing's index. In fact, it has its own search index, based on its crawler: perplexitybot."

Sixty and 28.6 are not a trend. One counts domain overlap on an industry keyword set in early 2024; the other counts URL overlap on a 15,000-prompt set in mid 2025. URL overlap is a stricter test than domain overlap, and the prompt sets are unrelated. What both say is that Perplexity's citations overlap with Google more than other assistants' do, and less than a hundred percent, which is exactly what you would expect from an engine with its own index that shares the web's authority signals without sharing Google's ranking function.

For the reader who came here from Google: ranking well in Google is a correlate of being cited by Perplexity. It is not the mechanism. The mechanism is the section above, and a page can be in Google's top ten and fail the prefilter for staleness, or lose the reranker to a passage that answers the question more directly, or be absent from Perplexity's index because a WAF rule blocks its published IPs.

Everything above is either Perplexity's description of its own system or a correlational count of its outputs. There is exactly one published experiment that changed pages and measured what Perplexity did, and it is older than most of the tactics that cite it.

"GEO: Generative Engine Optimization", by Pranjal Aggarwal and colleagues at Princeton and IIT Delhi, was submitted to arXiv on 2023-11-16, revised through 2024-06-28, and accepted to KDD 2024. Its main experiments ran on a generative engine the authors built, over a benchmark of 10,000 queries, and reported that "GEO can boost visibility by up to 40% in generative engine responses." That 40 percent figure is the one every agency guide repeats, usually without the sentence that follows it: "we show the efficacy of these strategies varies across domains."

The part that matters for this post is Section 6, "GEO in the Wild", where the authors "evaluate them on Perplexity.ai, a real deployed Generative Engine with a large user base." Table 5 gives four rows. On the position-adjusted word count metric, no optimization scored 24.1, keyword stuffing 21.9, quotation addition 29.1, statistics addition 26.2. On the subjective impression metric, the same four scored 24.7, 28.1, 32.1 and 33.9. The authors' summary: "Quotation Addition performs best in Position-Adjusted Word Count with a 22% improvement over the baseline," while keyword stuffing "performs 10% worse than the baseline."

Three cautions before anyone builds a service on that table. The experiment ran on Perplexity.ai in late 2023 or the first half of 2024, before the index reached 200 billion URLs, before the pplx-embed models, and before the September 2025 pipeline description; the engine it measured is not the engine running today. The two metrics disagree on the winner, with quotations best on one and statistics best on the other. And the paper measures visibility within an answer, not whether a page is retrieved at all, which is the gate most pages fail first.

What the paper does establish, and what no later study has contradicted, is the direction: adding sourced quotations and sourced statistics to a page increased how much of the Perplexity answer was attributed to it, and adding keywords decreased it. That is consistent with a cross-encoder reranker that scores passages on whether they answer the question, and inconsistent with a term-frequency ranker. Perplexity's own 2023 line about prioritising "non-SEOed sites" is the same finding from the other side.

Every number in this post so far is either Perplexity's or someone else's. This section is ours, and it is here because it changes how every other number should be read.

We ran a step-zero measurement: 12 money queries, each repeated 5 times, identical by construction, against one model on one day. All 60 calls succeeded. Seven of the twelve queries flipped outcome across repeats that were word-for-word identical. We then ran a permutation test, 20,000 random splits of the same query set with no intervention applied, to see what a "lift" looks like when nothing has changed. The null difference centred on zero, mean plus or minus 0.0016, with a standard deviation of 0.215. The full method and numbers are on our measurement page, why a single AI visibility score is noise.

What that means for Perplexity SEO specifically. If you change a page, ask Perplexity a question once before and once after, and see a citation appear, you have observed one draw from a distribution in which 7 of 12 queries flip on their own. You have not observed a lift. To see a lift you need a design that can distinguish a change from that noise, and our own design's minimum detectable lift is 51.1 percentage points, roughly four times underpowered against the 40-query by 40-sample design that would reach 9.9 points. We publish that number because it is the number that is normally missing, and because it is the reason no lift figure appears anywhere in this post.

It also means the third-party citation studies should be read as distributions, not points. Profound's 46.7 percent and Ahrefs' "not in the top 10" are both single readings of a system whose per-query output moves between identical calls. Neither study reports a repeat-run variance, and until one does, the honest statement is that Reddit is a large Perplexity source with an unknown error bar.

Here is the table the SERP does not have. Every lever that appears in the ranking pages, sorted into three columns: documented by Perplexity, correlated in a published study, or tested with a control. A lever can appear in more than one column. A lever in none of them is asserted, and this post does not list those.

Documented by Perplexity

• Allow PerplexityBot in robots.txt and allow its published IP prefixes through the WAF (crawler docs, read 2026-09-10). A disallow removes page text from the index; the domain, headline and a summary may still be indexed (robots help article, updated 2026-09-10).
• Publish on a regular cadence. The indexer "calibrates our indexing decision to both the importance and likely update frequency of the specific URL" and schedules refreshes accordingly (architecture post, 2025-09-25).
• Keep pages current. "Stale content" is named as a prefilter removal criterion (same post).
• Write extractable, self-contained passages. The unit of retrieval and ranking is the "sub-document" span (same post; pplx-embed post, 2026-02-26).
• Use the words the buyer uses, because retrieval is lexical as well as semantic (same post).
• Do not stuff keywords. The index "prioritizes high quality, non-SEOed sites" (2023-11-29), and keyword stuffing scored below baseline in the only experiment (KDD 2024).
• Cover your subject on your own domain. The Trusted label goes to sites that "publish information within their own area of expertise", and the context embedding scores a passage against its page (labels article; pplx-embed post).

Correlated in a published study

• Ranking in Google's top 10: 28.6 percent of Perplexity-cited URLs did (Ahrefs, 15,000 prompts, 2025-08-11); about 60 percent domain overlap in early 2024 (BrightEdge).
• Presence on Reddit, YouTube and LinkedIn: large shares in every instrument, with the size depending on the instrument (Profound, Ahrefs, Semrush, 2025).

Tested with a control

• Adding sourced quotations: 22 percent improvement in position-adjusted word count on Perplexity.ai (KDD 2024, Table 5).
• Adding sourced statistics: best on the subjective impression metric in the same table.
• Keyword stuffing: 10 percent worse than baseline in the same table.

Not documented, not measured, or contradicted

• A special schema type for Perplexity. Nothing in Perplexity's documents mentions structured data as a retrieval input. Our sibling post on schema markup and AI citations covers the one controlled study on other engines, which returned a null.
• An llms.txt effect. Perplexity's documents do not mention the file. We covered the evidence in does llms.txt move AI citations.
• Buying a label or a citation. "Perplexity's partnerships, payments, and other business arrangements do not affect a site's label" (labels article, 2026-09-09).

A short list for a developer-tool company, in the order the pipeline applies it, with the Perplexity document that backs each step, so nothing here rests on an agency assertion or on a factor list nobody published.

1. Confirm you are crawlable. Fetch your robots.txt and check for a PerplexityBot disallow, including in a wildcard block. Then check your WAF and CDN bot rules for the two user-agent strings and for the IP prefixes in the two JSON files, which had 8 and 4 entries on 2026-09-10. A firewall block is invisible in robots.txt. Our post on which OpenAI crawler decides whether ChatGPT can cite you walks the same check for a different engine.
2. Check your server logs for the two agents. If PerplexityBot has never appeared, the index question is answered. If Perplexity-User appears and PerplexityBot does not, users are triggering fetches of your pages but the search crawler is not indexing them, which usually means a block on the crawler's IPs.
3. Find the passages a buyer would need. Take the ten questions your buyers ask an assistant, listed in the questions developer tool buyers ask AI, and for each, find the single paragraph on your site that answers it directly. If there is no such paragraph, that is the work. If there is one but it is split across a hero, a feature grid and a footnote, that is also the work.
4. Date and source your numbers. Perplexity's own labels process asks whether a site names its authors and corrects its mistakes; the KDD experiment found sourced statistics and quotations moved attribution. Both point the same way.
5. Publish on a rhythm, and update on a rhythm. The indexer learns your cadence. A changelog page that moves weekly is a page it learns to revisit.
6. Establish the noise band before you change anything. Repeat your buyer queries enough times to know how far they move on their own. Without that number, step 7 is theatre.
7. Then change one thing, and measure against the band. Our approach to this is on measuring answer engine optimization lift.

A mechanism explainer is only as honest as its list of absences, so here is ours: the six things we looked for in Perplexity's own documents and in the published measurements, and did not find in either.

We did not find a published freshness threshold. "Stale" is a prefilter criterion and the API has a recency filter; how old is too old for a given query is not documented.

We did not find any documentation that the source labels feed the reranker. The labels article describes them as reader-facing.

We did not find a Perplexity statement on whether Google or Bing rankings are an input. The 2024 Reddit reply quoting a Perplexity answer to that effect is an answer, not a document, and the 2025 and 2026 posts describe an independent index without mentioning either.

We did not find a repeat-run variance in any of the three citation studies, so we cannot say how much of the disagreement between them is instrument and how much is Perplexity changing under them.

We did not find any controlled experiment on Perplexity newer than the KDD 2024 paper, whose Perplexity rows predate the current pipeline.

And we did not measure Perplexity ourselves at the scale needed to say anything about a lift. Our published design is underpowered by its own arithmetic, and we would rather print that than a number it cannot support.

We read all eight prose pages on the head SERP for this term on 2026-09-10. Four patterns recur across them, and each one is a place where Perplexity's own first-party record says something different from the page.

Pattern one: the factor list. Six of the eight present a numbered list of "Perplexity ranking factors." Perplexity has never published a factor list. It has published a pipeline, twice, and a labels process once. A factor list is a genre convention imported from Google SEO, and Perplexity's own 2023 sentence about prioritising "non-SEOed sites" reads as a direct comment on it.

Pattern two: freshness as a rule. Several pages state that Perplexity "prefers content from the last N months" with a specific N. No such N is documented. What is documented is a learned per-URL refresh schedule and a prefilter for stale content, which together mean freshness is relative to the query and to your own site's history, not a fixed window.

Pattern three: Reddit as a hack. The pages that mention Reddit present it as a channel to seed. The retrieval unit on Reddit is a comment, and the comment is scored by the same reranker as a paragraph on your site. A promotional comment is a weak passage; a specific answer from someone who has used the tool is a strong one. Our Reddit and community marketing practice is built on the second kind, and the distinction is the whole practice.

Pattern four: the daily index. The one page that links Perplexity's crawler documentation paraphrases it as "Perplexity updates its index daily." The linked page says nothing about the update interval; the architecture post says "tens of thousands of indexing operations per second" against an ML-scheduled refresh. The paraphrase is not false so much as invented, and it is the kind of sentence that gets repeated until it appears in a Perplexity answer as fact.

This is the fourth engine-specific post in our AI citations series. The pattern across all four is the same. Each engine publishes more than the advice pages read, each publishes less than the advice pages claim, and the measurements that exist disagree with each other in ways that come from the instrument rather than the engine.

For Google, the AI Overview optimization post found the company's own guide ranking first for the term and saying no special optimization exists. For OpenAI, the crawler post found three user agents doing three jobs and most robots.txt files naming one. For Perplexity, this post finds a published five-stage pipeline, a documented source review, two crawlers with different robots.txt behaviour, and a set of citation studies that cannot be averaged.

What we sell on the back of all this is narrow and is described on the answer engine optimization page: we measure where a developer-tool company stands across the engines its buyers use, with a design that states its own detection floor, and we do the passage-level and community-level work that the pipelines above retrieve. We have no customers yet, so there is no case study here and there will not be one until there is a real, nameable engagement. What there is instead is the method, the numbers it produced, and the number that says it is not yet good enough. Those are on the measurement hub, and the pricing page says what the work costs without a guarantee attached, because a guarantee on a noisy instrument would be a lie.