Linkup bots
The crawler and on-demand fetcher behind Linkup.
Loading document…
SPARSEUP is live - Linkup's powerful open-source sparse embedding model. Try it →
The crawler and on-demand fetcher behind Linkup.
Loading document…
Linkup operates two bots. Each identifies itself in its HTTP User-Agent header and sends requests from its own published IP ranges.
Requests from LinkupBot contain the following user-agent token:
LinkupBot
An example complete user-agent is:
LinkupBot/1.0 (LinkupBot for web indexing; https://www.linkup.so/bot; bot@linkup.so)
LinkupBot requests originate from the CIDR ranges published at: https://www.linkup.so/linkupbot-ips.txt
Requests from Linkup-User contain the following user-agent token:
Linkup-User
An example complete user-agent is:
Linkup-User/1.0 (+https://www.linkup.so/bot; bot@linkup.so)
Linkup-User requests originate from the CIDR ranges published at: https://www.linkup.so/linkup-user-ips.txt
Because user-agent headers can be spoofed, verify traffic from a Linkup bot using both:
The IP lists may change. Systems that automate allowlisting should retrieve them periodically.
LinkupBot respects applicable robots.txt rules.
Place robots.txt at the root of each host you want to control, for example:
https://example.com/robots.txt
Rules apply only to the corresponding host, protocol, and port. Separate subdomains may need their own robots.txt.
User-agent: LinkupBot
Disallow: /
User-agent: LinkupBot
Disallow: /private/
Disallow: /drafts/
Disallow: /internal-document.pdf
User-agent: LinkupBot
Disallow: /
Allow: /public/
Crawling is allowed by default when no applicable rule prohibits it. To allow LinkupBot while blocking other crawlers:
User-agent: *
Disallow: /
User-agent: LinkupBot
Allow: /
Allowing LinkupBot through a firewall or WAF does not override robots.txt. Both the network policy and the applicable robots rules must permit access.
robots.txt is not an access-control mechanism. Protect confidential content with authentication or other server-side controls.
To allow a Linkup bot through a firewall, CDN, or WAF:
LinkupBot or Linkup-User.For the strongest verification, require both the published source IP and user-agent conditions.
Questions or concerns about Linkup bots can be sent to bot@linkup.so.
Please include the requested URL, timestamp and timezone, source IP, complete user-agent, and relevant server-log entries.