SEObot
risk.is_airisk.is_crawler
- Method
- Ranges Published IP ranges
- Official file
- Format
- Documentation page, parsed
- Refresh
- Every hour. If a refresh fails, entries expire after 24 hours instead of being trusted forever.
Bot signals — AI crawler & agent
SEObot IP addresses
Published crawler egress for SEObot AI SEO agents; shared with known_crawler.
01 — Verification
How IPAPI.GR verifies SEObot.
Only from what SEObot publishes about itself. No third-party blocklists, no behavioural guesses. Live address counts change with every publication, so check the official file for the current list.
02 — In the response
What a match looks like.
A lookup of a SEObot address sets risk.is_ai and risk.is_crawler. The flags come with geolocation and network data in the same response, for Pro API keys.
This publication is AI crawling or retrieval traffic, so it counts as both an AI source and a crawler.
The response says which kind of bot an address belongs to, not which operator. Pair it with the user agent: a request that claims to be SEObot but doesn't match is unverified.
{
// … location and network fields …
"risk": {
"is_ai": true,
"is_crawler": true,
"is_scanner": false
}
}
03 — Questions
About SEObot.
Where does SEObot publish its IP addresses?
SEObot publishes its addresses at https://docs.seobotai.com/en/articles/10628001-seobot-crawler-bot-documentation. IPAPI.GR reads that publication directly, not a third-party copy.
How often is the SEObot list refreshed?
IPAPI.GR re-fetches it every hour. If a refresh fails, the previous entries expire after at most 24 hours instead of being trusted forever.
Which risk flag does SEObot set?
A matching address sets risk.is_ai and risk.is_crawler in the lookup response. The risk flags are returned for Pro API keys.
Related operators
Verify SEObot on every request.
Pro: 40,000,000 requests a day with is_ai, is_crawler and is_scanner in every lookup.