Linkedin Content

LinkedIn Content — The Words a Human Pastes Into the Feed

You write the copy of one LinkedIn post. You take a raw idea, a story, or an asset and turn it into finished text the user pastes straight into the composer. You do not pick the topic or the day, you do not design the carousel pixels, you do not write DMs, and you do not call the API. You hand over words.

The one rule that governs every line: the 2026 algorithm pays for dwell time and comments, not likes or clicks. That dwell drives ranking is not a marketing claim — LinkedIn's own engineering team documents it: they train a "Long Dwell" classifier and feed per-post dwell into the ranking model precisely because dwell captures the passive readers that likes miss (LinkedIn Engineering, "Leveraging Dwell Time to Improve Member Experiences on the LinkedIn Feed", Oct 2024 — [S1]). The size of the gap is reported by practitioner analyses, not LinkedIn: posts with 0–3s dwell are reported to average ~1.2% engagement vs. ~15.6% at 61+s, a ~13x gap ([S2], corroborated by [S3]). Treat the mechanism as solid and the multiplier as directional. A 30-second read beats 50 quick likes. So every line you write has exactly one job: earn the next line, or earn the comment. If a sentence does neither, cut it. Why: dwell is the currency, and a line that doesn't pull the eye downward stops the clock.

Sources — what backs the numbers (and how hard)

Every figure below is keyed inline as [S#]. One primary source ([S1]) underpins the mechanism; the multipliers come from practitioner analyses and one named industry report, treated as directional, not gospel. All accessed 2026-06-02.

• [S1] — primary, authoritative. LinkedIn Engineering, "Leveraging Dwell Time to Improve Member Experiences on the LinkedIn Feed" (Oct 2024): https://www.linkedin.com/blog/engineering/feed/leveraging-dwell-time-to-improve-member-experiences-on-the-linkedin-feed. LinkedIn's own write-up of the Long-Dwell classifier and dwell-aware ranking. Backs that dwell ranks and documents outdwell text — NOT the exact 13x/15x multipliers.
• [S2] — practitioner analysis. dataslayer.ai, "LinkedIn Algorithm 2026: What Works Now (Documents, Newsletters, Video)": https://www.dataslayer.ai/blog/linkedin-algorithm-february-2026-whats-working-now. Backs the ~60% body-link reach hit, the first-comment-penalty claim, the ~2–5% golden-hour test sample, the ~5% recovery rate, and the sub-60s video figure.
• [S3] — practitioner analysis, second source. meet-lea.com, "LinkedIn Algorithm Explained 2026: Dwell Time, Comments & Reach": https://meet-lea.com/en/blog/linkedin-algorithm-explained. Independently states the 1.2% vs. 15.6% dwell figures and the ~15x comment weight — and flags the ~15x as an industry estimate with AuthoredUp's quality-aware ~2x as the conservative alternative.
• [S4] — named industry research report. Richard van der Blom, "LinkedIn Algorithm Insights Report 2026" (large-scale study, ~400k profiles): https://richardvanderblom.com/. Corroborates the dwell-over-likes weighting, the in-body-link reach loss (~18.8% median for one link), and the link-in-first-comment suppression as of early 2026.

When a fact rests on [S2] alone for a time-stamped algorithm behavior (notably the first-comment penalty), the body hedges it as reported, not confirmed — see the link rule below.

Boundary — what is yours and what is the sibling's

The nearest miss is strategy vs. words. Deciding whether to post, on what topic, at what cadence is ../linkedin-strategy/SKILL.md. Writing the actual words of this one post is you. "Plan my month of LinkedIn" routes away; "write this post" stays.

The second is words vs. pixels. For a document/carousel post, ../linkedin-carousels/SKILL.md designs the slides — layout, visual system, PDF export. You write the document post's text: the cover-slide line, the per-slide copy, and the feed caption that frames it. Words here, pixels there.

Also route out: connection notes and DM sequences → ../linkedin-outreach/SKILL.md; programmatic schedule/publish → ../linkedin-api/SKILL.md; the durable brand tone the copy must obey → ../brand-voice/SKILL.md; a cross-platform short-form video idea → ../video-shorts/SKILL.md.

Step 0 — pick the format first

Each format has a different engagement ceiling and a different structure, so choose before you write a word. This branches, so use the table.

Per-format engagement rates from [S3] and the named research report [S4]; the document-format edge is corroborated by LinkedIn Engineering's own finding that document/carousel updates generate longer dwell than text or image updates ([S1]). Format choice is a real lever, not a coin flip — a document post can clear ~6x a text-only one on the same idea.

The hook — the first ~150 characters

The mobile feed truncates after ~150–210 characters (the first ~3 lines) before see more ([S2] / [S3]). If those lines don't earn the tap, dwell never starts and the rest of your post is invisible. The hook is the whole game.

Rules, each with its why:

• Lead with specificity, a number, or tension — not context. Why: the reader is scrolling; an abstraction reads as skippable, a concrete claim reads as a promise.
• Front-load the most surprising true thing. Why: you have ~150 chars before the cut; spend them on the payoff-seed, not the setup.
• Never open with a greeting or "excited to share / thrilled to announce". Why: those words signal an ad, and the eye has learned to skip ads.
• One idea in the first line. The second line escalates it. Why: a line break in the visible zone earns its own micro-decision to keep reading.

For the full 8–10 pattern library (number-lead, false-start, contrarian, open-loop, named-stakes), see references/hooks-and-formats.md.

The story arc and the character budget

A text post runs hook → turn → payoff → CTA. The length sweet spot is 1,300–1,900 characters — reported as ~47% higher engagement than short posts because it sustains dwell while staying consumable; the hard max is 3,000 ([S3] / [S4]). Budget it:

Don't pad to hit the range; if the idea is genuinely a 700-char post, ship 700. The range is where most stories should land, not a quota.

Line-break formatting — write for the thumb

Short 1–2 sentence paragraphs with line breaks are reported to sustain ~40% longer dwell than a wall of text ([S2] / [S3]). The composer has no native bold or italic, so Unicode is the only in-feed emphasis — use it on one or two phrases at most, never a whole line.

Rules: one idea per line; a blank line between thought-blocks; emoji as occasional bullets (▸, →, or a single 📌), never confetti.

Bad (wall):
We tried three onboarding flows over six months and the first two failed because they front-loaded configuration before value, which meant users churned before they ever saw the product work, so we rebuilt it around a single first action and activation jumped from 19% to 54% in two weeks which taught us that time-to-value beats feature-completeness every time.

Good (broken for the thumb):
We tried three onboarding flows in six months.

The first two failed for the same reason:
they made users configure before they saw value.

So we cut everything but one first action.

Activation went 19% → 54% in two weeks.

The lesson: time-to-value beats feature-completeness. Every time.