MetricRaven

What is LinkupBot?

Linkup · Search indexes · User agent only

LinkupBot is Linkup's AI search crawler. Builds the Linkup web search index, which powers search and web grounding for AI applications.

A visit usually means: The page is being discovered or refreshed so it can appear in search or AI search results.

LinkUp, a job search company, runs a different crawler called LinkUpBot. Tokens match regardless of case, so its requests are counted here too.

LinkupBot user agent

The full user agent string, as Linkup publishes it:

  • User-Agent
    LinkupBot/1.0 (LinkupBot for web indexing; https://www.linkup.so/bot; bot@linkup.so)

Version numbers change, so match the token LinkupBot anywhere in the user agent, ignoring case. Source: Linkup's crawler documentation, checked Nov 18, 2026.

Reading the string

  • The published version is LinkupBot/1.0. Expect the number to change.
  • It has no browser parts (no Mozilla/5.0 prefix), so it's easy to tell apart from visitors.
  • It carries a link, https://www.linkup.so/bot, so anyone reading their logs can look the crawler up.
  • It includes a contact address, bot@linkup.so.

Paste a string from your logs into the user agent parser to see which crawler it is. New to the term? Read what a user agent is.

Block or allow LinkupBot in robots.txt

Linkup says LinkupBot follows robots.txt.

Block everywhere
robots.txt
User-agent: LinkupBot
Disallow: /
Keep out of a folder
robots.txt
User-agent: LinkupBot
Disallow: /private/
Allow
robots.txt
User-agent: LinkupBot
Allow: /

A crawler follows the most specific group that names it, so a rule here overrides your User-agent: * group for this crawler. Well-behaved crawlers re-read robots.txt within about a day.

LinkupBot and Linkup's other crawlers

Linkup runs 2 crawlers in this directory, each with its own robots.txt token and its own job. What blocking each one costs you:

  • LinkupBot · IndexingYour pages in Linkup's AI search answers
  • Linkup-User · AnswersLinkup's assistant reading your pages when someone asks about them

LinkupBot IP ranges and verification

Linkup publishes no IP ranges for LinkupBot, so requests are identified by user agent only and recorded as unverified. Anyone can send this user agent.

What LinkupBot means for your traffic and revenue

LinkupBot builds the index Linkup draws on for AI search answers. Blocking it can keep your pages out of those answers and the clicks they send.

Most crawlers never run JavaScript, so browser analytics can't see them, and the ones that do shouldn't count as visitors. MetricRaven's tracker ignores LinkupBot, and server-side crawl tracking shows which pages it reads instead. See Bots & AI crawlers.

Questions

What is LinkupBot?
Builds the Linkup web search index, which powers search and web grounding for AI applications. MetricRaven groups it under Search indexes: search engines and AI search keeping their index fresh.
What is the LinkupBot user agent?
Linkup documents this user agent: "LinkupBot/1.0 (LinkupBot for web indexing; https://www.linkup.so/bot; bot@linkup.so)". Match the token "LinkupBot" rather than the whole string, because version numbers change.
How do I block LinkupBot in robots.txt?
Add "User-agent: LinkupBot" followed by "Disallow: /" to your robots.txt. Linkup says LinkupBot follows robots.txt.
Does LinkupBot publish IP ranges?
No. Linkup publishes no IP ranges for LinkupBot, so only the user agent identifies it, and anyone can send that string.
Is LinkupBot safe?
The real LinkupBot only requests public pages, and Linkup documents it. The risk is impostors using its name. Whether to allow it depends on what you get back: the page is being discovered or refreshed so it can appear in search or AI search results.
What other crawlers does Linkup run?
Linkup-User (AI assistant). Each has its own robots.txt token, and each does a different job.

See when AI assistants and crawlers read your site

Add one line to your server and MetricRaven shows which assistants, search engines and training crawlers request your pages, which ones are IP-verified, and the URLs they expected to find, including 404s.