Does AIWebIndex respect robots.txt?

Yes. The operator documents that AIWebIndex reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.

How do I block AIWebIndex?

Add these user-agent tokens (AIWebIndex, AIWebIndex-Agent) to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.

IPScanner

AI search crawlers

AIWebIndex

AIWebIndex is a bot operated by Lyrenth (Aleksma Ai, Inc.) that indexes pages so an AI answer engine can cite them. AIWebIndex is a web crawler operated by Lyrenth that builds an AI-readable index of web content and serves pages to AI agents with attribution. It honours robots.txt, and a request claiming to be AIWebIndex can be checked against a published IP range file or a forward-confirmed reverse DNS lookup.

Also seen as AIWebIndex-Agent. Rules need to cover every token.

Verify an IP that claimed to be AIWebIndex

Paste the address from the log line. It is checked against what the operator publishes, so the answer is evidence rather than a guess about the user-agent string.

The check needs JavaScript. The evidence it uses is public either way: the operator's own documentation says how a request claiming to be AIWebIndex can be verified, and the table below repeats it.

AIWebIndex at a glance

Reference data for the AIWebIndex crawler
User agent	`AIWebIndex/2.0 (+https://lyrenth.com/bot; AI-readable web index)`
Operator	Lyrenth (Aleksma Ai, Inc.)
Purpose	Builds an AI-readable web index and serves individual pages back to AI agents as structured text with attribution and a link to the source.
Respects robots.txt	Yes, documentedsource
Verification method	Published IP ranges or reverse DNS Lyrenth publishes its crawl IPs as JSON (gptbot.json format). Reverse DNS resolves under lyrenth.com and forward-resolves back to the same IP. A Web Bot Auth (RFC 9421) key directory is also published at api.lyrenth.com/.well-known/http-message-signatures-directory. All 22 published addresses forward-confirmed on 2026-08-24. https://lyrenth.com/bot/ip-ranges.json
Crawl pattern	At most one request per domain every 2 seconds, and slower where robots.txt sets a longer Crawl-delay.
Robots.txt tokens	`AIWebIndexAIWebIndex-Agent`
Operator documentation	https://lyrenth.com/crawler-policy

AIWebIndex is a web crawler operated by Lyrenth that builds an AI-readable index of web content and serves pages to AI agents with attribution. Lyrenth states it does not train foundation models on crawled content. Its crawler policy notes that owners who verify a domain grant Lyrenth the right to license that domain's canonical content to AI labs; this applies to verified domains only, not to regular crawling.

robots.txt

Allow or block AIWebIndex

Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.

Block AIWebIndex

User-agent: AIWebIndex
User-agent: AIWebIndex-Agent
Disallow: /

Blocks every path for this crawler only.

Allow AIWebIndex

User-agent: AIWebIndex
User-agent: AIWebIndex-Agent
Allow: /

Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.

Allow, except the pages you never want quoted

User-agent: AIWebIndex
User-agent: AIWebIndex-Agent
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /search

Edit the Disallow paths to match your own account, checkout and search URLs.

What blocking actually costs you

Blocking AIWebIndex takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.

Block every crawler in the directory at once

Verification

Is that really AIWebIndex?

A user-agent header is a string the client chooses. Scrapers copy AIWebIndex precisely because site owners allow it. Lyrenth publishes its crawl IPs as JSON (gptbot.json format). Reverse DNS resolves under lyrenth.com and forward-resolves back to the same IP. A Web Bot Auth (RFC 9421) key directory is also published at api.lyrenth.com/.well-known/http-message-signatures-directory. All 22 published addresses forward-confirmed on 2026-08-24.

Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.

Datacenter IP detectionNearly every real AI crawler egresses from cloud ranges. A residential IP claiming to be one is the first thing to check.IP reputation checkSee whether the address behind a fake crawler hit has a history of abuse elsewhere.Residential proxy detectionScrapers that get blocked by user agent often come back through residential proxy pools.

Related crawlers

AmazonbotAmazon · AI search crawlers Amzn-SearchBotAmazon · AI search crawlers ApplebotApple · AI search crawlers BingbotMicrosoft · AI search crawlers Claude-SearchBotAnthropic · AI search crawlers

Agentscan

Identify crawlers automatically instead of by hand

Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.

How Agentscan works API reference Pricing What is my IP

FAQ