Track GPTBot, ClaudeBot, and OAI-SearchBot with nginx
Add one nginx mirror block to record recognized AI crawler requests before WordPress, an application server, or a full-page cache answers them. Foglift groups each request by agent, purpose, page, and time in AI Traffic.
The generated configuration uses a public, hostname-bound workspace identifier. It forwards the path and user agent asynchronously, keeps query strings and request bodies out of the report, and leaves the original page request on its existing nginx path.
Step 1
Copy your generated nginx block
Open AI Traffic while signed in to copy this block with your workspace identifier filled in. The identifier is safe in server configuration and cannot read account data or act as an authenticated Foglift API key.
Place the generated map in the nginxhttp context. Merge the mirror directive and internal reporting location into the relevant server configuration.
Keep every existing proxy_pass, try_files, cache, TLS, and security directive.
Forward $uri, never $request_uri, so query strings remain excluded.
Do not remove the internal boundary on the reporting location.
Step 3
Validate, reload, and verify
Run nginx -t. Fix every reported error before continuing.
Reload nginx only after validation passes, using the command approved for your server or hosting environment.
Open AI Traffic and choose Verify install. Foglift sends a unique workspace-bound request and confirms when nginx mirrors it.
The crawler pattern list is frozen into the copied configuration. Re-copy the block whenFoglift adds patterns; the dated version comment shows which map is installed.
nginx AI crawler tracking is available on every plan
Free is enough to install the Sensor for one brand. Paid plans expand brand capacity and add five-engine AI Visibility monitoring plus developer access.
Plan
Price
Brands
AI Visibility
Free
$0/mo
1
Active-use weekly Perplexity monitoring
Launch
$49/mo
3
Five engines, up to daily
Growth
$129/mo
10
Five engines, up to twice daily
Enterprise
Custom
Custom
Five engines, up to hourly
nginx Sensor FAQ
What nginx records, and what a crawler request proves
How do I track GPTBot, ClaudeBot, and OAI-SearchBot with nginx?
Copy the Foglift mirror block into the nginx server configuration, keep the existing proxy and cache directives, run nginx -t, reload only after validation passes, and use Verify install in AI Traffic. The mirror reports recognized crawler requests with a public workspace identifier and does not require a secret API key.
What does the nginx Sensor record?
For a recognized AI agent, the nginx mirror sends the workspace identifier, original hostname, path, user agent, and event time. Foglift groups the request by agent, purpose, page, and time. The configuration forwards $uri instead of $request_uri, so query strings are not sent.
Does nginx mirroring delay the page response?
The nginx mirror module creates a background subrequest while the original request continues through the site's existing location behavior. The generated block disables request-body forwarding and sends only recognized crawler traffic to the reporting endpoint.
Does an AI crawler request prove that the page was cited?
No. A crawler request proves that a recognized agent reached the server at a recorded time. It does not prove indexing, citation, recommendation, model training, or a human visit. Prompt-level AI Visibility and recognized AI referrals are separate outcome evidence.
Can I track AI crawler requests at nginx for free?
Yes. Foglift Sensor and AI Crawler Analytics are available on the Free plan for one brand. Free also includes unlimited single-page Technical Audits and active-use weekly Perplexity monitoring. Launch starts at $49 per month and adds five-engine monitoring, API, CLI, MCP, and webhooks.
Tracked prompt
how do I track GPTBot, ClaudeBot, and OAI-SearchBot traffic
This guide owns the nginx installation answer. Use AI Crawler Analytics for the complete recognized-agent reporting contract and evidence boundaries.