LinkupBot user agent
Operated by Linkup
LinkupBot is a crawler reported for Linkup, a web search API for AI applications.
The LinkupBot bot at a glance
- LinkupBot is operated by Linkup and indexes web pages so an AI search product can show and cite them in answers.
- The robots.txt token for LinkupBot is LinkupBot.
- Blocking an AI search crawler has no effect on Google or Bing rankings.
- LinkupBot robots.txt support: Not documented.
- Recommendation for Generative Engine Optimization (GEO): Allow.
What is LinkupBot?
Linkup provides search results to AI products, so its index reaches several AI tools.
Linkup has not published a crawler page.
Should you block LinkupBot?
Allow LinkupBot unless it causes a measurable load problem.
| Effect on search rankings | Blocking an AI search crawler has no effect on Google or Bing rankings. |
|---|---|
| Effect on AI visibility | Blocking removes your pages from that AI search index, so its answers can no longer cite or link to your website. |
| Follows robots.txt | Not documented |
| Recommendation | Allow |
How to block or allow LinkupBot
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token LinkupBot is matched case-insensitively. robots.txt alone may not stop LinkupBot, so add the Nginx, Apache or Cloudflare rule as well.
robots.txt: block
# Block LinkupBot
User-agent: LinkupBot
Disallow: /robots.txt: allow
# Allow LinkupBot
User-agent: LinkupBot
Allow: /robots.txt: partial
# Keep LinkupBot out of private areas only
User-agent: LinkupBot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to LinkupBot
if ($http_user_agent ~* "(LinkupBot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to LinkupBot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (LinkupBot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "LinkupBot")How to verify real LinkupBot traffic
Linkup publishes no IP list or reverse DNS pattern for LinkupBot, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find LinkupBot in your server logs
Search the web server access log for the token. The command below counts LinkupBot requests per URL on Nginx or Apache.
grep -i "LinkupBot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
LinkupBot FAQ
LinkupBot uses the robots.txt token "LinkupBot". Linkup does not publish a full user-agent string, so match the token inside the User-Agent header.
Linkup has not documented how LinkupBot treats robots.txt. Add a robots.txt rule and back it with a server rule if the traffic matters to you.
Blocking an AI search crawler has no effect on Google or Bing rankings. Blocking removes your pages from that AI search index, so its answers can no longer cite or link to your website.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: LinkupBot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Linkup publishes no IP list or reverse DNS pattern for LinkupBot, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "LinkupBot", for example with: grep -i "LinkupBot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Public bot registry. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
