The LinkedIn Post Anatomy Framework

A Repeatable Structure, Not a Template to Copy Word-for-Word

Most LinkedIn advice tells you what to avoid. This lesson is a structural framework for what to actually build, a seven-part anatomy that separates posts people finish reading from posts people scroll past after the first line.

The structure works because each part does one specific job. Skip a part and the post usually still "reads fine," but it quietly underperforms, since each piece is solving a distinct problem in how a stranger decides whether to keep reading.

Quick Summary

• The hook must fit in roughly 140 characters and name a stake, not a topic, since the platform truncates there on mobile
• A re-hook line makes the hook's claim concrete by naming a specific, lived failure
• A credibility line names the actual tool or process used, before the framework starts
• Every framework post needs two devices: a physical analogy and a reframe (a better question than the one the reader thought they were asking)
• The closing question must pass the "stranger-usefulness test": would a competent stranger have a real, specific answer worth reading

Part 1: The Hook (Up to ~140 Characters)

The hook's only job is to earn the click that expands the post. It must state the actual stake, what the reader loses or gets wrong if they scroll past, and it must work standalone, since the feed now shows posts to people with no prior context on who wrote it.

Weak: "Here are 3 things I check in an SEO audit." This is a table of contents. It promises information but names no stake.

Strong: "The order you run an audit in determines whether you fix the real problem or just polish a symptom." This names a consequence (wasted effort on the wrong fix) without giving away the actual framework.

Part 2: The Re-Hook (Proof of Pain)

One short line that makes the hook's abstract claim concrete, usually by naming a specific failure the reader has likely lived through personally. This is where a reader decides the post was "written by someone who has actually been in the room," not a generic listicle.

Example: "I've seen teams spend hours optimizing titles and page speed for URLs Google was never even indexing." This doesn't add new information, it makes the stake from the hook feel real and specific.

Part 3: The Credibility Line

One line establishing how the author actually knows this, before the framework begins. Naming a real tool, a real process, or a real dataset here is what separates a practitioner post from a generic listicle, since anyone can write generic advice but naming the specific mechanism signals real, hands-on experience.

Example: "That's why I always follow the same sequence, backed by a live crawl and Search Console data, not assumptions." Naming the actual tools is the credibility, not a claim of expertise on its own.

Part 4: The Framework Body (3-4 Numbered Sections)

Each section should have a short bold header naming the step, a question framing what that step actually decides, and an answer that includes what happens if the reader gets it wrong. The question-per-step construction makes a post read as genuine reasoning rather than a recited list, since it shows the decision being made in real time rather than just stating a conclusion.

Keep one idea per block with a blank line between blocks. Dense paragraph walls are the fastest way to lose a reader mid-post, especially on mobile where line-wrapping makes long paragraphs look even denser than they are.

Part 5: The Analogy (Mandatory Device)

One concrete, physical metaphor that makes an abstract structure obvious and memorable. This is typically the single most "screenshot-able" block in a post, the part most likely to survive past the initial read because it compresses the whole framework into one memorable image.

Part 6: The Reframe (Mandatory Device)

Near the end, swap the question the reader thought they were asking for a better one. This is the insight peak, the line people quote and save, and it's what turns a post from information into a point of view.

Example: "When a page underperforms, I don't ask 'how do I optimize it?' I ask 'what's the first thing preventing it from succeeding?'" The reframe doesn't contradict the framework, it reveals the underlying principle the framework was actually built on.

Part 7: The Close (Call to Comment)

One specific, genuinely answerable question, never a generic "thoughts?" or "agree?". The test to apply: would a competent stranger have a real, specific answer, and would reading the range of answers actually be worth the time spent reading them?

A question like "what's the first thing you check when an important page starts losing traffic?" passes this test, since it invites a specific, comparable answer from anyone with relevant experience. A question like "do you agree?" fails it, since it invites no real information exchange.

The Four-Pillar Rotation, and Why Sameness Kills a Feed

Beyond any single post, a sustainable posting cadence needs variety across posts, not just within one. A useful model splits content into four rhetorical pillars:

1. Educational (the how): named problem, named framework, one concrete example, one takeaway.
2. Personal story (the who): a specific scene first, then the tension, then what changed, then the lesson stated last, never first.
3. Opinion (the stance): a contrarian claim stated plainly, then the strongest fair version of the opposing view, then the evidence, then what the author would do differently.
4. Engagement (the conversation): a short real situation, then one specific, genuinely answerable question, kept under roughly 100 words.

