Safe Official docs AI & LLM Bots

Lyrenth AI Web Index

Operated by Lyrenth

Quick Facts

User-Agent:
AIWebIndex
Category:
AI & LLM Bots
Operator:
Lyrenth
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
lyrenth.com

Confirmed by the operator

Lyrenth names AIWebIndex on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Lyrenth AI Web Index?

Lyrenth AI Web Index is an AI search-index crawler operated by Lyrenth. It collects and indexes web content so it can be surfaced as citations or answers inside Lyrenth's AI search experience. Allowing Lyrenth AI Web Index can increase your visibility in AI-powered search results, which is why most sites choose to permit it.

Lyrenth AI Web Index is an AI search-index crawler operated by Lyrenth. It collects and indexes web content so it can be surfaced as citations or answers inside Lyrenth's AI search experience. Allowing Lyrenth AI Web Index can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Lyrenth AI Web Index uses the user-agent token AIWebIndex. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Lyrenth AI Web Index?

✅ No SEO Impact - Blocking Lyrenth AI Web Index does not affect your rankings in Google, Bing, or any other search engine. Lyrenth AI Web Index is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
Generally safe to allow; provides legitimate crawling value.

Want to see whether Lyrenth AI Web Index actually visits you? Read how do I monitor AI bot traffic to my website?

How to block Lyrenth AI Web Index with robots.txt

<code>User-agent: AIWebIndex</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: AIWebIndex Disallow: /
Allow all (robots.txt)
User-agent: AIWebIndex Allow: /
Block private only (robots.txt)
User-agent: AIWebIndex Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Lyrenth AI Web Index if ($http_user_agent ~* "AIWebIndex") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Lyrenth AI Web Index SetEnvIfNoCase User-Agent "AIWebIndex" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Lyrenth AI Web Index safe to allow?

Yes, Lyrenth AI Web Index is a safe and legitimate crawler operated by Lyrenth. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Lyrenth AI Web Index requests resolve to Lyrenth's domain.

What does Lyrenth AI Web Index do?

Understanding Lyrenth AI Web Index's purpose helps you decide whether to allow or block it.

  • Indexes web pages for AI-powered search answers
  • Surfaces your content as citations inside AI search results
  • Builds a knowledge index used to answer user questions
  • Allowing it can increase visibility in AI search
  • Respects robots.txt directives

Lyrenth AI Web Index in context

Lyrenth AI Web Index is a retrieval crawler that feeds AI search answers operated by Lyrenth. In plain terms, it builds a search or answer index. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about Lyrenth AI Web Index rests on what you want from Lyrenth, not on its behaviour. How we rate safety and impact.

How site owners treat Lyrenth AI Web Index

Our robots.txt study of the Tranco top 10,000 did not track AIWebIndex as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

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.

Lyrenth crawlers and close alternatives

Lyrenth AI Web Index is one of 2 Lyrenth crawlers in our database. A User-agent: AIWebIndex group controls Lyrenth AI Web Index only; the other Lyrenth tokens below need their own lines.

  • AIWebIndex: this crawler (Tier 2)
  • AIWebIndex-Agent: Lyrenth on-demand fetch, fetches a page when a person asks an assistant or app to open it (Tier 3)

To give Lyrenth AI Web Index the same answer as its siblings, stack User-agent: AIWebIndex with their lines above one set of rules; to treat Lyrenth AI Web Index differently, give it its own group.

Other AI and LLM crawlers that do the same job (builds a search or answer index) include AddSearchBot from AddSearch, atlassian-bot from Atlassian, AzureAI-SearchBot from Microsoft, Cloudflare-AI-Search from Cloudflare, Cloudflare-AutoRAG from Cloudflare, ExaBot from Exa. Deciding about Lyrenth AI Web Index is usually a decision about the whole group, so check how your file treats these too.

We first recorded AIWebIndex on September 22, 2026. Lyrenth documents it on lyrenth.com, and we recheck that page before each release.

Which rule Lyrenth AI Web Index actually follows

Lyrenth AI Web Index reads exactly one group in robots.txt, the most specific one that names AIWebIndex, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: AIWebIndex
Disallow: /drafts/
  1. Find the group. Lyrenth AI Web Index looks for a group naming AIWebIndex. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Lyrenth AI Web Index, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Lyrenth AI Web Index if the file also has a User-agent: AIWebIndex group?

No. Once a group names it, Lyrenth AI Web Index reads only that group. Put every rule you want it to follow inside its own group.

Related: writing content AI engines can cite

Test yourself: will blocking Lyrenth AI Web Index remove your pages from AI answers?

Often, yes. Lyrenth AI Web Index is a retrieval crawler that feeds AI search answers, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: aiwebindex the same as User-agent: AIWebIndex?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Lyrenth AI Web Index? Decide by situation

Recommended setting for Lyrenth AI Web Index by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. Lyrenth AI Web Index fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because Lyrenth AI Web Index is a retrieval crawler that feeds AI search answers. Block the operator's training crawler instead.
You run an online shopAllow it on product and category pages, which are the pages shoppers ask assistants about.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Lyrenth AI Web Index on your own site

  1. Open /robots.txt on your domain and search for AIWebIndex. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Lyrenth AI Web Index follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Lyrenth AI Web Index even when robots.txt allows it, and that never shows in the file.
  4. Run our AI bot checker to see how Lyrenth AI Web Index and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Lyrenth AI Web Index

The errors we see most often with Lyrenth AI Web Index in the files and firewalls we test:

  1. Blocking Lyrenth AI Web Index 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.
  2. Letting a firewall or bot-fight mode refuse Lyrenth AI Web Index while robots.txt allows it. The file looks right, but the crawler still gets a 403 or a challenge page.
  3. Forgetting that once a User-agent: AIWebIndex group exists, Lyrenth AI Web Index ignores every rule under User-agent: *.

All three hide inside a file that looks correct, so check Lyrenth AI Web Index from outside after every change.

Spotting Lyrenth AI Web Index in your logs

robots.txt says what Lyrenth AI Web Index may do; your access logs show what it 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" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "AIWebIndex" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Lyrenth AI Web Index user-agent, so confirm the source before acting on a match:

  • AIWebIndex: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Lyrenth AI Web Index request with caution.

Frequently Asked Questions

What is the official user-agent string for Lyrenth AI Web Index?
The official user-agent string for Lyrenth AI Web Index is: AIWebIndex. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Lyrenth AI Web Index by performing a reverse-DNS lookup on the source IP.
Is Lyrenth AI Web Index safe?
Yes, Lyrenth AI Web Index is a safe and legitimate crawler operated by Lyrenth. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Lyrenth AI Web Index hurt my SEO?
✅ No SEO Impact - Blocking Lyrenth AI Web Index does not affect your rankings in Google, Bing, or any other search engine. Lyrenth AI Web Index is an AI crawler, not a traditional search indexer. You can freely block it via User-agent / Disallow: / without any SEO penalty.
How do I block Lyrenth AI Web Index in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: AIWebIndex
Disallow: /

This instructs Lyrenth AI Web Index not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Lyrenth AI Web Index respect robots.txt?
Lyrenth AI Web Index is operated by Lyrenth and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Lyrenth AI Web Index is crawling my site?
Search your web server access logs for the string AIWebIndex (case-insensitive: grep -i "AIWebIndex" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us