Crawler Logs

Crawler Logs shows you when AI crawlers from ChatGPT, Perplexity, Claude, Google, and others visit your website, and which pages they read. It turns raw bot traffic into a clear view of which pages AI systems fetch, and when.

Accessing Crawler Logs

Go to AI Search → Crawler Logs in the sidebar.

What Crawler Logs Shows You

AI-powered search is changing how people discover content. Crawler Logs helps you understand:

Which AI bots are crawling your site - GPTBot, ClaudeBot, PerplexityBot, and others
Live retrieval traffic - when ChatGPT or Perplexity fetch a page in real time to answer a question
Which pages AI search engines read - what content AI finds valuable
Fetch patterns - which pages AI systems fetch, and when

Different AI tools behave differently. ChatGPT fetches pages in real time when answering queries, while Perplexity often uses pre-indexed content from background crawls. Crawler logs show fetches, not citations: to see where AI answers cite you, use Citations.

Setup

Choose your platform to get started:

WordPress

If your site is connected through the WordPress integration, Asky can import your server logs once a day through that connection. No extra credentials or code are needed. The WordPress connection is available on Scale and above.

Daily log imports work on supported hosts. SiteGround is supported, including requests served from its cache. Asky checks whether your host is compatible before it turns anything on.

Connect WordPress

Connect your self-hosted site in Connections. When you connect, Asky checks whether your host’s logs are readable and turns on daily imports if they are.

Check the WordPress tab

Go to AI Search → Crawler Logs, click Setup Instructions, and open the WordPress tab. It shows whether daily tracking is active. If it is not on yet, click Enable now.

Wait for the first import

Asky imports up to 30 days of available history, newest first, and visits appear as they are imported. After that, new server logs are imported automatically each day.

Because the logs arrive once a day, WordPress imports are not live: a visit shows up after the host publishes that day’s log. For visits within seconds, use the Cloudflare Worker or a custom server integration.

To stop importing, click Disable daily logs on the same tab. Visits already imported stay in Asky.

Cloudflare

Cloudflare Worker

Use a Cloudflare Worker to intercept requests and send visit data to Asky.

This requires a Cloudflare account with Workers enabled. The free tier includes 100,000 requests/day which is sufficient for most sites.

Get Your Domain ID

Log in to your Asky dashboard
Go to AI Search → Crawler Logs in the sidebar
Click Setup Instructions
Copy your Domain ID (a UUID like 1d44d1d2-7396-4721-949d-8817c8e50265)

Create a Cloudflare Worker

Log in to your Cloudflare Dashboard
Select your website
Go to Workers Routes in the sidebar (under Workers & Pages)
Click Create Route or Manage Workers
Create a new Worker

Add the Worker Code

Paste the following code into your Worker, replacing YOUR_DOMAIN_ID with your actual Domain ID:


export default {
  async fetch(req, env, ctx) {
    const url = new URL(req.url);
 
    // Skip static assets - they don't need tracking
    if (url.pathname.match(/\.(png|jpg|jpeg|gif|svg|css|js|ico|woff2?|ttf|map)$/i)) {
      return fetch(req);
    }
 
    // Build the log payload
    const log = {
      ua: req.headers.get("user-agent") || "Unknown",
      referrer: req.headers.get("referer") || null,
      host: url.hostname,  // Required for security validation
      path: url.pathname,
      query: url.search || null,
      ip: req.headers.get("cf-connecting-ip") || null,
      ts: Date.now()
    };
 
    // Send to Asky asynchronously (non-blocking)
    ctx.waitUntil(
      fetch("https://zmmfehojjrqgcfapzgqy.supabase.co/functions/v1/collect", {
        method: "POST",
        headers: { "Content-Type": "application/json" },
        body: JSON.stringify({
          domain_id: "YOUR_DOMAIN_ID", // Replace with your Domain ID
          ...log
        })
      }).catch((err) => console.error("Error sending log:", err))
    );
 
    // Continue serving the original request
    return fetch(req);
  }
};

The host field is required for security validation. Asky verifies that the hostname matches the domain registered with your Domain ID, preventing data pollution from unauthorized sources.

Configure the Worker Route