Fill-In Templates for All Four Pillars

Copy a block, replace the brackets, delete the labels. The Educational template below is the same seven-part anatomy from earlier in this lesson, just formatted as a fill-in scaffold; the other three pillars need their own distinct shapes since they carry a different job.

Pillar 1: Educational (usually a document carousel, target 1,500-1,900 characters)

[HOOK - max 140 chars. Name the stake: doing X wrong costs you Y.]
[RE-HOOK - the lived failure that makes the hook concrete.]
[METHOD LINE - name the actual tools and process. Never skip this.]

1. [Step name]
[A question that frames what this step decides.]
[The answer, plus the cost of getting it wrong.]

2. [Step name] ... 3. [Step name] ...

[PROOF - your differentiator. Land a real, specific result here,
 ideally inside the step it actually came from.]

[ANALOGY - mandatory. "Think of it like [physical thing]:
 [element] is the [part]." One-line consequence of skipping the first part.]

[REFRAME - mandatory. "I don't ask '[obvious question]', I ask
 '[better question]'."]

[CTC - one specific, answerable question.]

Pillar 2: Personal story (text-only or text plus one real artifact, scene first, lesson last)

[HOOK - a specific moment, or the uncomfortable fact the story is about.]
[THE SCENE - where, when, what you were doing. Concrete detail is the
 entire value. "A routine Tuesday check" beats "one day I was reviewing analytics."]
[THE TENSION - what went wrong, specific numbers or symptom.]
[THE INSTINCT YOU RESISTED - what you almost did, this is what makes
 it a story rather than a report.]
[WHAT YOU ACTUALLY DID - the process, named tools, real steps.]
[WHAT HAPPENED - the honest outcome, including the part that didn't work.]
[THE LESSON - one line, stated LAST. If this appears before the scene,
 it's an educational post in a costume.]
[CTC - a question inviting the reader's version of the same story.]

The test for this pillar: could anyone else have written this? If yes, it isn't a personal story, it's advice with "I" in front of it.

Pillar 3: Opinion (contrarian claim first, no hedging, steelman mandatory)

[HOOK - the contrarian claim, standalone and declarative. No "unpopular
 opinion:", no hedge.]
[RE-HOOK - sharpen the claim so it's precise, not merely provocative.]
[THE STEELMAN - the strongest fair version of the opposing view.
 Mandatory, and vary how you introduce it every time. A strawman here
 makes the whole post read as posturing.]
[BUT - where the opposing view actually breaks. Be specific.]
[YOUR EVIDENCE - a real number or a real thing you watched happen.]
[DEVICE - an analogy or sharp distinction making the claim concrete.]
[WHAT YOU WOULD DO DIFFERENTLY - the constructive turn. Criticism alone
 reads as a complaint, not an opinion.]
[CTC - a question inviting genuine disagreement, not agreement.]

Pillar 4: Engagement (short, target 400-700 characters, the worst-performing band on every dataset is under 400)

[HOOK - a real situation you're actually in right now.]
[THE SETUP - two or three lines maximum. Do NOT answer your own
 question and do NOT supply worked examples, that suppresses replies.]
[THE QUESTION - one specific, answerable question.]

The failure mode to avoid here: drifting into a mini-opinion post. If it has a framework, an analogy, or a reframe, it's not an engagement post anymore.

Watch for Repeated Tics

The failure mode of a structured framework is that it flattens into a detectable template if specific phrasings get reused too often. Common tics to actively rotate out: a repeated "X wearing Y" construction (like "a guess dressed as data"), a repeated steelman opener phrase, a repeated two-beat parallel closer, and recycled story arcs or closing questions across different posts. A quick check: read a week's posts back to back. If they feel like four variations of one post rather than four distinct posts, the structure has calcified into a template.

The One-Line Takeaway

Hook names the stake, re-hook makes it real, credibility line names the actual tool, framework answers a question per step, analogy makes it memorable, reframe delivers the insight, and the close asks something a stranger would genuinely want to answer, skip any one part and the post quietly underperforms even though it still "reads fine."

Related Concepts

• LinkedIn Algorithm & Content Strategy in 2026, pairs directly with this lesson, the algorithm lesson covers what gets distributed, this one covers what gets read once it is.
• Storytelling in Copy, the personal story pillar draws directly on narrative-structure principles covered there.
• AIDA, PAS, and the Core Frameworks, this anatomy is a platform-specific descendant of classic direct-response copy structures.