The direct answer: Write your hook for the first 90 minutes, not for the algorithm's "ideal" structure. LinkedIn shows each post to a slice of your first-degree network first, and what that slice does in roughly the opening 90 minutes decides whether the feed expands it further. A hook that works names a specific audience, makes a checkable claim or takes a visible stance, and delivers the core thesis before the "see more" fold cuts the text off on mobile. If the payoff sits below that fold, dwell time dies — and dwell time is the quality signal the feed watches most closely.

Why most hooks die in the first seconds

The scroll is brutal. Your post first shows up in front of a slice of your network, and how that slice reacts decides whether the feed shows it to anyone else. Richard van der Blom's annual analyses of LinkedIn reach — he tracks the platform across large samples of posts — consistently find the same pattern: a post people scroll past in the first couple of seconds gets buried, while one that earns a longer read gets treated as high-quality and boosted.

Most hooks fail because they commit one of three sins:

Sin one: The throat-clear. "I'm excited to share..." "Today I want to talk about..." These tell the reader nothing and waste the only real estate that matters.

Sin two: The generic audience. "Attention everyone!" — everyone is no one. The relevance model needs to categorize your post, and it can't when the hook fits any topic in any industry.

Sin three: The buried payoff. A compelling story that doesn't land its point until paragraph four is a story nobody reads. The "see more" fold on mobile cuts posts off around 150 characters in the initial preview. If the thesis isn't visible in that window, the swipe happens.

What a scroll-stopping hook looks like

Concrete beats generic. Here's the worst (and most common) hook pattern:

"In today's fast-paced digital world, LinkedIn has become an essential tool for professionals looking to grow their network and advance their careers. In this post, I'll share some tips..."

What's wrong with it? Every sentence is a cliché. "Fast-paced digital world" tells the reader nothing. "In this post, I'll share" is a promise, not a payoff. Three sentences in, the reader has learned zero facts, encountered zero stakes, and has no reason to continue.

Now the best (and rarest) version:

"Your sitemap is on http — that's why Google hasn't indexed a single page of your new site."

Why was this version better? It names a specific problem (the http vs https issue), names the consequence (no indexing), and implies the reader's situation without a single wasted word. A marketing manager who just launched a site will stop. A web developer will stop. Even someone who's never touched a sitemap understands something broke.

The second hook works because it follows a simple test: could this sentence appear in a post about any other topic? If yes, it's too generic. The sitemap hook could only appear in a post about technical SEO.

Write the hook inside the first 210 characters

The first 210 characters of your post body (roughly 150 on mobile before the fold) carry the entire weight of your distribution. Write the hook first, then build the post around it.

The mechanism: LinkedIn's relevance model reads the opening lines to categorize your post. If the first three lines name your topic and your audience, the model knows where to route it. If they don't, the post drifts into the void.

The checklist for a 210-character hook:

  • Name the audience. "If you run a B2B newsletter..." beats "Hey everyone."
  • State a checkable fact or mechanism. "LinkedIn caps free posts at 3,000 characters" is verifiable. "Networking is everything" is not.
  • Take a side. Neutral posts get fewer comments. "Most LinkedIn hooks fail because they're written for the algorithm, not the reader" invites argument.
  • Front-load the thesis. The reader should know what the post is about by line two.

A practical exercise: write your hook, then delete the first sentence. If the post still makes sense, the first sentence wasn't doing its job.

A bad example, annotated

Let's annotate two real hook styles line by line.

Bad example:

"Networking is so important for career growth! I've met so many amazing people through LinkedIn. Here are some thoughts on how to connect with others."

What's wrong with it?

  • "Networking is so important" — a claim with no mechanism. Why is it important? What does it do?
  • "I've met so many amazing people" — a vague personal claim with no specificity. How many? In what context?
  • "Here are some thoughts" — a promise to maybe deliver value someday.

Good example:

"I sent 47 cold outreach messages last month. 12 got replies. 3 turned into calls. 1 became a client. The subject line that worked? The one that named a specific problem their company posted about on LinkedIn."

