omgili user agent
Operated by Webz.io
omgili is the Webz.io crawler user agent that collects web data sold to other companies.
The omgili bot at a glance
- omgili is operated by Webz.io and collects public web pages that may be used to train AI models.
- The robots.txt token for omgili is omgili.
- Blocking an AI training crawler has no effect on Google or Bing rankings.
- omgili robots.txt support: Yes.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is omgili?
Webz.io still uses the omgili name for crawling; the data can end up in third-party AI training sets.
Public registries report that it follows robots.txt.
Should you block omgili?
Blocking omgili is a business decision: it protects your content but can lower how well AI products know your brand.
| Effect on search rankings | Blocking an AI training crawler has no effect on Google or Bing rankings. |
|---|---|
| Effect on AI visibility | Blocking keeps your future pages out of that company's training data, so its models may know less about your brand over time. It does not remove you from that company's AI search, which uses a separate bot. |
| Follows robots.txt | Yes |
| Recommendation | Your choice |
How to block or allow omgili
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token omgili is matched case-insensitively.
robots.txt: block
# Block omgili
User-agent: omgili
Disallow: /robots.txt: allow
# Allow omgili
User-agent: omgili
Allow: /robots.txt: partial
# Keep omgili out of private areas only
User-agent: omgili
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to omgili
if ($http_user_agent ~* "(omgili)") {
return 403;
}Apache
# Apache .htaccess: return 403 to omgili
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (omgili) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "omgili")How to verify real omgili traffic
Webz.io publishes no IP list or reverse DNS pattern for omgili, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find omgili in your server logs
Search the web server access log for the token. The command below counts omgili requests per URL on Nginx or Apache.
grep -i "omgili" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
omgili FAQ
omgili uses the robots.txt token "omgili". Webz.io does not publish a full user-agent string, so match the token inside the User-Agent header.
Yes. Webz.io states that omgili follows robots.txt rules written for the "omgili" token.
Blocking an AI training crawler has no effect on Google or Bing rankings. Blocking keeps your future pages out of that company's training data, so its models may know less about your brand over time. It does not remove you from that company's AI search, which uses a separate bot.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: omgili" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Webz.io publishes no IP list or reverse DNS pattern for omgili, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "omgili", for example with: grep -i "omgili" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Public bot registry. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
