Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.searchable.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What this does

Netlify’s HTTP Log Drain streams every inbound request log entry to a destination of your choosing. We point that drain at Searchable’s ingest endpoint, classify the AI bots, and drop everything else.
No code changes. All configuration is done inside the Netlify dashboard.
Enterprise plan only. HTTP Log Drains are a Netlify Enterprise feature. If you’re on a Free, Pro, or Business plan, use the Edge Function path instead — it works on all plans.

​
Prerequisites

A Netlify team on the Enterprise plan
Team Owner access in Netlify (Log Drain settings are team-level)
A Searchable project with your domain confirmed

​
Setup

1

Generate an integration token in Searchable

  1. Open your Searchable dashboard
  2. Go to Agent Analytics → Setup
  3. Pick Netlify Log Drain as your crawler source
  4. Click Generate token
Copy the token now — it starts with sa_… and won’t be shown again. You can always generate a new one if you lose it.
2

Open Netlify's Log Drain settings

Navigate to your Netlify team:Team settings → Log drains → Add log drainThis setting is team-level, not site-level. You need Team Owner access to see it.
3

Configure the drain

Fill in these fields:
FieldValue
ServiceHTTPS endpoint
Endpoint URLhttps://searchable-tracker.searchable.workers.dev/v1/netlify-logs
FormatJSON (Netlify delivers NDJSON over HTTPS)
Custom header nameAuthorization
Custom header valueBearer <your-sa_-token>
The custom header value must be Bearer followed by the full sa_… token, with one space and no quotes. The header name must be exactly Authorization.
4

Save and verify

Click Save. Netlify sends a verification ping to the endpoint — Searchable accepts it.Then return to Agent Analytics → Setup in Searchable. The Netlify Log Drain card should show Connected within a few minutes once an AI bot hits your site.

​
Verifying the connection

In Searchable:
  1. Go to Agent Analytics → Setup
  2. Look at the Netlify Log Drain card status
  3. Click Check if it still shows “Waiting for first event”
StatusWhat it means
Waiting for first eventThe drain is configured but no AI bot has hit your site yet. Typical wait is a few hours for sites that are already indexed.
ConnectedEvents are arriving. The card shows the count from the last 24 hours.

​
Troubleshooting

The Authorization header is missing or wrong.
  • Make sure you added a custom header named exactly Authorization
  • The value must be Bearer followed by the full sa_… token, with one space and no quotes
  • If you’ve recently revoked the token in Searchable, generate a new one and update the drain
Check the drain format setting.
  • The format must be set to JSON (which delivers NDJSON over HTTPS) — not Datadog, Splunk, or any other structured format
  • If the format was wrong, update it and save — Netlify will retry pending deliveries
Log Drains are only visible to Team Owners on the Enterprise plan. If you don’t see Team settings → Log drains:
  • Confirm you have Team Owner access (not just Member)
  • Confirm your Netlify team is on the Enterprise plan
If you’re not on Enterprise, use the Edge Function path — it works on all plans and requires no Netlify plan upgrade.
A few possible causes:
  • The drain isn’t enabled or is paused — check Netlify’s Team settings → Log drains
  • Your domain in Searchable doesn’t match the site on Netlify (check Agent Analytics → Setup → Confirm your domain)
  • The drain is configured but no AI bot has visited yet — try visiting your site with a known AI user agent to trigger a test event
If deliveries are succeeding in Netlify but nothing appears in Searchable, that points to a domain mismatch.

​
Removing the integration

To stop sending traffic to Searchable:
  1. Netlify → Team settings → Log drains → delete the drain
  2. Searchable → Agent Analytics → Setup → Tokens → revoke the token
Both sides are independent — revoking the token alone is enough to stop ingestion immediately, even if the drain stays configured in Netlify (its deliveries will start returning 401).

​
Next steps

See the data

Open Agent Analytics to see which assistants are crawling your site.

Add Search Console

Correlate AI crawls with search demand.