WebmasterID logoWebmasterID
Robots & crawl control

How to block BLEXBot in robots.txt

BLEXBot is the crawler operated by WebMeUp to build a backlink index used by SEO tools. This page gives the robots.txt rule to disallow the BLEXBot token and notes that WebMeUp documents the crawler and its robots.txt support.

Verified against primary sources

What BLEXBot is

BLEXBot is the crawler operated by WebMeUp to gather link data for a backlink index that powers SEO analysis tools. It is not a search engine, so blocking it does not affect how Google or Bing index your site — it only removes you from WebMeUp's link dataset.

WebMeUp publishes a crawler page documenting BLEXBot, its robots.txt token, and how to limit it. Use that documentation rather than guessing the user-agent string.

The rule

To disallow BLEXBot site-wide, target its token:

User-agent: BLEXBot Disallow: /

The user-agent string contains the BLEXBot token plus a self-identifying URL pointing at WebMeUp's crawler help page. Match the stable token and confirm in logs that activity drops. robots.txt is a request to compliant crawlers, not enforcement.

How it appears in analytics and logs

A request carrying the BLEXBot token is WebMeUp's backlink crawler fetching a URL. It is a bot event that contributes to an SEO dataset, not a human visit or referral.

Diagnostic use case

Disallow BLEXBot when you do not want your pages sampled into a third-party backlink index, or to reduce crawl load from an SEO-data crawler that sends you no visitors.

What WebmasterID can help detect

WebmasterID classifies BLEXBot by its token as an SEO crawler, separate from human analytics, so you can confirm whether a disallow rule reduced its requests.

Common mistakes

Privacy and accuracy notes

Blocking BLEXBot is a publishing-policy choice in a public file. It involves no visitor data and is not an access-control mechanism.

Related pages

Sources and verification notes

Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.