robots.txt allows, and shows how the crawlers spent their requests.
Open it from the Analysis group in the menu: Technical Analysis.
How the audit works
The audit checks the pages that the last crawl stored. It also reads yourrobots.txt, your sitemap and your llms.txt, and it renders a sample of pages. The checks are in three areas:
- Crawlability: can a crawler reach your pages?
- Renderability: does a crawler see the content without JavaScript?
- Parseability: can a crawler understand the content?
Run an audit
1
Open the page
Open Technical Analysis.
2
Start the audit
Click Run audit. The button shows Auditing… while the audit runs.
3
Read the score
When the audit is done, the score and the issue list appear.
Health score
The gauge shows a score from 0 to 100:
Each check has a weight. A failed check lowers the score by its weight and by the share of pages that fail it. Below the gauge, you see the number of critical, medium and low issues, and the number of pages examined and rendered.
When a check cannot run, it is not part of the score. A note below the issue list gives the number of these checks.
Issue list
The Issue list shows each issue, with the most severe first. Each row has a title, a description with the affected pages, and one of these:- Fix: opens the tool that fixes the issue.
- manual: no tool fixes this issue. Fix it on your site.
The checks
In the titles, N is the number of affected pages and GPTBot is an example of a crawler name.Bot Access Status
This panel shows each AI crawler that Perquery watches and what yourrobots.txt says about it:
Crawl Budget
This panel shows what each AI crawler requested from your site in a recent period. The panel title gives the number of days. It needs the access logs of your web server.
When you have not uploaded logs, the panel shows No bot logs uploaded yet. Click Upload bot logs to go to LLM bot logs.
Related pages
LLM bot logs
See the real AI crawler traffic on your site.
Growth opportunities
See technical issues as ranked actions.