Go to Workers Routes for your domain
Add a route pattern: *yourdomain.com/* (replace with your actual domain)
Select your newly created Worker
Click Save

Make sure to replace yourdomain.com with your actual domain. You may want to exclude certain subdomains like www. if they redirect to your main domain.

Verify Installation

Crawler Logs only shows bot traffic, not regular human visits. To test your setup:

Go to ChatGPT and ask a question about your site (e.g., “What does [yoursite.com] offer?”)
Check your Asky dashboard → AI Search → Crawler Logs
You should see visits from OpenAI bots appear within seconds

You may see different OpenAI bots depending on how ChatGPT processes your query:

ChatGPT Citations (OpenAI) - live fetch when ChatGPT references your content
OAI-SearchBot (OpenAI) - search indexing
GPTBot (OpenAI) - training data crawler

If no visits appear, try asking about specific content on your pages. You can also use a browser extension to set your User-Agent to GPTBot/1.1 and visit your site directly.

Excluding Subdomains

If you have multiple subdomains and only want to track some of them:


// Skip specific subdomains
if (url.hostname === "www.yourdomain.com") {
  return fetch(req);
}
 
if (url.hostname === "api.yourdomain.com") {
  return fetch(req);
}

Excluding Additional Paths

To skip tracking on certain paths (e.g., admin areas):


// Skip admin and API routes
if (url.pathname.startsWith("/admin") || url.pathname.startsWith("/api/")) {
  return fetch(req);
}

Custom Server

Custom Server Integration

For custom servers (Node.js, Python, Go, etc.), send logs directly to the Asky API.

API Endpoint


POST https://zmmfehojjrqgcfapzgqy.supabase.co/functions/v1/collect
Content-Type: application/json

Request Body


{
  "domain_id": "your-domain-uuid",
  "host": "yourdomain.com",
  "ua": "Mozilla/5.0 ... GPTBot/1.0",
  "path": "/page-path",
  "query": "?param=value",
  "referrer": "https://google.com",
  "ip": "1.2.3.4",
  "ts": 1704067200000
}

Required Fields

Field	Type	Description
`domain_id`	string	Your Domain ID from the Asky dashboard
`host`	string	The hostname of the request (for validation)
`ua`	string	User-Agent header
`path`	string	Request path

Optional Fields

Field	Type	Description
`query`	string	Query string
`referrer`	string	Referer header
`ip`	string	Client IP address
`ts`	number	Timestamp in milliseconds

Node.js Example


// Express middleware
app.use(async (req, res, next) => {
  // Don't block the request
  fetch("https://zmmfehojjrqgcfapzgqy.supabase.co/functions/v1/collect", {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({
      domain_id: process.env.ASKY_DOMAIN_ID,
      host: req.hostname,
      ua: req.headers["user-agent"],
      path: req.path,
      query: req.url.includes("?") ? req.url.split("?")[1] : null,
      referrer: req.headers["referer"],
      ip: req.ip,
      ts: Date.now()
    })
  }).catch(console.error);
 
  next();
});

Python Example


import requests
import threading
from flask import request
 
def log_to_asky():
    def send():
        requests.post(
            "https://zmmfehojjrqgcfapzgqy.supabase.co/functions/v1/collect",
            json={
                "domain_id": os.environ["ASKY_DOMAIN_ID"],
                "host": request.host,
                "ua": request.headers.get("User-Agent"),
                "path": request.path,
                "query": request.query_string.decode(),
                "referrer": request.headers.get("Referer"),
                "ip": request.remote_addr,
                "ts": int(time.time() * 1000)
            }
        )
    # Non-blocking
    threading.Thread(target=send).start()
 
@app.before_request
def before_request():
    log_to_asky()

Always send logs asynchronously to avoid adding latency to your responses.

Detected Bots

Asky automatically detects and categorizes the following AI crawlers:

Bot	Displayed As	Company	Type
GPTBot	GPTBot (OpenAI)	OpenAI	Training crawler
ChatGPT-User	ChatGPT Citations (OpenAI)	OpenAI	Live retrieval
OAI-SearchBot	OAI-SearchBot (OpenAI)	OpenAI	Search indexing
ClaudeBot	ClaudeBot (Anthropic)	Anthropic	Training crawler
Claude-User	Claude Citations (Anthropic)	Anthropic	Live retrieval
PerplexityBot	PerplexityBot (Perplexity)	Perplexity	Crawler
Perplexity-User	Perplexity Citations (Perplexity)	Perplexity	Live retrieval
Googlebot	Googlebot (Google)	Google	Search crawler
Bingbot	Bingbot (Microsoft)	Microsoft	Search crawler

Some Google tokens, like Google-Extended (the Gemini-training opt-out) and Googlebot-News, are robots.txt control tokens only. They have no distinct HTTP user-agent, so they govern crawling preferences but never appear as visits in Crawler Logs. For Google you’ll typically see Googlebot (and, when they crawl, variants such as Googlebot-Image, GoogleOther, and Google-CloudVertexBot).

Troubleshooting

No Data Appearing

Check your Domain ID - verify you are using the correct UUID from your Asky dashboard
Check logs - look for errors in your platform’s logs (Cloudflare Workers, Vercel, etc.)
Wait a moment - data may take a few seconds to appear

403 Domain Mismatch Error

If you see 403 errors, the host field does not match the domain registered with your Domain ID.

Ensure host is included in your log payload
Check your domain registration - the hostname must exactly match (e.g., example.com vs www.example.com)
Handle www variants - normalize the hostname: host.replace(/^www\./, '')

High Request Volume

The tracking runs on every request. To reduce volume:

Add more static file extensions to the skip list
Skip paths that do not need tracking (like /api/*)
Consider only tracking specific paths you care about

Next Steps

See which of your pages AI crawlers visit in Pages
Read the answers those crawls help inform in Responses

Need help setting up crawler tracking? Reach out at hello@askylabs.com.

Crawler Logs

Accessing Crawler Logs

What Crawler Logs Shows You

Setup

WordPress

WordPress

Connect WordPress

Check the WordPress tab

Wait for the first import

Cloudflare

Cloudflare Worker

Get Your Domain ID

Create a Cloudflare Worker

Add the Worker Code

Configure the Worker Route

Verify Installation

Excluding Subdomains

Excluding Additional Paths

Vercel

Vercel Edge Middleware

Netlify

Netlify Edge Functions

Custom Server

Custom Server Integration

API Endpoint

Request Body

Required Fields

Optional Fields

Node.js Example

Python Example

Detected Bots

Troubleshooting

No Data Appearing

403 Domain Mismatch Error

High Request Volume

Next Steps