What is weborama-fetcher?

weborama-fetcher is a bot in the advertising and marketing bots category, operated by Weborama.

Bot name
weborama-fetcher
Operator
Weborama
Type
Bot
Respects robots.txt
Not confirmed
robots.txt user agent
weborama-fetcher
Signs requests (Web Bot Auth)
No

About weborama-fetcher

weborama-fetcher reads page content for Weborama's contextual and semantic advertising data.

Advertising bots review landing pages, check ad placements and classify pages for brand safety and contextual targeting. Blocking ad verification bots can stop your ads or your inventory from serving, so allow the ones your ad partners use.

weborama-fetcher user agent

Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.

How to block weborama-fetcher in robots.txt

We have not confirmed whether weborama-fetcher follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.

Block weborama-fetcher from the whole site

User-agent: weborama-fetcher
Disallow: /

Block weborama-fetcher from some folders

User-agent: weborama-fetcher
Disallow: /private/
Disallow: /search

Allow weborama-fetcher only on some folders

User-agent: weborama-fetcher
Allow: /blog/
Disallow: /

Allow weborama-fetcher and block other crawlers

User-agent: weborama-fetcher
Allow: /

User-agent: *
Disallow: /

Things to know

  • Each host needs its own file. Rules on www.example.com do not apply to shop.example.com.
  • A crawler obeys only the most specific group that names it. Once you add a User-agent: weborama-fetcher group, weborama-fetcher ignores your User-agent: * rules, so repeat any that should still apply.
  • The user agent name is not case sensitive. We take weborama-fetcher from weborama-fetcher's user agent; check Weborama's own documentation if it publishes a different robots.txt name.
  • Crawlers cache robots.txt, so changes can take up to a day to apply. Disallow stops crawling but does not remove pages already collected or indexed.

Limits of robots.txt

  1. weborama-fetcher may not follow the rule. robots.txt is a request that nothing enforces, and we have not confirmed that weborama-fetcher follows it. Check your logs after adding a rule.
  2. The user agent could be fake. robots.txt matches the name a request claims. Anyone can send weborama-fetcher's user agent, and a scraper using it is not bound by Weborama's robots.txt policy. Only checking the source network tells a real weborama-fetcher from a fake one.

Treat robots.txt as a statement of your policy, and enforce it where requests arrive.

Who should care about weborama-fetcher

Publishers

Ad verification and contextual crawlers like weborama-fetcher can decide whether your pages get demand. Blocking the ones your partners use can lower fill rates.

Transfon Security for publishers

Media buyers and advertisers

weborama-fetcher checks pages for ad platforms. Its visits to landing pages are not users, so exclude them from conversion data.

Transfon Security for advertisers

E-commerce

Ad platforms send crawlers like weborama-fetcher to check product landing pages. Keep it allowed so ads are not disapproved, and out of analytics.

Transfon Security for e-commerce

SaaS and APIs

Allow weborama-fetcher on landing pages linked from your ads, and keep it off the app.

Transfon Security for SaaS and APIs

Block weborama-fetcher with Transfon Security

robots.txt is a request, not an enforcement. Transfon Security shows weborama-fetcher by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.

Transfon Security

Control weborama-fetcher on your site

  • See every weborama-fetcher visit and the pages it reads
  • Spot bots that fake trusted crawler names
  • Block, allow or rate limit weborama-fetcher with one rule
  • Works with or without robots.txt support

Frequently asked questions

What is weborama-fetcher?

weborama-fetcher is a bot in the advertising and marketing bots category, operated by Weborama. weborama-fetcher reads page content for Weborama's contextual and semantic advertising data.

Does weborama-fetcher respect robots.txt?

We have not confirmed whether weborama-fetcher follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.

How do I block weborama-fetcher?

Add "User-agent: weborama-fetcher" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "weborama-fetcher" at your WAF. In Transfon Security that is one User Agent block rule.

Is robots.txt enough to block weborama-fetcher?

No. robots.txt is voluntary, so weborama-fetcher may not follow it, and anyone can send weborama-fetcher's user agent, so a fake weborama-fetcher ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.

Should I block weborama-fetcher?

Advertising bots review landing pages, check ad placements and classify pages for brand safety and contextual targeting. Blocking ad verification bots can stop your ads or your inventory from serving, so allow the ones your ad partners use.

Related bots

All advertising and marketing bots · Full bot directory

See Which Bots Visit Your Site

Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.

Stay ahead of the publishing curve

Privacy, security, monetization, and performance insights. A few emails a month, no spam.

By subscribing you agree to our privacy policy.