WebmasterID logoWebmasterID
Robots & crawl control

How to block Brandwatch

Brandwatch operates crawlers that collect public web and social content for its consumer-intelligence and social-listening products. It is a declared crawler with a documented robots.txt token. Operators who do not want their pages collected into brand-monitoring datasets can disallow it; this page shows the token and rule.

Partially verified

What this means

Brandwatch is a consumer-intelligence and social-listening platform that collects public web content so brands can monitor mentions, sentiment and trends. Part of that collection uses a crawler that fetches public pages. Blocking it asks Brandwatch to stop fetching your pages directly.

A block does not remove your brand mentions that Brandwatch gathers from social platforms and other feeds; it only addresses direct crawling of your own site. robots.txt is honoured by compliant crawlers and is not an access-control mechanism.

How to block it

Target the Brandwatch crawler token in its own user-agent group, matching on the stable token rather than a version string.

User-agent: Brandwatch Disallow: /

Because robots.txt is advisory, confirm in your logs that token-carrying requests stop. If they continue, the source may be impersonating the token, which a firewall rule would address. Brandwatch and adjacent social-listening tools such as Meltwater and Talkwalker each use their own token, so block them independently.

How it appears in analytics and logs

A request carrying the Brandwatch crawler token is a fetch for consumer-intelligence datasets, not a human visit. It is bot traffic. The user agent is a claim, so treat sustained activity as crawl coverage rather than audience.

Diagnostic use case

Stop Brandwatch from crawling your site for social-listening datasets, and confirm in your logs that the crawler honours the rule.

What WebmasterID can help detect

WebmasterID classifies social-listening crawlers like Brandwatch server-side and surfaces them on the bot-intelligence surface, so you can verify a robots.txt block without parsing raw logs.

Common mistakes

Privacy and accuracy notes

Blocking Brandwatch relies only on the request user-agent token. No human identity is involved. WebmasterID records the crawl as a bot event, separate from human analytics, and never attaches it to a visitor profile.

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.