ImagesiftBot
SafeUser-agent: ImagesiftBot
Category: Data Scrapers
SEO impact if blocked: 2/10
Unattributed crawlers
1 crawler with no publicly identified operator
Who runs these crawlers
These 1 crawlers have no publicly identified operator. The user-agent token appears in server logs, but the company or project behind it does not document the crawler or claim it publicly. Treat unattributed traffic more cautiously than a named operator: you cannot check a published crawl policy, and there is no documented contact for crawl-rate complaints.
Each one is still listed individually below with its verified user-agent string and blocking impact, so you can decide per bot rather than blocking a whole unknown group.
This group at a glance
| Operator | Unattributed |
|---|---|
| Crawler in directory | 1 |
| Categories | Data Scrapers |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
| Official crawler docs | Unattributed crawler documentation |
Crawler in this group
What Unattributed's crawlers are for
Unattributed runs 1 crawler in our database. Grouped by the job each one does:
- a utility crawler:
ImagesiftBot
The highest-priority token is Tier 6. That makes Unattributed a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Unattributed
None of Unattributed'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 Unattributed
A robots.txt file cannot say "Unattributed"; it can only name Unattributed's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Unattributed fetches through it
User-agent: ImagesiftBot
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 crawler access checker after any change to see the result for each Unattributed token, including firewall refusals.
Test yourself: does User-agent: Unattributed block all of Unattributed's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token ImagesiftBot.
Test yourself: if you block one Unattributed token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Unattributed crawler, explained
A one-paragraph brief for every Unattributed token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- ImagesiftBot (
ImagesiftBot, Tier 6): a utility crawler that harvests pages for a dataset or data product. Rated safe. ImagesiftBot's operator says it follows robots.txt, so a correctly written ImagesiftBot group is enough to control it. Not tracked in our robots.txt study.
Common mistakes with Unattributed's crawlers
The errors we see most often with Unattributed's crawlers in the files and firewalls we test:
- Treating Unattributed'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 Unattributed's crawlers is rated caution or aggressive. Back the rule with a server-side block.
- Blocking Unattributed'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 Unattributed's crawlers from outside after every change.
What our own data shows about Unattributed
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 Unattributed's marketing. Unattributed has one token in our database, so the whole picture fits in one place.
ImagesiftBot in our records
We first recorded ImagesiftBot on March 17, 2026. Unattributed documents it on imagesift.com, and we recheck that page before each release. No file in our top-10,000 scans names ImagesiftBot, so any rule you write for it puts you ahead of almost every large site.
Among the 39 data scrapers in our database, ImagesiftBot sits 20th 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 ImagesiftBot is usually a policy for these too.
A decision record for ImagesiftBot
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 ImagesiftBot entry reads:
- Operator and job: Unattributed; 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: ImagesiftBot's operator says it follows robots.txt, so a correctly written ImagesiftBot group is enough to control it.
User-agent: ImagesiftBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the ImagesiftBot entry once a quarter, or when Unattributed publishes a new token next to it.
Checking ImagesiftBot on your own site
Because Unattributed runs only ImagesiftBot in our records, one check covers the whole operator. Search your access logs for the string ImagesiftBot 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 Unattributed publishes about the crawler, since that page is the only authority on its behaviour. 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 Unattributed'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 Unattributed'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 Unattributed's crawlers too.
More questions about Unattributed
- Will blocking Unattributed affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Unattributed's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Unattributed?
- 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 Unattributed on some sections and block it on others?
- Yes. Inside the group for
ImagesiftBot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Unattributed delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Unattributed offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Unattributed?
- 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 Unattributed 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 live AI crawler test to see the outcome from outside, including any firewall layer.
How to block or allow these crawlers in robots.txt
This rule covers the single crawler in this group. Add it to the robots.txt file at the root of your domain.
Block Unattributed completely
User-agent: ImagesiftBot
Disallow: /
Allow Unattributed explicitly
User-agent: ImagesiftBot
Allow: /
These Unattributed rules ask; they do not enforce. If a Unattributed 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 unattributed crawlers
Which crawlers have no identified operator?
These 1 crawlers are grouped as unattributed because no operator is publicly identified for them: ImagesiftBot.
Should I block crawlers with no identified operator?
Decide per crawler rather than as a group, since these 1 share only the fact that no operator is publicly identified for them. The caution is that you cannot check a published crawl policy or contact anyone about crawl rate. Each crawler's own page, linked in the list above, carries its verified user-agent token, safety rating and blocking impact.
How do I block these crawlers in robots.txt?
Add the following to robots.txt at your domain root: User-agent: ImagesiftBot then Disallow: /.
Does blocking these crawlers 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 these crawlers 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.