Webz.io Extended
CautionUser-agent: Webzio-Extended
Category: Scrapers
SEO impact if blocked: 2/10
1 crawler operated by Webz.io
Webz.io operates 1 crawler in our directory, filed under Scrapers. Its crawl behaviour is rated caution.
Blocking Webz.io carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Webz.io: Generally safe to allow; provides legitimate crawling value.
| Operator | Webz.io |
|---|---|
| Crawler in directory | 1 |
| Categories | Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
| Official crawler docs | Webz.io crawler documentation |
Webz.io runs 1 crawler in our database. Grouped by the job each one does:
Webzio-ExtendedThe highest-priority token is Tier 6. That makes Webz.io a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
None of Webz.io'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.
A robots.txt file cannot say "Webz.io"; it can only name Webz.io's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Webz.io fetches through it
User-agent: Webzio-Extended
Disallow: /private/
Allow: /
User-agent: *.* group, so copy any Disallow lines you still want it to obey.User-agent: Webz.io block all of Webz.io's crawlers?No. robots.txt matches crawler tokens, not company names. Use the token Webzio-Extended.
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
A one-paragraph brief for every Webz.io token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
Webzio-Extended, Tier 6): a training crawler that collects pages to train AI models. Rated caution. Webz.io Extended's operator does not clearly document how it treats robots.txt. Write the Webz.io Extended rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.The errors we see most often with Webz.io's crawlers in the files and firewalls we test:
User-agent: * rule that also catches search engines. Name Webzio-Extended in its own group instead.All three hide inside a file that looks correct, so check Webz.io's crawlers from outside after every change.
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 Webz.io's marketing. Webz.io has one token in our database, so the whole picture fits in one place.
Webzio-Extended in our recordsWe first recorded Webzio-Extended on March 17, 2026. Webz.io documents it on webz.io, and we recheck that page before each release. No file in our top-10,000 scans names Webzio-Extended, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, Webzio-Extended sits 37th by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 6 of the 39 share its caution rating. Other operators with a crawler that collects pages to train AI models: ClaudeBot (Anthropic, Tier 1), Google-Extended (Google, Tier 1), GPTBot (OpenAI, Tier 1), Meta-ExternalAgent (Meta, Tier 1), AI2Bot (Allen Institute for AI, Tier 2). A policy for Webzio-Extended is usually a policy for these too.
Webzio-ExtendedTeams 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 Webzio-Extended entry reads:
User-agent: Webzio-Extended
Allow: /
Paste the line into the validator with one of your own URLs before it goes live. Revisit the Webzio-Extended entry sooner than most: a caution rating means Webz.io traffic deserves a monthly look at your logs.
Webzio-Extended on your own siteBecause Webz.io runs only Webzio-Extended in our records, one check covers the whole operator. Search your access logs for the string Webzio-Extended over the last 30 days, note how many requests it made and which paths it asked for, then compare that with what your robots.txt allows. Match the requests against what Webz.io publishes about the crawler, since that page is the only authority on its behaviour. A Tier 6 crawler rated caution rarely needs more than a quarterly look, and our log checker does the counting for you.
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Webz.io'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 Webz.io's crawlers too.
Webzio-Extended, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.User-agent group per decision and repeat any shared rules inside it.This rule covers the single crawler Webz.io operates. Add it to the robots.txt file at the root of your domain.
These Webz.io rules ask; they do not enforce. If a Webz.io 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.
Text size
Saved on this device only. Drag the round button to move it. Accessibility statement