AI search crawlers
LinkupBot is a bot operated by Linkup that indexes pages so an AI answer engine can cite them. LinkupBot crawls pages for Linkup, a paid search API that returns grounded web results to AI applications. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"LinkupBot"
Checked against
Nothing published
Live check
No operator check exists for LinkupBot. This still shows what the address really is.
Reference
| User agent | LinkupBotToken only: match on the substring. |
|---|---|
| Operator | Linkup |
| Purpose | AI search crawlers |
| Respects robots.txt | No policy |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | LinkupBot |
| Operator documentation | None published |
LinkupBot crawls pages for Linkup, a paid search API that returns grounded web results to AI applications.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: LinkupBot
Disallow: /User-agent: LinkupBot
Allow: /User-agent: LinkupBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking LinkupBot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.
Build a file for every crawlerFAQ
LinkupBot is a bot operated by Linkup that indexes pages so an AI answer engine can cite them. LinkupBot crawls pages for Linkup, a paid search API that returns grounded web results to AI applications. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Not documented. No operator statement says whether LinkupBot reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the LinkupBot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking LinkupBot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.