Skip to content
GrowthVector.io

Perplexity SEO: How Perplexity Chooses Its Sources

Which Perplexity SEO decisions change your citations, and which ones only change your measurement?

Updated

Perplexity SEO comes down to three decisions: who may fetch your pages, which passages Perplexity can score, and how you measure the visits it sends.

Perplexity documents its crawlers and its search index, but its published material gives no weights for the citation step. Vendor studies disagree on how much referral traffic Perplexity sends, so read each figure with its sample and date.

Related guides: SEO guide for practitioners, GEO and AEO guide, platform citation behavior, GEO vs SEO, how to get cited by ChatGPT.

Perplexity SEO Starts With Crawl Access: What PerplexityBot and Perplexity-User Do

Decide the access rule for each Perplexity agent before you change robots.txt. The two agents follow different rules, so one Disallow line does not control both.

Two agents, two rules

AgentWhat Perplexity says it doesHow robots.txt applies, per Perplexity
PerplexityBotSurfaces and links sites in Perplexity search results. It is not used to crawl content for AI foundation models.Perplexity says PerplexityBot complies with explicit robots.txt limits.
Perplexity-UserVisits a page when a person asks a question, and may link to it in the answer. It is not used for crawling or training.Perplexity says it generally ignores robots.txt, because a user requested the fetch.

Perplexity recommends that you allow PerplexityBot in robots.txt and permit requests from its published IP ranges, so your site can appear in results.

A Disallow rule for PerplexityBot does not govern Perplexity-User. Perplexity says the user-triggered agent generally ignores robots.txt, so do not count on robots.txt to stop a fetch started by a question.

Robots.txt changes can take up to 24 hours to reach Perplexity. Each setting works independently. Test a rule change after that window, not right after you save it.

Perplexity publishes user agent strings with a version number: PerplexityBot/1.0 and Perplexity-User/1.0. Match on the agent name, not the full string, because the version can change.

Firewall rules need the right order, and the order decides whether an allow rule works. Perplexity says Cloudflare's Bot Fight Mode cannot be skipped with WAF custom rules. If that mode is on, an allow rule alone does not stop the challenge.

For AWS WAF, Perplexity's guide describes one IP set per bot, plus an Allow rule per bot that matches both the IP set and the User-Agent. Give those Allow rules lower priority numbers than your blocking rules, so the WAF evaluates them first.

Each bot publishes its own IP list as a JSON file. Match both the User-Agent and the IP address before you accept a hit.

Use the most current IP ranges from the official JSON endpoints. Lists that you saved last year may no longer match.

Allow PerplexityBot if you want to appear in Perplexity results. Treat Perplexity-User as a fetch that robots.txt generally does not stop. Before you change any access rule, run the crawl and indexing checks in the SEO guide for practitioners.

How Perplexity Retrieves and Ranks Sources, and What It Does Not Publish

Plan for passage-level selection, not only for page-level ranking. Perplexity says it retrieves and scores results at both the document and sub-document levels.

Perplexity's Search API post says its index splits documents into units that are scored one at a time against the query. The API then returns documents with their most relevant snippets already ranked.

Perplexity says its search index tracks over 200 billion unique URLs, with capacity for many hundreds of billions more.

Perplexity says it built its own index and crawler for completeness, freshness and speed, and for fine-grained content understanding. Its retrieval runs lexical and semantic queries together, then merges the results into one candidate set.

The ranking runs in stages. Perplexity says prefilters remove clearly non-responsive or stale content, and lexical and embedding scorers narrow the set. Cross-encoder rerankers make the final selection.

Perplexity says its indexer keeps documents from authoritative domains, documents on undercovered topics, and other categories with outsize potential to enrich the index. It gives no weights for that signal, so do not size your effort from it.

Perplexity says the internet is too large to index every URL on a frequent, recurring basis. A machine-learning model decides which URLs to index, and when, based on importance and likely update frequency.

Update frequency is one input the indexing model weighs, so plan updates for the pages you want revisited.

Perplexity says its parsing rules vary by site type. A site with well-structured lists or tables may get more formulaic extraction than a site with freeform writing. If a page is a list or a comparison, format it as one, so the extraction has clear units to read.

The published material covers the index and the retrieval stages. It gives no weights for which sources an answer cites. Treat any vendor's citation weights as opinion, because none of the Perplexity pages cited here gives one.

Perplexity's help center says each answer includes numbered citations that link to the original sources. Run your own queries and record which numbered links point to your pages.

Mode changes the source count. Perplexity says Deep Research runs many searches on its own and reads hundreds of sources. A single source count does not describe every answer.

