Caution Official docs Scrapers

Webz.io Extended

Operated by Webz.io

Quick Facts

User-Agent:
Webzio-Extended
Category:
Scrapers
Operator:
Webz.io
Safety:
Use Caution
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
webz.io

Confirmed by the operator

Webz.io names Webzio-Extended 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 Webz.io Extended?

Webz.io Extended is an AI data-collection crawler operated by Webz.io. It gathers public web content to build or refine training datasets for large language models. Like other AI training crawlers, Webz.io Extended does not influence your search-engine rankings, so you can block it via robots.txt without any SEO penalty if you wish to opt out of AI training.

Webz.io Extended is an AI data-collection crawler operated by Webz.io. It gathers public web content to build or refine training datasets for large language models. Like other AI training crawlers, Webz.io Extended does not influence your search-engine rankings, so you can block it via robots.txt without any SEO penalty if you wish to opt out of AI training.
Webz.io Extended uses the user-agent token Webzio-Extended. 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 Webz.io Extended?

✅ No SEO Impact - Blocking Webz.io Extended does not affect your rankings in Google, Bing, or any other search engine. Webz.io Extended 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.

How to block Webz.io Extended with robots.txt

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

Block completely (robots.txt)
User-agent: Webzio-Extended Disallow: /
Allow all (robots.txt)
User-agent: Webzio-Extended Allow: /
Block private only (robots.txt)
User-agent: Webzio-Extended Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Webz.io Extended if ($http_user_agent ~* "Webzio-Extended") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Webz.io Extended SetEnvIfNoCase User-Agent "Webzio-Extended" 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 Webz.io Extended safe to allow?

Webz.io Extended is generally legitimate but warrants caution. It is operated by Webz.io. Review its crawl behaviour in your logs and apply robots.txt or rate-limiting if its activity is heavier than you expect.
Verify by reverse-DNS lookup: legitimate Webz.io Extended requests resolve to Webz.io's domain.

What does Webz.io Extended do?

Understanding Webz.io Extended's purpose helps you decide whether to allow or block it.

  • Collects public web content to train large language models
  • Builds and refreshes AI training datasets
  • Harvests text, code, and structured data for model improvement
  • Does NOT affect search-engine rankings
  • Can be blocked to opt out of AI training without SEO loss

Webz.io Extended in context

Webz.io Extended is a training crawler operated by Webz.io. In plain terms, it collects pages to train AI models. Our database files it under data scrapers and ranks it Tier 6, the lowest priority: scrapers and tools that offer most sites little or nothing. 37 of the 39 data scrapers in our database share this tier.

Its safety rating is caution and its blocking impact is low. So the decision about Webz.io Extended rests on what you want from Webz.io, not on its behaviour. How we rate safety and impact.

How site owners treat Webz.io Extended

Our robots.txt study of the Tranco top 10,000 did not track Webzio-Extended 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?

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.

Webz.io crawlers and close alternatives

Webz.io runs only this one crawler in our database, so a single User-agent: Webzio-Extended group controls everything Webz.io fetches through it.

Other data scrapers that do the same job (collects pages to train AI models) include TikTokSpider from ByteDance, Brightbot from Bright Data, CCBot from Common Crawl, Cotoyogi from ROIS-DS. Deciding about Webz.io Extended is usually a decision about the whole group, so check how your file treats these too.

We first recorded Webzio-Extended on March 17, 2026. Webz.io documents it on webz.io, and we recheck that page before each release.

Which rule Webz.io Extended actually follows

Webz.io Extended reads exactly one group in robots.txt, the most specific one that names Webzio-Extended, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Webzio-Extended
Disallow: /drafts/
  1. Find the group. Webz.io Extended looks for a group naming Webzio-Extended. 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 Webz.io Extended, 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 Webz.io Extended if the file also has a User-agent: Webzio-Extended group?

No. Once a group names it, Webz.io Extended reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Webz.io Extended remove your pages from AI answers?

No. Webz.io Extended collects training data. Blocking it changes what future models learn, not which pages AI answers cite today.

Test yourself: is User-agent: webzio-extended the same as User-agent: Webzio-Extended?

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

Should you allow Webz.io Extended? Decide by situation

Recommended setting for Webz.io Extended by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itYour call. Webz.io Extended is a training crawler, so blocking it does not remove you from AI answers; retrieval crawlers do that job.
You license content and want to stop AI trainingBlock it by name with User-agent: Webzio-Extended and Disallow: /.
You run an online shopConsider blocking it, especially on price and stock pages that competitors scrape.
Your server is under load from botsRate-limit before blocking. It is rated caution in our database.

Check Webz.io Extended on your own site

  1. Open /robots.txt on your domain and search for Webzio-Extended. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Webz.io Extended 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 Webz.io Extended even when robots.txt allows it, and that never shows in the file.
  4. Run our AI bot access checker to see how Webz.io Extended and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Webz.io Extended

The errors we see most often with Webz.io Extended in the files and firewalls we test:

  1. Assuming that blocking Webz.io Extended removes you from AI answers. It is a training crawler; AI answers are fed by retrieval and user-triggered crawlers with different tokens.
  2. Blocking Webz.io Extended with a broad User-agent: * rule that also catches search engines. Name Webzio-Extended in its own group instead.
  3. Expecting a Webz.io Extended block to remove content already collected. robots.txt only affects future visits.

All three hide inside a file that looks correct, so check Webz.io Extended from outside after every change.

Spotting Webz.io Extended in your logs

robots.txt says what Webz.io Extended 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 "Webzio-Extended" /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 "Webzio-Extended" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Webz.io Extended user-agent, so confirm the source before acting on a match:

  • Webzio-Extended: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Webz.io Extended request with caution.

Frequently Asked Questions

What is the official user-agent string for Webz.io Extended?
The official user-agent string for Webz.io Extended is: Webzio-Extended. 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 Webz.io Extended by performing a reverse-DNS lookup on the source IP.
Is Webz.io Extended safe?
Webz.io Extended is generally legitimate but warrants caution. It is operated by Webz.io. Review its crawl behaviour in your logs and apply robots.txt or rate-limiting if its activity is heavier than you expect.
Will blocking Webz.io Extended hurt my SEO?
✅ No SEO Impact - Blocking Webz.io Extended does not affect your rankings in Google, Bing, or any other search engine. Webz.io Extended 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 Webz.io Extended in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: Webzio-Extended
Disallow: /

This instructs Webz.io Extended not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Webz.io Extended respect robots.txt?
Webz.io Extended is operated by Webz.io 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 Webz.io Extended is crawling my site?
Search your web server access logs for the string Webzio-Extended (case-insensitive: grep -i "Webzio-Extended" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us