AISeeWhy
SV
Starta gratis prov

Varför syns inte min webbplats i Perplexity?

Publicerad

Kort svar

Perplexity kan bara visa och länka sidor som PerplexityBot får genomsöka och faktiskt får svar från. De vanligaste orsakerna är en robots.txt-regel som nekar PerplexityBot, en brandvägg eller ett CDN som svarar den med en 403 eller en utmaningssida, och text som först visas när JavaScript körs. Kontrollera alla tre och tillåt sedan Perplexitys publicerade IP-intervall.

Du frågar Perplexity om din produkt, och den citerar en konkurrent, en granskningssajt eller en forumtråd men aldrig dina egna sidor. Ibland handlar det om relevans. Oftare är det ett tekniskt block som du kan hitta på några minuter. Perplexity dokumenterar vilka agenter den använder, vad var och en gör och varifrån trafiken kommer, så varje länk i kedjan går att kontrollera: robots.txt, svaret som din server skickar och innehållet i det svaret.

På den här sidan
  1. How does Perplexity find and read pages?
  2. Is your robots.txt blocking PerplexityBot?
  3. Is your firewall or CDN blocking Perplexity?
  4. How do I allow Perplexity by its published IP ranges?
  5. Can JavaScript rendering keep Perplexity from reading a page?
  6. What if everything is open and my site still does not appear?

How does Perplexity find and read pages?

Perplexity documents two agents. They have different jobs, and a problem with either one can keep your page out of an answer.

In practice, PerplexityBot decides whether Perplexity knows about your pages before anyone asks, and Perplexity-User decides whether it can open a page live when a question needs it. If you want to be cited, both should get the same page a browser gets.

Is your robots.txt blocking PerplexityBot?

Open https://yourdomain.com/robots.txt and look for a group that names PerplexityBot. If there is none, the crawler follows the User-agent: * group. Under RFC 9309, matching is case-insensitive, and a named group replaces the * group completely rather than adding to it.

This block is common. In our study of the robots.txt files of the 1,000 most popular domains, 86 of the 518 sites that served a robots.txt (16.6%) disallowed the home page for PerplexityBot. That was the highest share of any AI search crawler we tested; OAI-SearchBot was blocked on 58 sites (11.2%). Some of these sites may have meant to stop AI training, but Perplexity says PerplexityBot is not a training crawler, so blocking it costs search visibility without serving that goal.

A setup that lets Perplexity in and keeps a private area closed looks like this:

User-agent: PerplexityBot
Allow: /
Disallow: /account/

User-agent: *
Allow: /
Disallow: /account/

Sitemap: https://example.com/sitemap.xml

Also check that the file itself answers correctly. If robots.txt returns a server error, RFC 9309 says a crawler must assume the whole site is disallowed. A robots.txt address that returns an HTML page with status 200 contains no valid rules. Perplexity says changes can take up to 24 hours to be reflected.

Is your firewall or CDN blocking Perplexity?

robots.txt is a request, not access control. Your firewall, CDN or bot protection decides what is actually sent back, and it can answer Perplexity with a 403, a 429 or a challenge page while your own browser visits look normal. Perplexity's documentation says that sites behind a web application firewall may need to explicitly allow its bots.

Test it by requesting the same URL as a browser and as each Perplexity agent, then compare the status and size:

for UA in "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" \
          "Mozilla/5.0 (compatible; PerplexityBot/1.0; +https://perplexity.ai/perplexitybot)" \
          "Mozilla/5.0 (compatible; Perplexity-User/1.0; +https://perplexity.ai/perplexity-user)"; do
  curl -s -o /dev/null -w "%{http_code} %{size_download}\n" -A "$UA" https://example.com/page
done

A 403, 429 or 503 for the Perplexity agents only, a page titled Just a moment..., or a 200 response that is much smaller than the browser's all point to the firewall. This test comes from your IP address, not Perplexity's, so it shows how your rules treat the user agent; IP-based rules can still differ for the real crawler.

If you use Cloudflare, note two things. Perplexity's documentation repeats Cloudflare's own statement that Bot Fight Mode cannot be skipped with WAF custom rules, so if that feature challenges Perplexity, an allow rule will not help. And in August 2025 Cloudflare said it had removed Perplexity from its verified bots list after observing what it described as undeclared crawling; Perplexity disputed that account. Rules that let through only verified bots may therefore not cover Perplexity. Check the current status in your dashboard rather than assuming.

How do I allow Perplexity by its published IP ranges?

Anyone can send a request that claims to be PerplexityBot, so an allow rule that matches only the user agent also admits imitators. Perplexity publishes the address ranges of both agents and recommends matching the user agent and the IP address together:

curl -s https://www.perplexity.ai/perplexitybot.json | jq -r '.prefixes[] | .ipv4Prefix // .ipv6Prefix'
curl -s https://www.perplexity.ai/perplexity-user.json | jq -r '.prefixes[] | .ipv4Prefix // .ipv6Prefix'

Perplexity says these lists are updated regularly and suggests automating updates to your WAF rules. Place the allow rule above any rule that blocks or challenges requests: first in Cloudflare's custom rules, or with a lower priority number in AWS WAF. Then watch your logs, because firewall changes can take time to propagate.

Can JavaScript rendering keep Perplexity from reading a page?

It can. Perplexity's crawler documentation does not say whether its agents execute JavaScript, so the safe assumption is that the text a crawler needs should be in the HTML the server sends. Pages built entirely in the browser, such as single-page apps without server rendering, can arrive as an empty shell with a loading spinner.

A quick check is to fetch the page with curl and search the output for a sentence from your main content. If it is not there, the text is added by scripts. Server-side rendering, static generation or prerendering for crawlers fixes this for every AI crawler at once, not only Perplexity.

What if everything is open and my site still does not appear?

Being readable is a precondition, not a guarantee. Perplexity does not publish how it chooses which sources to cite, so a page that every agent can read may still lose to pages that answer the question more directly. What you can control is that nothing technical stands in the way: a clear page title, the answer stated early in the text, and accurate facts that match what you say elsewhere.

Also remember what robots.txt does not cover. Perplexity says Perplexity-User generally ignores robots.txt because a user requested the fetch. A rule for Perplexity-User is therefore not a reliable way to block live visits, and a robots.txt that allows it is not proof that it gets through your firewall.

AISeeWhy requests your page as PerplexityBot, Perplexity-User and 12 other crawlers next to a browser, applies your robots.txt rules for each, recognises challenge pages and shows how much of the text arrives without JavaScript, so you can see which link in the chain fails.

Vanliga frågor

Does Perplexity train its models on my content?

Perplexity says PerplexityBot is not used to crawl content for AI foundation models and that Perplexity-User does not collect content for training. Disallowing PerplexityBot therefore does not serve as a training opt-out; it only reduces your visibility in Perplexity's search results.

How long after I fix robots.txt will Perplexity notice?

Perplexity says it may take up to 24 hours for its systems to reflect robots.txt changes. Firewall changes take effect when your provider applies them, but give the crawler time to return before judging the result.

Can I block Perplexity-User with robots.txt?

Not reliably. Perplexity says the fetcher generally ignores robots.txt because a user requested the fetch. If you need to stop it, a firewall rule matched to its published IP ranges is the dependable control.

Is a user agent check enough to identify Perplexity traffic?

No. User agents are easy to copy. Compare the source IP with the ranges Perplexity publishes in perplexitybot.json and perplexity-user.json, and match both the user agent and the IP in firewall rules.

Källor

Fler artiklar