PerplexitySearch indexingFirst seen Aug 25Last seen Aug 3129 hits4 × 404
Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko); compatible; PerplexityBot/1.0; +https://perplexity.ai/perplexitybot
Identity is claimed by this user-agent and is not verified.
crawled for search/llms.txt40417h ago
crawled for search/changelog1d ago
crawled for search/pricing1d ago
crawled for search/sitemap.xml1d ago
crawled for search/1d ago
crawled for search/robots.txt1d ago
crawled for search/robots.txt1d ago
crawled for search/api-reference4041d ago
crawled for search/robots.txt2d ago
crawled for search/robots.txt2d ago
crawled for search/robots.txt2d ago
crawled for search/2d ago
crawled for search/robots.txt2d ago
crawled for search/robots.txt3d ago
crawled for search/robots.txt3d ago
crawled for search/.netrc3d ago
crawled for search/robots.txt3d ago
crawled for search/robots.txt4d ago
crawled for search/pricing4d ago
crawled for search/.env.production.local4d ago
crawled for search/sitemap.xml4d ago
crawled for search/.env.production.local6d ago
crawled for search/llms.txt4046d ago
crawled for search/robots.txt6d ago
crawled for search/llms.txt4046d ago
crawled for search/robots.txt6d ago
crawled for search/robots.txt6d ago
crawled for search/robots.txt6d ago
crawled for search/6d ago
Crawler activity is recorded server-side and ignores the dashboard’s filters — a bot has no visitor, session or device. Rows marked as answering someone are pages an assistant fetched while replying: the question itself never reaches your server, so nobody can see what was asked, only which page was read.