How to Show Up in Perplexity Answers (2026)
We rank PerplexityBot access first, then a citation tracker. Perplexity-User is a live fetch that generally ignores robots.txt. Schema is not the lever.
Perplexity publishes crawler rules. We rank tools after you follow them. Official page: Perplexity crawlers. Showing up means a numbered source you control, not a brand name in passing.
Rank 0: their bots
PerplexityBot: search surfacing, not foundation-model crawl, allow in robots.txt, IPs at perplexitybot.json, up to 24 hours. Full UA includes PerplexityBot/1.0.
Perplexity-User: user-triggered fetch so an answer can include a link. Generally ignores robots.txt. IPs at perplexity-user.json. Auth hides drafts. Disallow does not.
WAF: user-agent plus IP, Cloudflare and AWS examples in their docs. Custom rule: UA contains PerplexityBot or Perplexity-User, and source IP is in the JSON ranges, action Allow. Refresh the JSON. They say it is the source of truth and it changes. Fail the ranking if you only edited robots.txt and never opened the firewall.
Rank 1: software that stores the citation
Promptwatch first in our list: Perplexity on paid UI monitoring, page-level citations, and visitor analytics for referred sessions on Essential at $95/mo. PerplexityBot appears in Agent Analytics on Professional at $245/mo or an agency plan. Explore skips Perplexity (ChatGPT only). Daily paid checks. Not instant alerts.
Otterly.AI: Perplexity in the $29 base four. Thermometer. Possible week lag. No crawler-log product on our listing. Profound Starter: ChatGPT-only. Wrong engine. Peec AI last.
Rank 2: a page that is not a clone
Public HTML. Unique facts. Google's generative guide is optional reading, not Perplexity policy. llms.txt is not on Perplexity's crawler page as a requirement. There is no submit console.
22M+ monthly active users is the scale we cite from the Promptwatch sheet. Smaller than ChatGPT (820M+ weekly on the same sheet). Still worth a row in a ranking if buyers use it. Explore will not answer this title. Essential is the first Perplexity desk.
Freeze the purchase questions, including vs-queries. Run them for two weeks. Record the cited host. Named-only is a different KPI. On Professional or an agency plan, stop the writer if Bot never 200s. Wait the 24 hours Perplexity documents after a robots.txt change before you call the allow-list a failure.
A WAF that matches the UA string but not the JSON IPs will still 403. Their Cloudflare sketch is Security, WAF, custom rules, UA contains PerplexityBot or Perplexity-User, and IP is in the published ranges, action Allow. AWS is IP sets plus string matches, higher priority than block rules. Fetch the JSON on a schedule. Do not paste CIDRs from a Slack screenshot.
Visitor analytics (script or GTM) can catch a referred session. That is not a numbered citation. Report both. Do not average them. If Reddit is the numbered source, that is an offsite ticket. If /blog/2019 is the source, fix that URL.
Search Console will not tell you if Perplexity numbered you. Overviews are Google. Keep those reports in a different column. PerplexityBot's full UA includes PerplexityBot/1.0 and a docs link. User's UA includes Perplexity-User/1.0. Match both at the WAF with the matching JSON. They say WAF changes take time. On Professional or an agency plan, watch logs before you rewrite.
Show up = stored Perplexity answer with your URL after a Bot 200. That is the ranking. Everything else is commentary. Content Agents stay closed on a 403. WordPress publishing is not live. Visitor analytics is referral, not the numbered source. Product: promptwatch.com.