LinkedIn Post Rules

LinkedIn only shows the first two or three lines before a "see more" cutoff — everything about a post's structure follows from that one constraint. A post that front-loads its point behind a generic opener never gets the click that would reveal it.

The hook

• Write the first line to work completely on its own, before the "see more" fold: a specific claim, a concrete result, a pointed question, or a sentence that creates a real information gap. Generic openers ("Excited to share...", "I've been thinking about...") waste the only guaranteed impression the post gets.
• Keep the hook to one short, punchy line — a single idea, not a compound sentence trying to set up the whole post. The second line can add a beat of context, but the first line alone should make someone want to expand the post.
• Avoid clickbait that the body doesn't pay off. A hook that overpromises relative to the content erodes trust fast in a professional feed, and readers notice the pattern quickly.

Length bands

• Short posts (under ~150 words) work for a single sharp observation, a quick win, or a quote-plus-reaction — anything that doesn't need supporting structure.
• Medium posts (roughly 150–400 words) are the default for most professional insight, a lesson learned, or a mini case study — long enough to make one point well, short enough to read in a scroll break.
• Long posts (400+ words) only earn their length with real structure (numbered steps, a clear before/after, a story with a payoff) — an unstructured long post reads as a wall of text and gets skipped regardless of how good the content is.

Formatting

• Use short paragraphs — one to three sentences — with a blank line between them. Dense paragraphs are the single biggest reason a post gets skipped on mobile, where LinkedIn is read.
• Use line breaks to create rhythm and let key sentences stand alone for emphasis, but don't overdo it to the point every sentence is its own line; that reads as an obvious engagement-bait pattern.
• Use at most 3 hashtags, placed at the end of the post, chosen for actual relevance to the topic — a wall of 10+ hashtags reads as spam and doesn't meaningfully improve reach on the platform as it works today.
• Avoid heavy emoji use as a substitute for actual formatting (e.g. an emoji as a bullet on every single line) — one or two used deliberately for emphasis read fine; a pattern of them reads as trying too hard.

Tone

• Write like a specific, real professional talking to peers, not like a corporate press release or a motivational poster. Concrete detail (a number, a specific mistake, a real timeline) reads as credible; vague inspiration ("Hard work pays off!") reads as filler.
• Avoid manufactured vulnerability or humble-bragging framed as a lesson ("I failed... and that's how I learned to 10x my revenue") — readers have seen the pattern enough times that it now undermines credibility rather than building it.
• State opinions plainly when you have one. Hedged, consensus-safe takes get scrolled past; a specific, defensible position is what actually starts a comment thread.

Call-to-action patterns

• End with a CTA that matches what you actually want: a genuine question invites comments; "I wrote more on this here: [link]" invites clicks; "Tag someone who needs this" invites shares — pick one, don't stack three different asks in the same closing line.
• Keep the CTA proportional to the post. A single sharp observation doesn't need a "What do you think? Drop a comment below! 👇" — let some posts just make their point and stop.

What to avoid

• Don't bury a link mid-post if reach matters — LinkedIn's feed algorithm has historically deprioritized posts with external links in the body; put a link in the first comment instead if that's a concern, and say so in the post ("link in comments").
• Don't post walls of unbroken text, don't stack more than 3 hashtags, and don't open with a generic announcement line the hook rules above already cover.

Repurposing long content into a post

• Extract the single most counterintuitive or specific claim from the long piece and lead with that as the hook — not the topic in general, and not the piece's own headline if it's generic.
• Compress the argument to its 3–5 core beats as short paragraphs or a numbered list, drop supporting detail and caveats that the long piece needed but a post doesn't, and close with a link to the full piece for readers who want the complete version.