magpie-crawler
CautionUser-agent: magpie-crawler
Category: Data Scrapers
SEO impact if blocked: 2/10
Brandwatch
1 crawler operated by Brandwatch
Who Brandwatch is, for site owners
Brandwatch operates 1 crawler in our directory, filed under Data Scrapers. Its crawl behaviour is rated caution.
Blocking Brandwatch carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Brandwatch: Consider blocking based on your content strategy.
Brandwatch at a glance
| Operator | Brandwatch |
|---|---|
| Crawler in directory | 1 |
| Categories | Data Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated caution |
| Official crawler docs | Brandwatch crawler documentation |
Crawler operated by Brandwatch
What Brandwatch's crawlers are for
Brandwatch runs 1 crawler in our database. Grouped by the job each one does:
- a utility crawler:
magpie-crawler
The highest-priority token is Tier 6. That makes Brandwatch a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Brandwatch
None of Brandwatch'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.
Writing one policy for Brandwatch
A robots.txt file cannot say "Brandwatch"; it can only name Brandwatch's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Brandwatch fetches through it
User-agent: magpie-crawler
Disallow: /private/
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the robots.txt AI crawler test after any change to see the result for each Brandwatch token, including firewall refusals.
Test yourself: does User-agent: Brandwatch block all of Brandwatch's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token magpie-crawler.
Test yourself: if you block one Brandwatch token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Brandwatch crawler, explained
A one-paragraph brief for every Brandwatch token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- magpie-crawler (
magpie-crawler, Tier 6): a utility crawler that harvests pages for a dataset or data product. Rated caution. magpie-crawler's operator does not clearly document how it treats robots.txt. Write the magpie-crawler rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.
Common mistakes with Brandwatch's crawlers
The errors we see most often with Brandwatch's crawlers in the files and firewalls we test:
- Treating Brandwatch's crawlers as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
- Relying on robots.txt alone when Brandwatch's crawlers is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Brandwatch's crawlers by IP alone. Ranges change; match the token and verify with logs.
All three hide inside a file that looks correct, so check Brandwatch's crawlers from outside after every change.
What our own data shows about Brandwatch
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 Brandwatch's marketing. Brandwatch has one token in our database, so the whole picture fits in one place.
magpie-crawler in our records
We first recorded magpie-crawler on March 17, 2026. Brandwatch documents it on brandwatch.com, and we recheck that page before each release. No file in our top-10,000 scans names magpie-crawler, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, magpie-crawler sits 24th 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 harvests pages for a dataset or data product: FirecrawlAgent (Firecrawl, Tier 2), iaskspider (iAsk, Tier 2), NovaAct (Amazon, Tier 2), CloudflareBrowserRenderingCrawler (Cloudflare, Tier 3), Amazon Kendra (Amazon, Tier 6). A policy for magpie-crawler is usually a policy for these too.
A decision record for magpie-crawler
Teams 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 magpie-crawler entry reads:
- Operator and job: Brandwatch; it harvests pages for a dataset or data product.
- Priority and behaviour: Tier 6, rated caution, blocking impact low.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: magpie-crawler's operator does not clearly document how it treats robots.txt. Write the magpie-crawler rule anyway, then confirm in your logs that its requests stop.
User-agent: magpie-crawler
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the magpie-crawler entry sooner than most: a caution rating means Brandwatch traffic deserves a monthly look at your logs.
Checking magpie-crawler on your own site
Because Brandwatch runs only magpie-crawler in our records, one check covers the whole operator. Search your access logs for the string magpie-crawler 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 Brandwatch 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.
How top sites treat Brandwatch's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Brandwatch'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 Brandwatch's crawlers too.
More questions about Brandwatch
- Will blocking Brandwatch affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Brandwatch's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Brandwatch?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Brandwatch on some sections and block it on others?
- Yes. Inside the group for
magpie-crawler, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Brandwatch delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Brandwatch offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Brandwatch?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Brandwatch review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI search crawlability check to see the outcome from outside, including any firewall layer.
How to block or allow Brandwatch in robots.txt
This rule covers the single crawler Brandwatch operates. Add it to the robots.txt file at the root of your domain.
Block Brandwatch completely
User-agent: magpie-crawler
Disallow: /
Allow Brandwatch explicitly
User-agent: magpie-crawler
Allow: /
These Brandwatch rules ask; they do not enforce. If a Brandwatch 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.
Frequently asked questions about Brandwatch
What crawler does Brandwatch run?
Brandwatch operates 1 crawler in our directory: magpie-crawler (user-agent magpie-crawler).
Should I block Brandwatch?
Consider blocking based on your content strategy. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block Brandwatch in robots.txt?
Add the following to robots.txt at your domain root: User-agent: magpie-crawler then Disallow: /.
Does blocking Brandwatch hurt my search rankings?
Blocking impact is rated: Low - No SEO ranking impact. Google's own ranking crawler is Googlebot, which this operator does not run, so blocking Brandwatch does not by itself remove you from Google's index. What it can change is whether AI assistants and analytics tools can read your pages.