Lyrenth AI Web Index
SafeUser-agent: AIWebIndex
Category: AI & LLM Bots
SEO impact if blocked: 2/10
Lyrenth
2 crawlers operated by Lyrenth
https://lyrenth.com/Who Lyrenth is, for site owners
Lyrenth operates 2 crawlers in our directory, filed under AI & LLM Bots. Of those 2, 2 rated safe for crawl behaviour.
Blocking Lyrenth carries an SEO impact score of 1/10 to 2/10 across its crawlers. Every crawler here carries the same blocking impact: Low - No SEO ranking impact.
Our recommendation for Lyrenth, set by its least reassuring crawler (Lyrenth AI Web Index, rated safe): Generally safe to allow; provides legitimate crawling value.
Lyrenth at a glance
| Operator | Lyrenth |
|---|---|
| Crawlers in directory | 2 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 1/10 to 2/10 |
| Crawl behaviour | 2 rated safe |
| Website | lyrenth.com |
| Official crawler docs | Lyrenth crawler documentation |
Crawlers operated by Lyrenth
What Lyrenth's crawlers are for
Lyrenth runs 2 crawlers in our database. Grouped by the job each one does:
- a retrieval crawler that feeds AI search answers:
AIWebIndex - a user-triggered agent:
AIWebIndex-Agent
The highest-priority token is Tier 2. That puts Lyrenth among the operators whose crawlers have a direct effect on whether AI answers or search results can include your pages.
How site owners treat Lyrenth
None of Lyrenth's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
Writing one policy for Lyrenth
A robots.txt file cannot say "Lyrenth"; it can only name Lyrenth's tokens, one group at a time. So "block Lyrenth" really means naming each of its 2 tokens, and you can give them different answers.
# Allow Lyrenth search and assistants, refuse training
User-agent: AIWebIndex
Disallow: /
User-agent: AIWebIndex
User-agent: AIWebIndex-Agent
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the live AI crawler test after any change to see the result for each Lyrenth token, including firewall refusals.
Test yourself: does User-agent: Lyrenth block all of Lyrenth's crawlers?
No. robots.txt matches crawler tokens, not company names. Name each token: AIWebIndex, AIWebIndex-Agent.
Test yourself: if you block one Lyrenth token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Lyrenth crawler, explained
A one-paragraph brief for every Lyrenth token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Lyrenth AI Web Index (
AIWebIndex, Tier 2): a retrieval crawler that feeds AI search answers that builds a search or answer index. Rated safe. Lyrenth AI Web Index's operator does not clearly document how it treats robots.txt. Write the Lyrenth AI Web Index rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study. - Lyrenth on-demand fetch (
AIWebIndex-Agent, Tier 3): a user-triggered agent that fetches a page when a person asks an assistant or app to open it. Rated safe. Lyrenth on-demand fetch's operator says it follows robots.txt, so a correctly written Lyrenth on-demand fetch group is enough to control it. Not tracked in our robots.txt study.
Common mistakes with Lyrenth's crawlers
The errors we see most often with Lyrenth's crawlers in the files and firewalls we test:
- Blocking Lyrenth's crawlers while trying to stop AI training. Retrieval crawlers fetch pages so answers can cite them; blocking it can remove you from those answers without affecting training.
- Letting a firewall or bot-fight mode refuse Lyrenth's crawlers while robots.txt allows it. The file looks right, but the crawler still gets a 403 or a challenge page.
- Forgetting that once a
User-agent: AIWebIndexgroup exists, Lyrenth's crawlers ignores every rule underUser-agent: *.
All three hide inside a file that looks correct, so check Lyrenth's crawlers from outside after every change.
Spotting Lyrenth in your logs
robots.txt says what Lyrenth AI Web Index and Lyrenth on-demand fetch may do; your access logs show what they actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "AIWebIndex|AIWebIndex-Agent" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -cAnd this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "AIWebIndex|AIWebIndex-Agent" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20Check the requests are genuine
Anyone can send these user-agents, so confirm the source before acting on a match:
AIWebIndex: we hold no published IP list, so use reverse DNS where Lyrenth documents a hostname and treat an unverifiable Lyrenth AI Web Index request with caution. Check it separately from Lyrenth on-demand fetch.AIWebIndex-Agent: we hold no published IP list, so use reverse DNS where Lyrenth documents a hostname and treat an unverifiable Lyrenth on-demand fetch request with caution. Check it separately from Lyrenth AI Web Index.
What our own data shows about Lyrenth
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Lyrenth's marketing. It covers 2 Lyrenth tokens in turn.
AIWebIndex in our records
We first recorded AIWebIndex on September 22, 2026. Lyrenth documents it on lyrenth.com, and we recheck that page before each release. No file in our top-10,000 scans names AIWebIndex, so any rule you write for it puts you ahead of almost every large site.
Among the 104 AI and LLM crawlers in our database, AIWebIndex sits 19th by priority (Tier 2), level with AddSearchBot, AI2Bot, AI2Bot-DeepResearchEval, aiHitBot. 81 of the 104 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2), Cloudflare-AutoRAG (Cloudflare, Tier 2). A policy for AIWebIndex is usually a policy for these too.
A decision record for AIWebIndex
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the AIWebIndex entry reads:
- Operator and job: Lyrenth; it builds a search or answer index.
- Priority and behaviour: Tier 2, rated safe, blocking impact low.
- Suggested starting point: Allow, and watch it in your logs.
- Enforcement: AIWebIndex's operator does not clearly document how it treats robots.txt. Write the AIWebIndex rule anyway, then confirm in your logs that its requests stop.
User-agent: AIWebIndex
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the AIWebIndex entry whenever Lyrenth announces a change, because a Tier 2 crawler affects visibility directly.
AIWebIndex-Agent in our records
We first recorded AIWebIndex-Agent on October 19, 2026. Lyrenth documents it on lyrenth.com, and we recheck that page before each release. No file in our top-10,000 scans names AIWebIndex-Agent, so any rule you write for it puts you ahead of almost every large site.
Among the 104 AI and LLM crawlers in our database, AIWebIndex-Agent sits 89th by priority (Tier 3), level with alphalens-bot, amazon-QBusiness, Anomura, Channel3Bot. 81 of the 104 share its safe rating. Other operators with a crawler that fetches a page when a person asks an assistant or app to open it: ChatGPT Agent (OpenAI, Tier 1), ChatGPT Operator (OpenAI, Tier 1), ChatGPT-User (OpenAI, Tier 1), ChatGPT-User/2.0 (OpenAI, Tier 1), Claude-SearchBot (Anthropic, Tier 1). A policy for AIWebIndex-Agent is usually a policy for these too.
A decision record for AIWebIndex-Agent
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the AIWebIndex-Agent entry reads:
- Operator and job: Lyrenth; it fetches a page when a person asks an assistant or app to open it.
- Priority and behaviour: Tier 3, rated safe, blocking impact low.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: AIWebIndex-Agent's operator says it follows robots.txt, so a correctly written AIWebIndex-Agent group is enough to control it.
User-agent: AIWebIndex-Agent
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the AIWebIndex-Agent entry once a quarter, or when Lyrenth publishes a new token next to it.
How top sites treat Lyrenth's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Lyrenth's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Lyrenth's crawlers too.
More questions about Lyrenth
- Will blocking Lyrenth affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Lyrenth's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Lyrenth?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Lyrenth on some sections and block it on others?
- Yes. Inside the group for
AIWebIndex, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Lyrenth delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Lyrenth offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Lyrenth?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Lyrenth review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the free AI crawler check to see the outcome from outside, including any firewall layer.
How to block or allow Lyrenth in robots.txt
These rules cover all 2 crawlers Lyrenth operates. Add them to the robots.txt file at the root of your domain.
Block Lyrenth completely
User-agent: AIWebIndex
User-agent: AIWebIndex-Agent
Disallow: /
Allow Lyrenth explicitly
User-agent: AIWebIndex
User-agent: AIWebIndex-Agent
Allow: /
These Lyrenth rules ask; they do not enforce. If a Lyrenth token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Lyrenth
What crawlers does Lyrenth run?
Lyrenth operates 2 crawlers in our directory: Lyrenth AI Web Index (user-agent AIWebIndex), Lyrenth on-demand fetch (user-agent AIWebIndex-Agent).
Should I block Lyrenth?
Generally safe to allow; provides legitimate crawling value. That guidance follows this operator's least reassuring crawler, Lyrenth AI Web Index, rated safe, because allowing an operator allows every crawler it runs. The SEO impact score for blocking is 1/10 to 2/10, where 10 means blocking costs you the most visibility.
How do I block Lyrenth in robots.txt?
Add the following to robots.txt at your domain root: User-agent: AIWebIndex then User-agent: AIWebIndex-Agent then Disallow: /. One Disallow line covers all 2 user-agent tokens.
Does blocking Lyrenth hurt my search rankings?
Every crawler here carries the same blocking impact: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking Lyrenth does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.