Kangaroo

1 crawler operated by Kangaroo

Who Kangaroo is, for site owners

Kangaroo operates 1 crawler in our directory, filed under Scrapers. Its crawl behaviour is rated safe.

Blocking Kangaroo carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.

Our recommendation for Kangaroo: Generally safe to allow; provides legitimate crawling value.

Kangaroo at a glance

OperatorKangaroo
Crawler in directory1
CategoriesScrapers
SEO impact if blocked2/10
Crawl behaviour1 rated safe

Crawler operated by Kangaroo

What Kangaroo's crawlers are for

Kangaroo runs 1 crawler in our database. Grouped by the job each one does:

  • a utility crawler: Kangaroo Bot

The highest-priority token is Tier 6. That makes Kangaroo a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.

How site owners treat Kangaroo

How often site owners write rules for Kangaroo's tokens, from our own robots.txt study of the Tranco top 10,000:

Kangaroo tokens named and blocked in top-site robots.txt files
TokenFiles naming itFiles blocking it
Kangaroo Bot168 (3%)Not measured

A Kangaroo token can be blocked without being named, through a User-agent: * group with Disallow: /, so its blocking share can be higher than its naming share.

All counts come from 5,583 valid files fetched October 20, 2026.

Writing one policy for Kangaroo

A robots.txt file cannot say "Kangaroo"; it can only name Kangaroo's tokens, one group at a time. With a single token, one group is the whole policy.

# One token controls everything Kangaroo fetches through it
User-agent: Kangaroo Bot
Disallow: /private/
Allow: /
  1. Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
  2. Name every token you mean. A token you leave out follows User-agent: *.
  3. Repeat shared rules. A named group ignores the * group, so copy any Disallow lines you still want it to obey.
  4. Verify from outside. Run the AI search crawlability check after any change to see the result for each Kangaroo token, including firewall refusals.
Test yourself: does User-agent: Kangaroo block all of Kangaroo's crawlers?

No. robots.txt matches crawler tokens, not company names. Use the token Kangaroo Bot.

Test yourself: if you block one Kangaroo token, are the others blocked too?

No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.

Each Kangaroo crawler, explained

A one-paragraph brief for every Kangaroo token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:

  • Kangaroo Bot (Kangaroo Bot, Tier 6): a utility crawler that harvests pages for a dataset or data product. Rated safe. Kangaroo Bot's operator does not clearly document how it treats robots.txt. Write the Kangaroo Bot rule anyway, then confirm in your logs that its requests stop. 3% of top-site robots.txt files name it.

Common mistakes with Kangaroo's crawlers

The errors we see most often with Kangaroo's crawlers in the files and firewalls we test:

  1. Treating Kangaroo'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.
  2. Relying on robots.txt alone when Kangaroo's crawlers is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking Kangaroo'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 Kangaroo's crawlers from outside after every change.

What our own data shows about Kangaroo

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 Kangaroo's marketing. Kangaroo has one token in our database, so the whole picture fits in one place.

Kangaroo Bot in our records

We first recorded Kangaroo Bot on March 17, 2026. We could not find a page where Kangaroo names it, so treat the token as reported rather than documented. Kangaroo Bot is outside our tracked token set, but 168 of 5,583 top-site files already name it, which is enough to show owners treat it as a real crawler.

Among the 39 data scrapers in our database, Kangaroo Bot sits 23th by priority (Tier 6), level with Amazon Kendra, ApifyBot, Barkrowler, BLEXBot. 29 of the 39 share its safe 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 Kangaroo Bot is usually a policy for these too.

A decision record for Kangaroo Bot

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 Kangaroo Bot entry reads:

  • Operator and job: Kangaroo; it harvests pages for a dataset or data product.
  • Priority and behaviour: Tier 6, rated safe, blocking impact low.
  • Suggested starting point: Allow by default; revisit if it costs you bandwidth.
  • Enforcement: Kangaroo Bot's operator does not clearly document how it treats robots.txt. Write the Kangaroo Bot rule anyway, then confirm in your logs that its requests stop.
User-agent: Kangaroo Bot
Allow: /

Paste the line into the validator with one of your own URLs before it goes live. Revisit the Kangaroo Bot entry once a quarter, or when Kangaroo publishes a new token next to it.

Checking Kangaroo Bot on your own site

Because Kangaroo runs only Kangaroo Bot in our records, one check covers the whole operator. Search your access logs for the string Kangaroo Bot 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. Kangaroo publishes no page about the crawler that we could find, so judge it by the requests you actually see rather than by its name. A Tier 6 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.

How top sites treat Kangaroo'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 Kangaroo'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 Kangaroo's crawlers too.

More questions about Kangaroo

Will blocking Kangaroo affect my Google rankings?
Only if one of its tokens is a Google search crawler. None of Kangaroo's tokens are Googlebot, so classic Google rankings are unaffected.
How quickly does a robots.txt change take effect for Kangaroo?
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 Kangaroo on some sections and block it on others?
Yes. Inside the group for Kangaroo Bot, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.
Does blocking Kangaroo delete content it already collected?
No. robots.txt only controls future visits. For content already collected, check whether Kangaroo offers a removal or opt-out process.
Is a firewall block better than robots.txt for Kangaroo?
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 Kangaroo review

  1. 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.
  2. Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
  3. Write the group. Add or edit one User-agent group per decision and repeat any shared rules inside it.
  4. Publish and wait. Allow about a day for crawlers to fetch the new file.
  5. Confirm the result. Check your logs, then run the blocked AI crawler check to see the outcome from outside, including any firewall layer.

How to block or allow Kangaroo in robots.txt

This rule covers the single crawler Kangaroo operates. Add it to the robots.txt file at the root of your domain.

Block Kangaroo completely
User-agent: Kangaroo Bot Disallow: /
Allow Kangaroo explicitly
User-agent: Kangaroo Bot Allow: /

These Kangaroo rules ask; they do not enforce. If a Kangaroo 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 Kangaroo

What crawler does Kangaroo run?
Kangaroo operates 1 crawler in our directory: Kangaroo Bot (user-agent Kangaroo Bot).
Should I block Kangaroo?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block Kangaroo in robots.txt?
Add the following to robots.txt at your domain root: User-agent: Kangaroo Bot then Disallow: /.
Does blocking Kangaroo 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 Kangaroo 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.
WhatsApp us