On this page11
- Why repurpose tweets instead of writing from scratch?
- The six-step archive-to-article pipeline
- What changes when a tweet becomes a blog post?
- How should you quote your own posts honestly?
- How do you turn a blog post into a LinkedIn article?
- When doesn't repurposing work?
- FAQ
- Can I embed tweets in a blog post instead of quoting them?
- Is it duplicate content if my blog post contains my own tweets?
- How many tweets should one blog post quote?
- Should I repurpose posts that did badly on X?
To repurpose tweets into blog posts, group your past posts by theme, pick a cluster that answers one question a reader would search for, and write a new article around that question, quoting your best posts word for word with their date and link. Then add what the posts couldn't hold: the reasoning, the steps, the trade-offs and the examples. A LinkedIn article comes after the blog post, shorter and with more context for a less crypto-native audience.
That's how a large part of this site was built. My X archive goes back to 2020, and the field notes here, like what posting on X did for my career and my piece on why journalists are not on your payroll, each started as a cluster of my own posts. Every one of them ends with a list of the posts it's built on.
Why repurpose tweets instead of writing from scratch?
Because your archive is a record of what you actually thought, at the time you thought it. That's worth more than a fresh draft written to fill a content calendar.
Posts on X are written quickly, in reaction to real events, client calls and conferences. They're honest in a way that planned content rarely is. They're also scattered. Nobody is going to scroll back three years to find your five posts on journalist relations and stitch them into an argument. You have to do that for them.
That's the whole case for repurposing. The thinking already exists. The value you add is the organising: picking the question, putting the posts in order, and filling the gaps between them.
There's a newer reason too. A lot of content now reads the same because it's generated rather than written. A post you wrote in 2022 about something that happened to you can't be faked, and readers can tell.
now brands need folks that could write old-school original content without using AI Shilika Jain on X, 19 Jun 2026
Quoting your own dated posts is one of the clearest ways to show a piece comes from real experience.
The six-step archive-to-article pipeline
This is the process I use, in order.
- Export your archive. X lets you request a download of your account data. You want every post with its date, text and ID, so you can link back to it.
- Strip the noise. Remove replies that make no sense out of context, giveaways, event check-ins and anything you no longer stand behind. What's left is usually a fraction of the total.
- Tag by theme. Give each remaining post one theme and a few topics. Mine fall into clusters like journalist relations, agency truths, personal brand on X and conference playbooks. Some posts won't fit anywhere, and that's fine.
- Pick a question per cluster. Look at a cluster and ask what single question a reader would search that these posts help answer. "Why won't journalists cover my launch" is a question. "Journalist relations" is a category.
- Write the article around the question. Lead with a direct answer, then use the posts as evidence inside sections. Quote three to five of the strongest, verbatim, and explain or extend each one.
- Adapt for LinkedIn. Cut, add context, and reframe for that audience, as covered below.
Step 4 is also where you find out which ideas actually landed. The posts that drew replies, saves and arguments are the ones readers already wanted more of, and they're the strongest seeds for an article.
creators building businesses must have a content product fit! Shilika Jain on X, 15 Oct 2023
Your archive is the cheapest content-product-fit test you'll ever run, because the results are already in. Steps 3 and 4 are where the real work is. A cluster of 20 posts on one theme might hold three or four separate articles, each answering a narrower question. This post is one of ten that grew out of a single theme.
What changes when a tweet becomes a blog post?
Almost everything except the original words. The post becomes evidence inside a larger argument, and the article supplies what X didn't have room for.
| Element | On X | In a blog post | In a LinkedIn article |
|---|---|---|---|
| Length | One line to a short thread | 1,500 words or more | A few hundred words to a short read |
| Job | React, provoke, share one idea | Answer a searchable question completely | Explain the idea to a wider professional audience |
| Context | Assumes the reader follows the space | Defines terms, adds examples and steps | Adds more context, less jargon |
| Your old posts | They're the content | Quoted as dated evidence | Paraphrased or quoted once or twice |
| Structure | None needed | Headings phrased as questions, a table, an FAQ | Short sections, clear subheads |
| Ending | Often a question to the reader | A next step that fits the reader | A light pointer to the full piece or your work |
The middle column is where most of the value gets added. A post that says "journalists are on the media's payroll, not yours" becomes a section explaining what that means for how you pitch, what founders get wrong, and what to do instead.
How should you quote your own posts honestly?
Treat your old posts the way a journalist treats a source. The rules I follow:
- Never change the words. Typos, slang and lowercase stay as they were. You can trim to a complete sentence or two, but you don't rewrite. If a post embarrasses you now, leave it out rather than tidying it up.
- Always date and link it. The date tells the reader what you thought and when. The link lets them check. Both build trust.
- Don't present an old view as current without saying so. If you've changed your mind since 2022, say that. It's more interesting than pretending you always held today's view.
- Quote only what fits the section. A post should sit next to the point it supports, not be dropped in as decoration.
- Credit others properly. If you quote someone else's post, name and link them, and think twice before quoting private individuals rather than public figures.
This is why every field note on this site ends with the list of posts it's built on. Anyone can follow the links and see the original context.
How do you turn a blog post into a LinkedIn article?
LinkedIn and X reward different things, and I noticed the difference early.
LinkedIn requires too much homework! Twitter is just shitposting! Shilika Jain on X, 1 Sep 2022
I was half joking, but the point holds. On X you can post a thought half-formed and let the replies finish it. On LinkedIn, readers expect the thinking done for them: setup, point, takeaway. The audience is also broader, with more people from outside crypto, so jargon that works on X needs explaining.
My conversion steps from blog post to LinkedIn article:
- Keep the strongest idea and cut the rest. A 2,000-word blog post often becomes a much shorter article built on its best section.
- Rewrite the opening as a personal moment, not a definition. LinkedIn readers respond to "here's what happened to me" more than to a search-style answer.
- Explain every crypto term once, briefly.
- Use one or two of your original posts, not five.
- End by pointing to the full blog post or to your work, lightly.
This piece belongs to a family like that: my original posts, a field note on this blog built from them, and a LinkedIn article on what posting on X did for my career. Each version reaches a different reader. If you want the bigger picture on how the two platforms divide the work, my piece on LinkedIn vs X for Web3 founders covers it.
When doesn't repurposing work?
When the archive is thin. If you've posted a few times a month for a year, there may not be enough material on any one theme to build an article honestly. In that case, keep posting and use a structured method to pull ideas out of your head instead, like my content extraction framework for founders.
It also doesn't work if the posts were mostly reactions to news that no longer matters. A take on a 2021 token price move rarely makes a useful article now, unless the lesson outlives the event.
And there's a cost: repurposing takes longer than people expect. Sorting, tagging and checking quotes against the original posts is slow, careful work. Rushing it is how misquotes and broken links end up in published pieces, and a misquote of yourself is still a misquote.
Founders who want this done for them, from archive to blog to LinkedIn, can see how I approach it through my content writing service and LinkedIn ghostwriting for founders. For deciding which ideas should be a thread first and which should go straight to an article, see threads vs single posts.
FAQ
Can I embed tweets in a blog post instead of quoting them?
You can, and embeds show the original formatting and engagement. The downside is that embeds depend on X staying available and can break if a post is deleted or the embed code changes. Quoting the text with a dated link is more durable and easier for search engines and AI assistants to read.
Is it duplicate content if my blog post contains my own tweets?
No. Short quotes inside a much longer original article aren't treated as duplicate content. The issue arises when you publish the same long article in several places without a canonical link, which is a separate question from quoting posts.
How many tweets should one blog post quote?
Enough to show the idea comes from real experience, without letting the quotes do the writing. I usually quote two to four per post. More than that and the article starts to read like a collection rather than an argument.
Should I repurpose posts that did badly on X?
Sometimes. A post can underperform on X because of timing or phrasing while the idea itself is strong. If it answers a question people search for, it may do far better as an article than it ever did as a post.
Sitting on years of posts and want them working as articles? Book a 30-min content teardown with me and bring your archive.


