LinkedIn

Common mistakes with LinkedIn's crawlers

The errors we see most often with LinkedIn's crawlers in the files and firewalls we test:

1. Treating LinkedIn's crawlers as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
2. Relying on robots.txt alone when LinkedIn's crawlers is rated caution or aggressive. Back the rule with a server-side block.
3. Blocking LinkedIn's crawlers by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check LinkedIn's crawlers from outside after every change.

What our own data shows about LinkedIn

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 LinkedIn's marketing. LinkedIn has one token in our database, so the whole picture fits in one place.

LinkedInBot in our records

We first recorded LinkedInBot on March 17, 2026. LinkedIn documents it on linkedin.com, and we recheck that page before each release. No file in our top-10,000 scans names LinkedInBot, so any rule you write for it puts you ahead of almost every large site.

Among the 9 social preview bots in our database, LinkedInBot sits fourth by priority (Tier 5), level with FacebookBot, facebookexternalhit, Pinterestbot, Quora-Bot. 9 of the 9 share its safe rating. Other operators with a crawler that fetches a page to build a link preview when someone shares it: MicrosoftPreview (Microsoft, Tier 3), FacebookBot (Meta, Tier 5), facebookexternalhit (Meta, Tier 5), GoogleMessages (Google, Tier 5), Pinterestbot (Pinterest, Tier 5). A policy for LinkedInBot is usually a policy for these too.

A decision record for LinkedInBot

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 LinkedInBot entry reads:

• Operator and job: LinkedIn; it fetches a page to build a link preview when someone shares it.
• Priority and behaviour: Tier 5, rated safe, blocking impact not documented.
• Suggested starting point: Allow by default; revisit if it costs you bandwidth.
• Enforcement: LinkedInBot's operator does not clearly document how it treats robots.txt. Write the LinkedInBot rule anyway, then confirm in your logs that its requests stop.

User-agent: LinkedInBot
Allow: /

Paste the line into the validator with one of your own URLs before it goes live. Revisit the LinkedInBot entry once a quarter, or when LinkedIn publishes a new token next to it.

Checking LinkedInBot on your own site

Because LinkedIn runs only LinkedInBot in our records, one check covers the whole operator. Search your access logs for the string LinkedInBot 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 LinkedIn publishes about the crawler, since that page is the only authority on its behaviour. A Tier 5 crawler rated safe rarely needs more than a quarterly look, and our log checker does the counting for you.

How top sites treat LinkedIn'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 LinkedIn'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 LinkedIn's crawlers too.

More questions about LinkedIn

Will blocking LinkedIn affect my Google rankings?

Only if one of its tokens is a Google search crawler. None of LinkedIn's tokens are Googlebot, so classic Google rankings are unaffected.

How quickly does a robots.txt change take effect for LinkedIn?

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 LinkedIn on some sections and block it on others?

Yes. Inside the group for LinkedInBot, add Disallow lines for the paths to keep private and Allow lines for exceptions. The longest matching rule wins.

Does blocking LinkedIn delete content it already collected?

No. robots.txt only controls future visits. For content already collected, check whether LinkedIn offers a removal or opt-out process.

Is a firewall block better than robots.txt for LinkedIn?

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.