Most blogs are sitting on a body of work that gets read once. A post goes live, enjoys a few days of attention, then settles into the archive where search engines occasionally find it and almost nobody else does. That is a waste of thinking. The ideas in those posts are still good; they are just wearing the wrong clothes.
Repurposing is not copying and pasting. It means taking something you have already worked out and rebuilding it for a format where people read, listen or skim differently. Done well, it reaches an audience that missed the original. Done badly, it produces thin, repetitive material that helps nobody. Here is how to stay on the right side of that line.
Find the material worth a second life
Before you open a new document, spend half an hour in your own archive. You are looking for posts with heat rather than the ones with the highest numbers.
- Posts people still mention. If a reader emails about it six months later, the idea has staying power.
- Answers to recurring questions. The thing you explain again and again in comments is a subject, not a one-off.
- Opinion rather than list. A post that argues a point gives you something to build on. A list of ten tips is harder to expand.
- Clusters. Three or four posts circling the same subject are the raw material for a guide.
- Good bones, dated examples. Update the screenshots and references, and the post is ready to travel.
Write the shortlist down, then decide the format from what the material actually suits.
Turning posts into a newsletter
A newsletter is not a notification that you have published something. Subscribers give you a small slice of attention and expect one clear idea in return.
Take a single post and use its argument as the spine, then write a fresh opening. Blog openings are usually written for a stranger who arrived from a search engine and needs context; your subscriber does not. Start with the story or the problem and make your point within two sentences.
What to add that the post did not have
- Something you have learnt since writing it, including where you were wrong.
- A reader's question and your answer to it.
- A shorter, plainer example for people who skim.
- One action they can take today, stated directly.
Keep a single-idea issue to roughly 400 to 700 words. If readers want the long version, point them to the original post rather than pasting it into the email. Many will have read it already, and repetition is the quickest way to lose people.
Building a podcast from written work
Reading a post aloud does not make an episode. Writing for the eye and writing for the ear are different jobs, even when the material is identical.
Strip out the subheadings but keep their function. Where a post says "Step two: gather your sources", the spoken version says "The second thing you need is your sources". Signposting matters more when there is no page to scan. Sentences should be shorter than you think, and each episode should carry one idea rather than four.
Record a rough version and listen back. The places where you stumble are usually the places the writing was too dense; rewrite those lines, not the whole script. If three related posts form a natural series, three short episodes make a more useful run than one long one.
One check before you record: your own posts are yours to reuse, but guest posts, co-written pieces and anything built on long quotations from other people are not. Ask first, or leave those alone.
Shaping old posts into an ebook
An ebook is where a cluster earns its keep. Choose a promise and a reader: what will someone be able to do by the final page? A short guide of a few thousand words is a perfectly good first ebook. It does not need to be a book-length manuscript, and padding it out will show.
The connective tissue
- An introduction that sets out the promise and who the guide is for.
- Transitions between chapters, so the reader is not dropped from one post into the next.
- A chapter that fills the gap readers always ask about and you have never written down.
- A checklist or summary at the end, so the guide is something to use rather than just read.
Cut anything that does not serve the promise, even a favourite post. Update names, figures, screenshots and references as you go. If you plan to sell the result, sort out the practical side — file format, delivery, refunds and how you record the income — and speak to an accountant if you are unsure.
Keep the original posts working
Repurposing should send people back to the source, not bury it. Update each original post with corrections and fresh examples, then connect related posts to each other so a reader arriving from search has somewhere to go next. If a guide has grown out of a series, say so in the posts themselves.
Avoid publishing the same text in two places word for word. An email, an episode or a chapter should be rewritten for its format, even when the argument is unchanged. The voice can stay the same; the shape should not.
A routine that keeps it going
Repurposing fails when it is treated as a big project. Make it small and repeatable.
- Once a month, open your archive and pick one theme rather than one post.
- Match the material to the format: a strong argument suits a newsletter, a story or conversation suits a podcast, a cluster suits an ebook.
- Block ninety minutes and write a new opening and a new ending. The middle can stay close to the original.
- Note the date on the original so you do not rework it twice by accident.
- Publish, then stop. One reworked piece a month beats a burst of enthusiasm followed by nothing.
Start with three posts this week
Open your archive and pick three posts that still feel true. Label each one: newsletter, podcast or ebook chapter. Write the first new opening now, while the idea is fresh, and set a date for publishing it. You did the hard thinking the first time round; this is mostly assembly, and it is much quicker than starting from an empty page.
Photo: Spudaitis / Pixabay
Related posts
More stories you’ll love reading