For the tactics that apply across AI search, read the GEO and AEO guide. The GEO vs SEO page explains where that work differs from classic SEO.

Publisher Programs: Whether a Marketing Site Can Plan Around Them

Do not plan a traffic or payment gain from Perplexity's publisher programs. Both name publishers as their partners, so the work that helps a marketing site is crawl access, passage quality and measurement.

Perplexity launched its Publishers' Program on July 30, 2024. Its first partners were TIME, Der Spiegel, Fortune, Entrepreneur, The Texas Tribune and WordPress.com.

Perplexity says it pays a share when it earns revenue from an interaction where a publisher's content is referenced. Partners also get free access to its online LLM APIs and developer support.

Perplexity announced Comet Plus on August 25, 2025. It says the program pays publishers for three types of traffic: human visits, search citations and agent actions.

Perplexity says it distributes all revenue to participating publishers, minus a small portion for compute costs. Its post gives no percentage and no dollar figure.

Digiday reports, quoting Perplexity's head of publisher partnerships, that Perplexity keeps 20% of the pooled subscription revenue. The other 80% goes to publisher program participants. Digiday also reports a $42.5 million pool.

Digiday says Comet Plus pays for direct visits through Comet, for citations in answers on Comet, and for tasks that Comet's assistant completes. Those payments do not depend on citations in Perplexity.ai web answers alone.

Digiday quotes the same executive saying publishers could stand to make millions from the program. Neither Perplexity's post nor Digiday gives a payout total.

The named partners are news and media companies, plus WordPress.com. Neither program names a brand or a marketing site as a partner, so do not plan a traffic gain around one.

The Cloudflare Crawling Dispute: What Each Side Claims and How to Set Your Block Policy

Cloudflare's claims

Decide your block policy with both accounts in view. The dispute is not settled, and neither side has made its raw logs public.

Cloudflare published its stealth-crawling report on August 4, 2025. It says Perplexity starts from its declared user agent, but when blocked, Perplexity appears to obscure its crawling identity.

Cloudflare says that, after its declared crawler was blocked, Perplexity used a generic browser user agent that impersonates Chrome on macOS. It says the traffic rotated through IP addresses outside Perplexity's published range.

Cloudflare's table lists 20 to 25 million daily requests for declared Perplexity-User traffic. It lists 3 to 6 million daily requests for the stealth Chrome user agent, across tens of thousands of domains.

Cloudflare also ran a test on new domains that were not indexed. It set robots.txt to disallow all bots, and it added WAF rules that blocked PerplexityBot and Perplexity-User. Cloudflare says Perplexity still answered detailed questions about the content on those domains.

Cloudflare says a working block lowers answer quality. It observed that answers became less specific and lacked details from the original content.

Cloudflare used ChatGPT-User as a control. It says that agent read robots.txt and stopped when the file disallowed it.

Cloudflare removed Perplexity from its list of approved bots. It also added heuristics for the stealth crawler to its managed AI-crawler block rule, which is available to all customers, including free customers.

Perplexity's response

Perplexity replied on August 4, 2025. It says its user-driven agents do not store the information they retrieve, and do not train on it.

Perplexity says Cloudflare confused its traffic with 3 to 6 million daily requests from BrowserBase, a third-party cloud browser service. It says it uses BrowserBase only occasionally, for highly specialized tasks, at less than 45,000 daily requests.

Perplexity argues, citing Google's user-triggered fetchers, that user-driven agents act on a person's behalf. On that basis, it says robots.txt should not govern them.

Perplexity also says PerplexityBot complies with explicit robots.txt limits. Where a domain sets no limits, it says PerplexityBot follows industry-standard request-rate norms.

The two accounts disagree on one point: whether the 3 to 6 million daily requests came from Perplexity's own crawler. Cloudflare says they came from Perplexity. Perplexity says they came from BrowserBase, so public data cannot settle the question.

What a site owner can do now

  1. Set the rule for each agent. Perplexity says robots.txt governs PerplexityBot but generally not Perplexity-User, so the two need separate decisions.
  2. Filter your logs for the pattern Cloudflare describes: a Chrome user agent that arrives from IP addresses outside Perplexity's published lists.
  3. Test any block with a fixed list of questions about the blocked pages. Wait for the change to take effect, since Perplexity says robots.txt changes can take up to 24 hours, then run the same list again and compare.

Keep your logs. They record your own traffic, which no vendor study does.

What Perplexity Cites Most Often, and How Far to Trust Each Study

Read the study design before the figure

