Check delivery

Most methods send something only when an AI crawler visits, which on a small site can take hours or days. To test the connection now, run the setup check command Setup shows, curl -L -A "SearchlySetupCheck/1.0" "https://example.com/" with your own domain. Your method reports the request like a crawler's, and Searchly counts it as a setup check without storing it. Then choose Check now.

Confirm data is flowing shows one of three states:

• Waiting for the first delivery: nothing from this source has reached Searchly yet.
• Connected. No AI crawler requests yet: a delivery arrived, such as a setup check, a Cloudflare validation upload, or a Vercel test, but no AI crawler request has been stored.
• Receiving AI crawler requests.

Below the state, today's counts (UTC) show the deliveries, the crawler requests stored, and what was set aside: requests from people and other bots, requests for other domains such as preview deployments, and requests over the daily limit.

Setup also tells you when something needs a look:

• No delivery for 24 hours from a method that also sends requests from people or other bots: a Vercel log drain, or an HTTP API sender that posted such requests in the last 7 days. For these, a quiet day usually means the method stopped. Cloudflare Logpush, whose filter keeps your visitors' requests in Cloudflare, the Cloudflare Worker, and the code in your site get 7 days, because a quiet week can be normal on a small site.
• Most requests that name a crawler with published IP ranges came from other addresses. Your site probably sits behind another proxy or CDN that replaces the visitor's address. Those requests are kept as declared.
• Cloudflare Logpush and the Cloudflare Worker both delivered today. A request both see is counted once; you can remove one of them.
• A Vercel log drain and Next.js middleware both delivered today. A request both see may be counted twice, so keep only one of them; the drain also records status codes.

For WordPress, the check Setup shows adds a query string, which gets it past most page caches. If it still doesn't arrive, a page cache may have answered it before WordPress ran. On hosts where the plugin sends through WP-Cron, the check can take a few minutes to arrive.