Turn a blog post into LinkedIn posts
Paste any public article link. This reads the page and writes three LinkedIn posts from what is actually on it, each taking a different angle. Free, no signup, and it will tell you when it cannot read something rather than inventing a post about it.
By Tayyab, Founder
No signup. Paste a public link and it reads the page, then writes from what is actually on it.
Why three posts and not one
One article almost always contains several posts. The argument, the counterintuitive detail, and the practical how-to are three different reads for three different people, and posting all three over a fortnight beats posting a summary once. Each draft here deliberately opens on a different angle so you can pick, or queue all three.
The tool reads the page before writing. That is the difference between a post that cites the specific thing you wrote and a post that could have been generated from the headline alone, which is what most "repurposing" output reads like.
Frequently asked questions
How do I turn a blog post into a LinkedIn post?
Paste the article URL. The tool fetches the page, pulls the title and body text, and writes three different LinkedIn posts from what is actually there: each with its own angle, a first line built to earn the "see more" click, and a closing question. Copy the one you like. No account needed.
Is the blog to LinkedIn converter free?
Yes, and there is no signup. This page runs a real language model on every request, unlike our other free tools which are pure browser code, so it is capped at a handful of runs per day per visitor. The workspace has a free forever plan with a much higher allowance.
Will it just summarise my article?
No. A summary is what most tools produce and it reads like one. Each post takes a different angle out of the source and is shaped for how LinkedIn actually gets read: short paragraphs, a concrete specific rather than a generality, and a question a person can answer in one line.
Does it invent statistics?
It is instructed not to, and it only ever sees the text on the page you gave it, which is why the tool reads the URL rather than working from the title alone. Check any number against your source before publishing, as you should with any generated draft.
What kinds of links work?
Public article and blog URLs. Pages behind a login or a hard paywall cannot be read, and a page with very little text is rejected rather than padded out into something invented. For videos, use the YouTube to social posts tool instead.
What this can actually read from a blog post
We fetch at most 5 MB of the page and read the first 5,000 characters of it. Those two numbers are the whole shape of the output: a long piece is repurposed from its opening rather than its full length, which is usually where the argument is anyway, and a very long one is not silently summarised from the middle.
What we read is whatever the page exposes to a plain fetch, in a fixed priority order: og:title before the title tag before the first heading, then the body from an article element before a main element before every paragraph on the page concatenated. Nothing runs the page's JavaScript, so a site that assembles its article in the browser hands us a title and very little else, and the tool works from that rather than writing around the gap.
Doing this for every post gets old
In the workspace the same engine runs on a schedule: it repurposes, writes in your brand voice, routes for approval, and publishes to every network. This page is one run of the first step.
Start freeFree forever plan, no credit card. Every network is included.
Prefer to see the whole loop first? How the repurpose engine works.