The studies below use different samples, periods and definitions. Their figures do not combine into one answer, so read each one with its design.

Ahrefs found that Perplexity is the outlier among the assistants it tested. Nearly 1 in 3 of its citations point to pages that rank in the top 10 for the target query.

The same study puts ChatGPT, Gemini and Copilot at an average of 12% of cited links in Google's top 10.

Ahrefs also states that Perplexity does not draw on Google's or Bing's index. It has its own search index, based on its crawler.

Ahrefs' Brand Radar, covering the US and all topics and updated September 2, 2026, puts Reddit first among the domains Perplexity cites, at 21.6% mention share. YouTube follows at 20.8%. Mention share is a domain's citations as a percentage of the summed citations of the top sources, not of all citations.

The ranking moves each month, so date any share you quote.

If your category's citations lean on those platforms, a presence on them is a channel decision, not a page edit.

Seer Interactive studied 7,683 dated pages cited across ChatGPT, Gemini and Perplexity, from March to June 2026. Of Perplexity's cited pages, 65% were updated within the last year, and 83% within two years.

Seer reads its data as showing that refreshing older pages is what earns recency. Its fresh-from-old share for Perplexity, meaning pages updated in the last year but first published two or more years ago, is 28%.

Seer covers four brands in four categories, so read these shares as one sample, not as a rule for every site.

A preprint on arXiv analyzed 602 controlled prompts across ChatGPT, Google AI Overview and Gemini, and Perplexity, with 21,143 valid citations. Its authors report that Perplexity and Google cite more sources per answer on average than ChatGPT does.

The same preprint finds that high-influence pages tend to be longer, more structured and richer in extractable evidence, such as definitions, numerical facts, comparisons and procedural steps. The preprint has not been peer reviewed.

A second arXiv study analyzed 158,099 answers and 468,037 citations from ChatGPT, Gemini and Perplexity, over two 90-day collections. Within one site, pages whose title and paragraphs match the questions people ask get cited more.

The same study finds that FAQ blocks, structured data, summary boxes and page speed appear effective only when compared across websites. It covers three engines together, so read its findings as cross-engine, not as Perplexity-only.

Qwairy measured 21.87 citations per question for Perplexity and 7.92 for ChatGPT, across 118,101 AI answers in Q3 2025. Use that count with its sample and period, and treat it as one measure of a single quarter.

For the cross-platform view, read the platform citation behavior page. For how the ChatGPT side differs, read how to get cited by ChatGPT.

Use each study's design to decide what to test. Then measure your own citations for your own questions, because no shared figure predicts your results.

How to Measure Perplexity SEO Referrals in GA4 and Server Logs

Measure two series separately: referral visits from Perplexity, and bot visits from its crawlers. Bot visits show crawl access. They do not show who clicked through.

Ahrefs separates crawl hits from human referral traffic. It says AI crawlers fetch and index pages, but they do not necessarily send human visitors.

Size the channel before you invest

Ahrefs' March 2026 tracker, across 74,752 websites, counted around 230,000 visitors from Perplexity and around the same from Gemini. ChatGPT sent 2.7 million.

SE Ranking's June 2026 study, across 101,574 websites with Google Analytics data, puts Perplexity at 7.23% of AI referral traffic. It puts ChatGPT at 74.78% and Gemini at 11.56%.

SE Ranking reports a share of AI referral traffic from sites with Google Analytics data, while Ahrefs counts visitors across 74,752 sites, so the two figures cannot be compared directly. Measure your own share before you set a budget.

Cloudflare Radar reports that Perplexity sent fewer referrals in 2025 while its crawling rose. It measured 194 crawls per visitor in July.

Read that ratio as crawl load against referral value. It does not show how many citations a page earns.

Find Perplexity visits in GA4

Google describes the AI Assistant channel as visits from sources such as ChatGPT, Gemini, Deepseek, Copilot or Grok. The description does not name Perplexity, and it excludes AI Overviews and AI Mode. Test where perplexity.ai visits land in your own property.

The AI Assistant rule keys on the referrer. Google sets the medium to ai-assistant when the referrer matches its list of AI assistants, so a visit with no referrer cannot be classed as AI Assistant.

A visit with no referrer lands in Direct, where the source is (direct) and the medium is (not set) or (none).

Ahrefs warns that AI chatbot traffic often shows up as direct traffic, or disappears into an unlabeled referral bucket, unless you set up specific tracking.

