How to write a LinkedIn hook
Updated by the Inkpost team
A LinkedIn hook is the opening line of a post, the part readers see before “…see more”. A good hook states something specific (a result, a mistake, a number or a clear opinion) for a named audience, in under about 140 characters so it shows in full on mobile. It gives a reason to click without giving away the whole post.
Why the hook matters more than the rest
The LinkedIn feed shows roughly the first 140 characters of a post on mobile and 210 on desktop, or three lines, before it cuts to “…see more”. Our guide to the “see more” character limit sets out the measurements. Everything a scrolling reader knows about your post comes from that slice.
So the hook does not need to be clever. It needs to tell the right reader, quickly, that the rest of the post is for them and worth the click.
A six-step method
- Write the post first. It is much easier to write the opening line once you know what the post says. Many writers draft the body, then write the hook last.
- Find the single most useful sentence. Usually it is the result, the lesson or the surprising fact. That sentence, or a version of it, is your hook.
- Make it specific. Replace general words with a number, a timeframe, a name or a concrete detail. “We cut onboarding from 14 days to 3” beats “We improved onboarding”.
- Say who it is for. Naming the audience (“for first-time managers”, “if you sell to hospitals”) helps those readers recognise the post as theirs.
- Fit it in 140 characters. Count it. If it runs over, cut words before you cut the specific detail. Keep it on one line: a line break uses a third of the visible space.
- Leave the how for the body. State the result or the problem; keep the explanation below the cut. That gap is the reason to click.
18 hook formulas, with examples
These are the formulas in the Inkpost extension’s Hooks menu. Square brackets are the parts you fill in. The examples are illustrations, not real results; use your own numbers.
| Formula | Template | Example |
|---|---|---|
| Result + timeframe | We went from [before] to [after] in [timeframe]. Here is what changed. | We went from 2 to 11 demo calls a week in a month. Here is what changed. |
| Mistake | I spent [time/money] on [thing] before I noticed one mistake. | I spent six months on cold email before I noticed one mistake. |
| Contrarian | Most advice about [topic] is wrong for [audience]. | Most advice about pricing is wrong for solo consultants. |
| Specific number | [Number] [things] I wish I knew before [milestone]: | 5 things I wish I knew before my first board meeting: |
| Question to the reader | How many of your [things] actually [outcome]? | How many of your meetings actually end with a decision? |
| Before / after | A year ago I [old behaviour]. Today I [new behaviour]. | A year ago I answered email all day. Today I check it twice. |
| Uncomfortable truth | Nobody likes to say this about [topic], so I will. | Nobody likes to say this about hybrid work, so I will. |
| Behind the scenes | Here is exactly how we [achieved result], step by step. | Here is exactly how we hired our first engineer, step by step. |
| Data point | We analysed [number] [things]. One pattern stood out. | We analysed 300 support tickets. One pattern stood out. |
| Lesson from a customer | A customer told me something last week that changed how we [do X]. | A customer told me something last week that changed how we write invoices. |
| Stop doing | Stop [common practice]. Do this instead. | Stop sending the deck before the call. Do this instead. |
| Small win | A small change to [process] saved our team [amount] a week. | A small change to stand-ups saved our team three hours a week. |
| Myth | “[Common belief].” I believed this for years. It is not true. | “You need a big audience to sell on LinkedIn.” I believed this for years. It is not true. |
| Hiring / team | The best hire we made this year had none of the usual credentials. | (Use as written, if it is true for you.) |
| Announcement with stakes | After [time] of work, we are finally ready to share [thing]. | After 18 months of work, we are finally ready to share our new app. |
| Checklist | Before you [action], check these [number] things: | Before you raise prices, check these 4 things: |
| Comparison | [Option A] vs [Option B]: which one we chose and why. | Notion vs Google Docs: which one we chose and why. |
| Prediction | In [timeframe], [prediction] will be normal in [industry]. | In five years, four-day weeks will be normal in agencies. |
To fill these with your own topic and audience, and see which fit before the mobile cut, use the free LinkedIn hook generator.
Choosing a formula
Pick the formula that matches what you actually have, not the one that sounds most dramatic:
- You have a result: Result + timeframe, Small win, Behind the scenes.
- You learned something the hard way: Mistake, Lesson from a customer, Before / after.
- You disagree with common advice: Contrarian, Myth, Stop doing, Uncomfortable truth.
- You have a list or process: Specific number, Checklist, Behind the scenes.
- You have data: Data point, Comparison.
- You want replies: Question to the reader, Prediction.
Common hook mistakes
- Starting with context. “As many of you know, I’ve been working in marketing for ten years…” uses the visible space on background the reader did not ask for.
- Greeting the reader. “Happy Monday, everyone!” tells people nothing about the post.
- A vague question. “Ever thought about productivity?” Most readers have, and keep scrolling.
- Too many line breaks. A one-word line, a blank line and another one-word line can hit the three-line cap before the hook has said anything.
- Over-promising. “This will change how you think about sales forever” sets up a post to disappoint.
- Bold everywhere. A fully bold first line is harder to read, counts double against the character budget and is skipped by screen readers. Bold one key phrase at most. See how to bold text on LinkedIn.
Testing hooks on your own posts
What works depends on your audience, so your own results are the best guide. Try two or three formulas over a few weeks and compare how those posts did.
If you use the Inkpost extension, its Insights page reads the stats on your own posts when you open your LinkedIn activity page and shows your best format, best length, best day and time, and your top five posts. That data stays in your browser. It will not tell you which hook formula is best on its own, but it does show which of your posts readers responded to, so you can look at how those posts opened.
A quick checklist
Before you post, read only your first line and ask:
- Would the person I am writing for know this post is for them?
- Is there a specific detail: a number, a name, a timeframe?
- Does it fit in about 140 characters, on one line?
- Is there a reason to click, and does the post deliver on it?
Check the result in the post preview to see exactly where the cut falls.