No data is showing up
Give edge deploys a minute
Give edge deploys a minute
Vercel, Netlify, and CloudFront roll out globally over a few minutes. Wait,
then send a test request:
Confirm your domain is verified
Confirm your domain is verified
Events for unverified domains are dropped. Check that the host you are
testing is the exact one you verified. Verifying
an apex (
example.com) covers its subdomains.Use a recognized bot user-agent
Use a recognized bot user-agent
The test must use a known agent string.
GPTBot/1.0 works. A normal browser
request from your laptop is treated as human traffic and won’t appear in the
bot view.Check the integration is bound to all routes
Check the integration is bound to all routes
For the Cloudflare Worker, confirm the routes cover your whole site
(
yourdomain.com/* and www.yourdomain.com/*). For Vercel/Netlify, confirm
the middleware matcher is /:path* or /*.Check the endpoint is reachable
Check the endpoint is reachable
From your network:
curl https://ingest.tryrankly.com/ingest/status should
return {"status":"ok"}.Bots show as “unverified”
The true client IP is missing
The true client IP is missing
Verification needs the real client IP. If your site is behind a proxy and
your logs record the proxy’s IP, requests fall back to unverified. Use an
edge integration (Cloudflare Worker, Fastly, Akamai) that captures the real
IP, or log it explicitly. See Verification.
On Google Cloud behind Cloudflare
On Google Cloud behind Cloudflare
Log the real IP into a
jsonPayload field named cfConnectingIp,
clientIp, or xForwardedFor. Rankly reads it automatically.The numbers look too low
Check the date range
Check the date range
The dashboard defaults to a recent window. Widen it (for example to “Last 1
year”) to see the full picture.
The integration may only cover part of your traffic
The integration may only cover part of your traffic
If a route or subdomain isn’t behind the integration, its traffic isn’t
counted. Make sure the integration covers every path and host you care about.
LLM referrals read zero
Confirm referer is being captured
Confirm referer is being captured
LLM referrals come from human visits with an LLM referer (browser user-agent +
a referer like
chatgpt.com). The official integrations forward these on
purpose. If you built a custom integration, make sure you send requests whose
referer is an LLM domain, not just bot user-agents.Still stuck?
Book a call
Get on a 30-minute call and we’ll connect your site with you live.
Email support
Send us your domain and the integration you used.