Default channel groups cannot be edited, but you can create custom channel groups with your own rules.

  1. Filter your referral report for perplexity.ai in the session source. Note the channel group that each visit lands in.
  2. If visits land in Direct, or in a group you do not want, build a custom channel group with a rule for perplexity.ai above the Referral channel.
  3. Run a click test from a page that Perplexity cites. Repeat it in a normal browser, in the Perplexity app and in Comet. Record the source and channel that GA4 shows for each.
  4. Ahrefs suggests a GA4 segment on a referral source that includes perplexity. The segment will not catch everything.

Whether Comet passes a referrer is not settled, so run the test in step 3 on your own property.

Check bot hits in server logs

Perplexity publishes a separate IP list for PerplexityBot and for Perplexity-User, as JSON files. Always use the current lists.

  1. Filter your server logs for the two user agent strings, PerplexityBot and Perplexity-User.
  2. For each hit, check the IP address against the JSON list for that same bot. Keep the hits that match both the agent and the IP.
  3. Count the rest as spoofed or unmatched traffic. Review those IP addresses before you block them.

Cloudflare says an undeclared crawler used IP addresses outside Perplexity's published range.

Perplexity says that traffic came from BrowserBase, a third-party cloud browser service.

Your own logs show whether this pattern appears on your site.

A test plan you can repeat

  1. Write a fixed list of questions that your buyers ask. Do not change the list between runs.
  2. Ask each question in Perplexity, and record which of your pages it cites, with the date.
  3. Record the GA4 referral clicks and the bot hits in your logs for the same days.
  4. Repeat the run after each change, with the same list, because the answers can change between runs.

Compare the runs, not one answer. A single answer shows little about your share of citations.

Common Questions

If I block PerplexityBot in robots.txt, can Perplexity still use my page?

Yes, in some cases. Perplexity says Perplexity-User, the agent that runs when a person asks a question, generally ignores robots.txt, so a PerplexityBot block does not govern it. Cloudflare reports that, in its test, Perplexity still answered detailed questions about domains that blocked both agents. Perplexity says the stealth traffic Cloudflare measured came from BrowserBase, not from its crawler. Cloudflare also observed that a working block made answers less specific. Decide the block by agent, and check your logs before you rely on either outcome.

Does ranking in Google's top 10 get a page cited by Perplexity?

Only partly. Ahrefs found that Perplexity is the outlier among the assistants it tested, with nearly 1 in 3 of its citations pointing to pages in the top 10 for the target query. Most citations therefore come from pages outside that group. Perplexity says it runs its own index and crawler, and that it scores documents and passages, so one clear section can earn a citation without a top 10 page. Track citations for your own queries, and do not assume the Google rank carries over.

How recent does a page need to be before Perplexity cites it?

Recency matters, but the sample sets the limit. Seer Interactive reports that 65% of Perplexity's cited pages were updated within the last year, and 83% within two years. Its fresh-from-old share, meaning pages updated in the last year but first published two or more years ago, is 28%. Seer covers four brands in four categories, so treat these shares as one sample, not a rule. Refresh the older pages that still matter, and show the updated date on them.

Why does my Perplexity traffic not appear in the GA4 AI Assistant channel?

Google's description of the AI Assistant channel names ChatGPT, Gemini, Deepseek, Copilot and Grok, and it does not name Perplexity. The channel rule keys on the referrer, so a visit with no referrer cannot count as AI Assistant and lands in Direct. Test where perplexity.ai visits land in your own property, using a click from a cited page in a normal browser, the Perplexity app and Comet. If the visits land in the wrong group, build a custom channel group with a rule above Referral.

How do I tell real PerplexityBot hits from spoofed ones in my server logs?

Match two fields for each hit: the user agent string and the IP address. Perplexity publishes a separate JSON list of IP ranges for PerplexityBot and for Perplexity-User, and it says to use the most current lists. Hits that fail the IP match are spoofed or come from another source, so keep them out of your crawl count. Cloudflare alleges that stealth traffic came from a crawler outside Perplexity's published ranges. Perplexity says that traffic came from BrowserBase, a third-party service it uses only occasionally.

Can a marketing site gain Perplexity visibility through the Publishers' Program or Comet Plus?

Probably not. Perplexity's launch post names news and media companies as its first Publishers' Program partners, and Digiday names publishers as participants in the program. Comet Plus pays publishers for human visits, search citations and agent actions. Digiday reports that Perplexity keeps 20% of pooled subscription revenue and sends 80% to participants, with a $42.5 million pool. Perplexity's own post gives no split. Spend your effort on crawl access, passage quality and measurement instead.

Next step

Start with the access rules for PerplexityBot and Perplexity-User. Then check where perplexity.ai visits land in GA4. For tracking after the click, read the conversion tracking page.