Copy Coach.

Guide

LinkedIn post formatting: how to lay out a post people read

Formatting a LinkedIn post isn't decoration. It decides whether anyone taps "…see more". Here's how to lay out a post so the right lines land in the right places, from the fold to the final line.

1. Write for the fold

On mobile, LinkedIn shows about 140 characters or three lines, whichever comes first, then cuts to "…see more". Blank lines use up that budget, so a dramatic one-line opener followed by two empty lines can leave you with almost nothing visible.

Judge the visible part on its own. Does it stand alone? Does it contain something concrete: a number, a name, a moment? Would a stranger tap? The most common failure is chronological setup above the fold: "Three years ago, I started a new job at a mid-sized company…"

Read more on openings in how to write a hook, or test yours with the hook checker.

2. Rehook right after the fold

The first line after "…see more" is the second most important line in the post. It must pay off or sharpen the hook. If it starts a timeline ("Let me back up…"), the reader who just tapped feels the bait and leaves.

3. Break lines on beats, not on every sentence

Line breaks are pacing. A full stop and a fresh line can turn a statement into a pause before the payoff. Use them where the story turns, where something is revealed, and before the lesson. A break after every single sentence reads as a template, and readers have seen the template.

4. Keep one scene

LinkedIn stories drift into summary and lessons. Keep at least one real scene: a place or a time, an action, words someone actually said. One scene does more than three paragraphs of reflection.

5. Lists: only when the content is a list

A numbered list is the right format for steps, tools or mistakes, items the reader might screenshot. It's the wrong format for a story or an argument, where it chops the reasoning into slogans. If you use one, keep the items parallel and short, and still end on a line that isn't part of the list.

6. Length

For a story post, roughly 1,200 to 2,000 characters is plenty. Before posting, look for any paragraph that restates the lesson and cut it. The post is long enough when every paragraph moves the reader forward.

7. Endings without bait

"Agree?", "Thoughts? 👇" and "Comment YES" are engagement bait, and LinkedIn demotes them. Ending without a question is completely fine. If you do ask, make it a question only someone with experience of this exact situation could answer; those are the comments worth having.

8. Small things that matter

A formatting checklist

  1. Does the visible part, before "…see more", hold something concrete and make a stranger tap?
  2. Does the first line after the fold pay off or sharpen the hook?
  3. Are the line breaks on the turn, the reveal and the lesson, not after every sentence?
  4. Is there at least one real scene?
  5. Is there a paragraph that only restates the lesson? Cut it.
  6. Does it end without bait?

Styles that format well for LinkedIn: Justin Welsh (one line at a time, numbers up top) and Lara Acosta (a dated confession, then a rehook on line two).

See your post the way LinkedIn shows it

Copy Coach previews the fold as you write and checks every item on this list. $1 of free credit.

Rate my post free first

Questions

How many characters show before "see more" on LinkedIn?

On mobile, about 140 characters or three lines, whichever comes first. Blank lines count against that budget.

How long should a LinkedIn post be?

For a story, roughly 1,200 to 2,000 characters is plenty. Longer is fine only if every paragraph earns its place; cut any paragraph that restates the lesson.

Should I put a line break after every sentence?

No. Line breaks are pacing: use them for the turn, the reveal and the lesson. A break after every sentence reads like a template.

Do hashtags and engagement questions help?

Hashtags add nothing measurable, and engagement bait such as "Agree?" or "Comment below" is demoted by LinkedIn. End without a question, or ask one only someone with real experience could answer.