Starsky
← Back to signals

MARKET SIGNAL

On LinkedIn, ask for the denominator before the number: the same engagement rate differs fivefold by company size

Verdict
Check now
Event date
2026-09
Published
2026-11-10
Last verified
2026-11-10

Check now

Before using any benchmark, confirm the denominator (impressions / reach / followers), then benchmark against your own size tier.

What happened

01What happened

Socialinsider analysed 1.3 million business-page posts (16,645 pages) from January 2024 to December 2025: overall engagement rate 5.20% (engagements/impressions), up 8% year over year. By format: native documents 7.00%, multi-image 6.45%, video 6.00%, text-only 4.50%, polls 4.20%, link posts 3.25%. Average video views fell 36% year on year.

Oktopost’s Q1 2026 report (1,000+ anonymised B2B pages): the median page earns 911 impressions and 48 engagements per post; pages with 1K–5K followers show a 5.42% median engagement rate, pages above 500K only 1.08%.

Personal profiles are not the same system: across analyses, the same content on a personal profile earns roughly 2.75x the organic impressions of a company page — employee and executive reposts remain the largest free amplifier outside the page itself.

02Who this affects

Teams that report LinkedIn performance to leadership on a regular cadence.

Anyone benchmarking their page directly against numbers quoted in an agency deck.

03What it may change

Denominator mismatch is the most common self-deception: most B2B analytics tools compute engagement over impressions while LinkedIn’s native page analytics computes it over followers. The same page can report “8% (by followers)” and “under 1% (by impressions)” — and the gap widens once paid amplification enters. Agree the definition first, performance second.

The platform also rewards quality over volume: saves and dwell time outweigh likes, and five substantive comments outrank fifty generic reactions. Link posts bottoming out (3.25%) while documents lead (7.00%) shows that format itself is a variable — sometimes the shell, not the content, is the problem.