Why was this version better?

  • It leads with a specific number pattern (47, 12, 3, 1) that the reader can check against their own experience.
  • It names the mechanism (a subject line referencing a company's own post) rather than a vague principle.
  • It creates a curiosity gap (what was the subject line?) that pulls the reader into the body.

The annotation rule: every line of a good hook either states a fact, names a mechanism, or takes a stance. If a line does none of those three, cut it.

The 7 opening lines that stop the scroll

Across the analyses that track LinkedIn engagement, saves consistently outrank comments, comments outrank shares, and shares outrank likes. Each is a different level of intent: a save says "I need to come back to this"; a like says "that's nice." Write the hook to earn the stronger reaction, and these seven lines are the shapes that do it.

  1. The checkable-fact opener. "Shopify's cheapest paid plan starts at $39/month — confirm current pricing before you commit." Verification builds trust; trust builds dwell time.
  2. The counter-intuitive mechanism. "This gets slower the more people you add — here's why." The brain stops on the mismatch between expectation (more people = more progress) and reality.
  3. The first-person stance. "I used to believe posting daily was the only way to grow on LinkedIn. I was wrong." A confession reads like a person, not a company page, and it invites pushback.
  4. The number funnel. Lead with your own result count, descending: "I sent 47 cold outreach emails last month. 12 replied. 3 booked calls. 1 signed." The pattern makes the reader ask what the winner said — just use real numbers from your own logs; an invented funnel is the fastest way to lose trust.
  5. The named-audience line. "If you run a B2B newsletter, the next 210 characters decide whether this post gets read at all." Naming the reader tells the relevance model where to route the post and tells the reader it's for them.
  6. The direct question with stakes. "Why do most cold pitches get ignored before the second sentence?" A specific question opens a loop the reader needs closed.
  7. The specific failure you fixed. "Your sitemap is on http — that's why Google hasn't indexed a single page of your new site." One concrete cause, one concrete consequence; anyone who has launched a site stops.

Avoid the three openers that burn the same window: the invented statistic ("90% of professionals..."), the motivational aphorism ("Success leaves clues."), and the humble brag ("Humbled to announce..."). None of them name a mechanism, and all three read as recycled.

Test the hook before you post

You can't A/B test a LinkedIn post the way you'd test a landing page. But you can run a 60-second self-check before publishing.

The three-question test:

  1. Could this hook appear in a post about any other topic? If yes, rewrite. Specificity is the entire game.
  2. Does the reader know who this is for within the first two lines? If the audience isn't named or implied, the relevance model can't route the post.
  3. Is there a reason to save this beyond the hook itself? The hook earns the read; the body earns the save. If the body is generic advice, the save never happens.

The timing test: the first hour is when the feed decides. Posts that pick up a few genuine comments fast tend to travel further, and answering every early reply keeps the thread alive. Your hook needs to be strong enough to start that conversation — which means ending the post with a specific, low-friction question, not a generic "thoughts?"

The catch: a great hook gets the click, but it can't save a post that doesn't deliver. If the body doesn't match the promise of the hook, the reader bounces, dwell time collapses, and the post dies in the test window. The hook and the body are one system.

If you remember nothing else

  • The first 210 characters decide distribution. Front-load the thesis before the "see more" fold cuts the post off on mobile.
  • Saves are the strongest engagement signal. Write at least one part people want to return to — a framework, a checklist, a specific data point.
  • Early comments matter most. End with a specific question that invites a real reply, then answer every reply while the thread is young.
  • Specificity beats generality. "We cut demo-request time 34% in Q1" outperforms "here are tips for better demos."
  • Stay in one lane. Posts aligned with your stated professional domain get amplified; off-topic posts get suppressed even with strong engagement.
  • Never invent a statistic. A checkable fact with a named source beats a plausible-sounding number every time.

FAQ

How long should a LinkedIn hook be? Aim for the first 210 characters of the post body (roughly 150 characters on mobile before the fold). The hook should state the thesis and name the audience within that window.

Should I write the hook first or the body first? Write the hook first. It forces you to clarify the thesis before you write anything else. If you can't articulate the core claim in one or two sentences, the body will wander.

Do hashtags matter for reach? Use one or two industry-relevant hashtags maximum. Hashtag stacks are a signal of low-quality content, and the algorithm doesn't reward them.

Should I include a link in the post body? No. External links carry a distribution penalty. Put links in the first comment.

How often should I post to build topic authority? Consistency matters more than frequency. Posting three to four times per week about one professional domain builds algorithmic recognition of your expertise faster than daily posting about random topics.

What's the single biggest mistake people make? Writing hooks that could apply to any topic. If your hook doesn't name a specific audience and a specific problem, it's not a hook — it's noise.