Most articles about using AI to repurpose blog posts into social media tell you the same thing: paste your blog into a tool, click a button, get five posts. The output reads like AI wrote it, because it did – and your audience can smell it from a feed away.
The actual skill isn’t picking a tool. It’s structuring the prompt so the AI extracts ideas the way a tired marketer would after their second coffee – pulling the one quotable line, the one stat that surprised them, the one contrarian take buried in paragraph nine. That’s the whole article.
Why one-shot prompts produce dead copy
“Turn this blog into a LinkedIn post” gives ChatGPT one job that’s actually three jobs at once: figure out what matters, decide on an angle, then format it. It collapses all three into a lossy summary. Intro, three bullet points, a question at the end. Safe output. Not the paragraph that would stop a scroll.
Split it into three passes instead. Extraction first: “what’s the most counterintuitive claim in this piece?” Then angle: “rewrite that claim as if you’re disagreeing with the conventional wisdom.” Then format: “compress to under 1,500 characters, hook in the first 210.” Each pass is shorter and more specific than “repurpose this,” so the model can actually think hard about one thing at a time.
The three-layer prompt that actually works
Here’s the structure. It works in ChatGPT, Claude, or any decent LLM. Run each layer as a separate message in the same conversation so the model keeps context.
LAYER 1 - EXTRACTION
Read the blog below. List:
- The 3 most counterintuitive claims (with the exact sentence)
- The 2 strongest data points (with numbers)
- 1 personal anecdote or specific example
- 1 line that could work as a standalone hook
[paste blog]
LAYER 2 - ANGLE (run after Layer 1 outputs)
Take claim #2 from your list. Write it as a LinkedIn post where:
- The first sentence (under 210 characters) states the claim
baldly, no setup
- Lines 2-6 explain why it's true with one specific example
- The last line is a question, not a CTA
- Total under 1,500 characters
- No emoji, no hashtag stack, no "thoughts?" ending
LAYER 3 - PLATFORM ADAPTATION
Now compress that same idea into:
- An X thread (5 posts max, 280 chars each)
- An Instagram carousel outline (6 slides, 1 idea per slide)
Keep the original claim intact. Don't soften it.
Layered prompts let the model think hard about extraction without simultaneously formatting – which is exactly when the generic-sounding stuff creeps in.
Platform limits – and the numbers that actually matter
Every tutorial mentions character limits. Few connect them to what the AI prompt should actually produce. Here’s what matters per platform, as of early 2026.
| Platform | Hard limit | The number that actually matters |
|---|---|---|
| LinkedIn post | 3,000 chars | ~210 chars before “see more” cutoff |
| LinkedIn Article | ~125,000 chars (~20,000 words) | Use only for full re-publish, not snippets |
| X (free) | 280 chars | URLs auto-shorten to 23 chars |
| X Premium | 25,000 chars | Mentions after char 280 don’t notify |
| Instagram caption | 2,200 chars | ~125 chars before truncation in feed |
That right-hand column is what your prompt needs to reference. X’s own help docs confirm the mention-notification quirk: if you mention an account in the first 280 characters they get notified, but mentions after character 280 currently don’t trigger a notification. Repurpose a blog into one long X post that tags the source author at the bottom and they’ll never know you posted it.
The LinkedIn 210-character fold is worth sitting with for a second. That’s roughly one medium sentence – and it’s the only thing most people read before deciding whether to tap “see more.” All the context, caveats, and setup that AI loves to front-load? Goes after the fold. Your actual point needs to be in sentence one, every time.
Brand memory: Projects vs. Custom GPTs
Every session, a one-shot prompt forgets your tone. The fix: a persistent workspace with your past posts, voice notes, and a few already-repurposed blogs that worked. Both major tools support this. They behave very differently.
Turns out Claude reads everything, every time. Claude Projects load your uploaded files into a 200,000-token context window – roughly 500 pages – so if your voice is defined by a quirky aside in blog post #7, Claude finds it. Custom GPTs work differently: up to 20 files (512 MB each) are stored, but ChatGPT runs a retrieval step at query time, pulling only the chunks it thinks are relevant. Cross-document reasoning is weaker by design.
For repurposing, that gap matters. “Write like my last 10 LinkedIn posts” – Claude reads all 10. A Custom GPT retrieves maybe two it considers semantically similar to the current blog, and misses the ones that actually define your cadence. Pricing is the same either way: both Claude Pro and ChatGPT Plus run $20/month at the entry tier (as of early 2026 – check current pricing before subscribing). The decision is about behavior, not cost.
One setup that kills most of the AI smell: Drop your last 5-10 best-performing social posts into a Project as “voice samples,” then add one instruction: “Match the rhythm and sentence length of these examples. Do not add emojis unless the examples use them.” That single line does more than any prompt template.
Three traps nobody warns you about
These are failure modes I’ve hit personally. No other tutorial I’ve found flags all three.
- Unicode bold silently doubles your character count. AI tools that “format” your LinkedIn post with bold text aren’t using real bold – LinkedIn doesn’t support it natively in posts. They substitute Unicode lookalike characters, and those use around double the character count of plain text. A 1,400-character post can silently breach 3,000 and get rejected without any error message that explains why.
- The hook gets buried in sentence two. AI loves opening with context (“In a recent blog post about…”). LinkedIn’s feed cuts after about 210 characters on desktop. The actual point lands behind “see more” and engagement collapses. Prompt explicitly for the hook in sentence one, no setup.
- Tagged sources on long X posts don’t get notified. See the table above – mentions after character 280 currently don’t trigger notifications. This one stings most when you’ve credited a source author at the end of a long Premium post. They never see it.
All-in-one repurposing tools
Planable, Typeface, Postiv. They work. They also produce output that looks like everyone else’s output, because similar prompt scaffolding runs under the hood across all of them. Volume-focused and on a deadline? Fine choice.
Goal is sounding like yourself at scale? The layered prompt plus Project approach wins. In my experience, it takes about 8 minutes per blog instead of 30 seconds – and the difference shows up in comments and saves, not in how fast you hit publish.
FAQ
Should I use Claude or ChatGPT for this?
Claude, for writing tasks. Projects handle long voice samples better than Custom GPT retrieval. ChatGPT wins if you need image generation in the same workflow.
How many social posts can I realistically get from one blog?
Five to seven across platforms is the honest range: one LinkedIn post, a 4-5 tweet thread, an Instagram carousel, maybe a quote graphic. Going higher means stretching the same idea past where it has anything new to say. A 1,500-word blog has maybe three repurposable claims. Squeeze out twelve posts and the AI starts inventing angles that aren’t in the source – that’s where hallucinated stats start showing up in your captions. I’ve seen it happen. It’s hard to catch before you publish.
Won’t Google penalize me for duplicate content?
No – but there’s a specific exception worth noting. Social posts adapted for tone, length, and platform aren’t duplicates in any meaningful sense, and most social platforms aren’t indexed the way blog content is. The one case to handle carefully: pasting blog paragraphs verbatim into a LinkedIn Article. That’s a direct republish. Rewrite it, or canonicalize back to the original.
Try it on one post this week
Pick your last published blog. Run the three-layer prompt on it. Compare the output against whatever your usual repurposing tool produces. If the layered version wins – and it usually does, even if the 8-minute time cost stings – build a Project around it. If it ties, you’ve at least saved yourself a subscription.