Linkup Search
SafeUser-agent: LinkupBot
Category: AI & LLM Bots
SEO impact if blocked: 2/10
Linkup
1 crawler operated by Linkup
https://www.linkup.so/Who Linkup is, for site owners
Linkup operates 1 crawler in our directory, filed under AI & LLM Bots. Its crawl behaviour is rated safe.
Blocking Linkup carries an SEO impact score of 2/10. Blocking impact is rated: Low - No SEO ranking impact.
Our recommendation for Linkup: Generally safe to allow; provides legitimate crawling value.
Linkup at a glance
| Operator | Linkup |
|---|---|
| Crawler in directory | 1 |
| Categories | AI & LLM Bots |
| SEO impact if blocked | 2/10 |
| Crawl behaviour | 1 rated safe |
| Website | www.linkup.so |
| Official crawler docs | Linkup crawler documentation |
Crawler operated by Linkup
What Linkup's crawlers are for
Linkup runs 1 crawler in our database. Grouped by the job each one does:
- a retrieval crawler that feeds AI search answers:
LinkupBot
The highest-priority token is Tier 2. That puts Linkup among the operators whose crawlers have a direct effect on whether AI answers or search results can include your pages.
How site owners treat Linkup
None of Linkup'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 Linkup
A robots.txt file cannot say "Linkup"; it can only name Linkup's tokens, one group at a time. With a single token, one group is the whole policy.
# One token controls everything Linkup fetches through it
User-agent: LinkupBot
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 AI bot checker after any change to see the result for each Linkup token, including firewall refusals.
Test yourself: does User-agent: Linkup block all of Linkup's crawlers?
No. robots.txt matches crawler tokens, not company names. Use the token LinkupBot.
Test yourself: if you block one Linkup token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Linkup crawler, explained
A one-paragraph brief for every Linkup token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Linkup Search (
LinkupBot, Tier 2): a retrieval crawler that feeds AI search answers that builds a search or answer index. Rated safe. Linkup Search's operator does not clearly document how it treats robots.txt. Write the Linkup Search rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.
Common mistakes with Linkup's crawlers
The errors we see most often with Linkup's crawlers in the files and firewalls we test:
- Blocking Linkup's crawlers while trying to stop AI training. Retrieval crawlers fetch pages so answers can cite them; blocking it can remove you from those answers without affecting training.
- Letting a firewall or bot-fight mode refuse Linkup's crawlers while robots.txt allows it. The file looks right, but the crawler still gets a 403 or a challenge page.
- Forgetting that once a
User-agent: LinkupBotgroup exists, Linkup's crawlers ignores every rule underUser-agent: *.
All three hide inside a file that looks correct, so check Linkup's crawlers from outside after every change.
What our own data shows about Linkup
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 Linkup's marketing. Linkup has one token in our database, so the whole picture fits in one place.
LinkupBot in our records
We first recorded LinkupBot on June 18, 2026. Linkup documents it on linkup.so, and we recheck that page before each release. No file in our top-10,000 scans names LinkupBot, so any rule you write for it puts you ahead of almost every large site.
Among the 104 AI and LLM crawlers in our database, LinkupBot sits 61th by priority (Tier 2), level with AddSearchBot, AI2Bot, AI2Bot-DeepResearchEval, aiHitBot. 81 of the 104 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for LinkupBot is usually a policy for these too.
A decision record for LinkupBot
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 LinkupBot entry reads:
- Operator and job: Linkup; it builds a search or answer index.
- Priority and behaviour: Tier 2, rated safe, blocking impact low.
- Suggested starting point: Allow, and watch it in your logs.
- Enforcement: LinkupBot's operator does not clearly document how it treats robots.txt. Write the LinkupBot rule anyway, then confirm in your logs that its requests stop.
User-agent: LinkupBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the LinkupBot entry whenever Linkup announces a change, because a Tier 2 crawler affects visibility directly.
Checking LinkupBot on your own site
Because Linkup runs only LinkupBot in our records, one check covers the whole operator. Search your access logs for the string LinkupBot 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 Linkup publishes about the crawler, since that page is the only authority on its behaviour. A Tier 2 crawler rated safe is worth confirming every month, and our log checker does the counting for you.
How top sites treat Linkup'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 Linkup'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 Linkup's crawlers too.
More questions about Linkup
- Will blocking Linkup affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Linkup's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Linkup?
- 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 Linkup on some sections and block it on others?
- Yes. Inside the group for
LinkupBot, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Linkup delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Linkup offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Linkup?
- 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 Linkup 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 AI search visibility check to see the outcome from outside, including any firewall layer.
How to block or allow Linkup in robots.txt
This rule covers the single crawler Linkup operates. Add it to the robots.txt file at the root of your domain.
Block Linkup completely
User-agent: LinkupBot
Disallow: /
Allow Linkup explicitly
User-agent: LinkupBot
Allow: /
These Linkup rules ask; they do not enforce. If a Linkup 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 Linkup
What crawler does Linkup run?
Linkup operates 1 crawler in our directory: Linkup Search (user-agent LinkupBot).
Should I block Linkup?
Generally safe to allow; provides legitimate crawling value. The SEO impact score for blocking is 2/10, where 10 means blocking costs you the most visibility.
How do I block Linkup in robots.txt?
Add the following to robots.txt at your domain root: User-agent: LinkupBot then Disallow: /.
Does blocking Linkup 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 Linkup 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.