Perplexity SEO: How to Get Your Site Found and Cited by Perplexity, Plus a Script to Check Your robots.txt and Logs
Perplexity can only cite pages its own crawler is allowed to reach. Here is what Perplexity's documentation says about its two bots, the robots.txt and firewall settings that decide whether you show up, what we found when we checked 25 well-known sites, and a free script to check yours.
Perplexity SEO starts with access: Perplexity's crawler documentation says that to appear in its search results, a site should allow PerplexityBot in robots.txt and permit requests from its published IP ranges.
Perplexity runs two bots: PerplexityBot, which follows robots.txt and finds pages for its search results, and Perplexity-User, which fetches a page when someone asks a question and generally ignores robots.txt.
Perplexity says Cloudflare's Bot Fight Mode can still challenge its bots even when a custom firewall rule allows them, so a site can block Perplexity without touching robots.txt.
Of 24 well-known sites whose robots.txt we could read on Nov. 19, 2026, 11 blocked PerplexityBot from their homepage, including The New York Times, the BBC, Reddit, Amazon and Yelp; 13 allowed it.
Perplexity has not published how it ranks or picks the sources it cites, so after access is fixed, the useful work is writing pages that answer a question directly and can be quoted paragraph by paragraph.
Perplexity SEO is mostly about access: Perplexity answers questions by searching the web and citing the pages it used, and its own crawler documentation says that to appear in its results you must allow PerplexityBot in robots.txt and let its published IP addresses through your firewall. Many sites block it without meaning to, through a firewall or a bot-blocking setting rather than robots.txt. Once access is right, what is left is writing pages that are easy to quote.
This guide covers what Perplexity has published about its bots, the settings to check, what we found on 25 well-known sites, and a free script that checks your robots.txt and tells you whether a visit in your logs really came from Perplexity.
How does Perplexity find and cite pages?
Perplexity's help article How does Perplexity work? says it "searches the internet, gathering information from authoritative sources like articles, websites, and journals," then writes an answer in which "Each answer includes numbered citations linking to the original sources."
Two crawlers do the fetching, according to Perplexity's crawler page:
Visits a page when a user's question needs it, and may link to it in the answer. Not used for general crawling or training data, Perplexity says.
Generally no, because a person asked for the fetch
Each bot has its own list of IP addresses, published as JSON files. On Nov. 19, 2026, the PerplexityBot list had 21 entries, dated Nov. 18, and the Perplexity-User list had 10, dated Oct. 28. The lists change, so firewall rules should read them, not copy them once.
Perplexity has not published how it ranks or chooses which pages to cite. Lists of "Perplexity ranking factors" you will find online are guesses by SEO vendors.
Step 1: Allow PerplexityBot in robots.txt
If your robots.txt has no rule for PerplexityBot and your User-agent: * group doesn't block /, you are already allowed. To make it explicit, add:
User-agent: PerplexityBotAllow: /
Watch for two common mistakes:
A blanket block.User-agent: * with Disallow: /, followed by allow rules only for Googlebot and Bingbot, shuts out PerplexityBot and every other crawler you didn't name. Three of the sites in our test do this.
A named block copied from a template. Lists of "AI bots to block" often include PerplexityBot next to training crawlers. Perplexity says PerplexityBot is for search results, not model training, so blocking it removes you from Perplexity's results, not from training data.
Perplexity says changes can take up to 24 hours to reach its systems.
Step 2: Let Perplexity through your firewall and bot protection
This is the step most sites miss. Perplexity's advice for sites behind a web application firewall (WAF):
Allow both PerplexityBot and Perplexity-User, matching the user agent and the published IP ranges together, so impostors using the name are still blocked.
Put the allow rules above your blocking rules, since rules are evaluated in order.
Update the IP lists automatically from the JSON files.
Know that Cloudflare Bot Fight Mode cannot be bypassed by custom WAF rules, so it may still challenge Perplexity's bots even when you allow them.
If your site is on Cloudflare, look at Security settings for Bot Fight Mode and any AI crawler blocking before assuming robots.txt is the whole story. Our post on Cloudflare's AI agent settings explains what we chose for this site.
Step 3: Check your logs for the real PerplexityBot
Anyone can send a request that says "PerplexityBot" in the user agent. The only way to know a visit was really Perplexity is to check the IP address against its published lists. The script below does that, so you can confirm Perplexity is reaching your pages and that your firewall isn't turning it away.
Step 4: Write pages Perplexity can quote
Perplexity hasn't said what makes it pick one page over another, so this part is our view, built on what AI answers tend to quote and on how we write this site:
Answer the question in the first two sentences of the page or section, in plain words.
Use question-style subheads, each answered right below it, so a single section can be cited on its own.
Give specific facts with dates and sources, and say how you measured any number.
Show a visible "updated" date when you revise a page, so a fresh fetch has a reason to replace an old copy.
Clicks from Perplexity answers usually arrive in Google Analytics 4 as referral traffic from perplexity.ai. Our guide Does Google Analytics show ChatGPT traffic? shows how to find them and set up an AI traffic channel that groups Perplexity with ChatGPT, Gemini and Copilot.
Who blocks Perplexity? We checked 25 sites
On Nov. 19, 2026, we ran the script below on 25 well-known sites: news publishers, reference and review sites, stores and SEO tools. It reads each robots.txt and asks whether PerplexityBot and Perplexity-User may fetch the homepage, using the matching rules in RFC 9309 (the most specific user-agent group wins, then the longest matching path). Search Engine Land returned an error to our request, so 24 sites were checked.
Eight sites block PerplexityBot by name. Reuters, The Wall Street Journal and Reddit don't name it at all; their User-agent: * group disallows the whole site, so any crawler without its own allow rules is shut out.
Three block the crawler but not the fetcher. The Guardian, The Washington Post and Forbes name PerplexityBot but have no rule for Perplexity-User. Since Perplexity says Perplexity-User generally ignores robots.txt anyway, a rule for it is more a statement than a barrier.
Tripadvisor allows PerplexityBot with limits: it has its own PerplexityBot group that blocks forum pages but leaves the homepage open.
SEO tools and health publishers leave it open. None of the SEO tool sites in our list blocks Perplexity.
robots.txt is only half the picture: a site can allow PerplexityBot there and still block it at the firewall, which our test can't see from outside.
Does Perplexity respect robots.txt?
PerplexityBot does, according to Perplexity's documentation. Perplexity-User generally does not, because it fetches a page only when a person asks a question that needs it. If you want to keep Perplexity out entirely, robots.txt alone won't do it; you would need a firewall rule.
A script to check robots.txt and verify Perplexity IPs
This Node.js script (version 18 or later, no packages) has two modes. robots checks whether each bot may fetch a site's homepage; ip checks addresses from your server logs against Perplexity's published lists.
// perplexity-check.mjs// node perplexity-check.mjs robots example.com another.com// node perplexity-check.mjs ip 18.97.9.96 203.0.113.7const UA = 'Mozilla/5.0 (compatible; PerplexityCheck/1.0)';const get = (u) => fetch(u, { headers: { 'user-agent': UA }, signal: AbortSignal.timeout(20000) });// RFC 9309: the most specific user-agent group wins (else '*'),// then the longest matching rule, with Allow winning a tie.function verdict(robots, agent, path = '/') { const groups = []; let cur = null, lastWasUA = false; for (let line of robots.split(/\r?\n/)) { line = line.replace(/#.*/, '').trim(); const m = line.match(/^([a-z-]+)\s*:\s*(.*)$/i); if (!m) continue; const key = m[1].toLowerCase(), val = m[2].trim(); if (key === 'user-agent') { if (!lastWasUA) { cur = { agents: [], rules: [] }; groups.push(cur); } cur.agents.push(val.toLowerCase()); lastWasUA = true; } else { lastWasUA = false; if (cur && (key === 'allow' || key === 'disallow')) cur.rules.push({ allow: key === 'allow', path: val }); } } const a = agent.toLowerCase(); let group = groups.filter((g) => g.agents.some((x) => x !== '*' && a.startsWith(x))); const matched = group.length ? 'own group' : 'falls back to *'; if (!group.length) group = groups.filter((g) => g.agents.includes('*')); const rules = group.flatMap((g) => g.rules).filter((r) => r.path !== ''); const toRe = (p) => new RegExp('^' + p.replace(/[.+?^${}()|[\]\\]/g, '\\$&').replace(/\*/g, '.*').replace(/\\\$$/, '$')); let best = null; for (const r of rules) { if (!toRe(r.path).test(path)) continue; if (!best || r.path.length > best.path.length || (r.path.length === best.path.length && r.allow)) best = r; } return { allowed: best ? best.allow : true, matched, rule: best ? `${best.allow ? 'Allow' : 'Disallow'}: ${best.path}` : 'no rule' };}const ipToInt = (ip) => ip.split('.').reduce((n, o) => (n << 8) + Number(o), 0) >>> 0;const inCidr = (ip, cidr) => { const [base, bits] = cidr.split('/'); const mask = bits === '0' ? 0 : (~0 << (32 - Number(bits))) >>> 0; return (ipToInt(ip) & mask) === (ipToInt(base) & mask);};const [mode, ...args] = process.argv.slice(2);if (mode === 'robots') { for (const site of args) { try { const r = await get(`https://${site}/robots.txt`); const text = r.ok ? await r.text() : ''; for (const agent of ['PerplexityBot', 'Perplexity-User']) { const v = verdict(text, agent); console.log([site, r.status, agent, v.allowed ? 'allowed' : 'BLOCKED', v.matched, v.rule].join('\t')); } } catch (e) { console.log([site, 'error', e.cause?.code || e.name].join('\t')); } }} else if (mode === 'ip') { const lists = {}; for (const name of ['perplexitybot', 'perplexity-user']) { const j = await (await get(`https://www.perplexity.ai/${name}.json`)).json(); lists[name] = j.prefixes.map((p) => p.ipv4Prefix).filter(Boolean); } for (const ip of args) { const hit = Object.entries(lists).find(([, cidrs]) => cidrs.some((c) => inCidr(ip, c))); console.log(`${ip}\t${hit ? 'real ' + hit[0] : 'NOT a published Perplexity IP'}`); }} else { console.log('Usage: node perplexity-check.mjs robots <site...> | ip <address...>');}
We tested the ip mode on Nov. 19 with one address from each published list and with Google's public DNS address, 8.8.8.8: the first two came back as real PerplexityBot and Perplexity-User, and 8.8.8.8 as not a Perplexity address. The script checks IPv4 only, which is all the two lists contained that day.
What we don't know
How Perplexity ranks sources. It hasn't said, and we haven't tested it.
Whether a firewall blocks Perplexity on a given site. That only shows in the site's own logs, which is what the ip mode is for.
How quickly a newly allowed page gets cited. Perplexity gives 24 hours for settings to take effect, not a time for pages to appear in answers.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.