A blog is written for people arriving one post at a time. A book is read by someone starting at page one with no context. That difference is why chronological collections fail: they repeat, they assume the reader was there last week, and they have no argument running through them. The fix is a thematic rebuild, and it means cutting most of the archive.
Turning a blog into a book
What has to change, post by post
Run three of your own posts against this. It is the quickest way to see how much rewriting a blog-to-book actually involves.
| In a blog post | In a book | Why |
|---|---|---|
| 'As I wrote last week…' | Cut, or absorb the point | The reader has no last week |
| Topical references and news pegs | Cut or reframe | They date the book immediately |
| Your framework, explained again | Explained once, early | You taught it forty times because readers kept arriving |
| Links doing the explaining | Written out, or cut | A printed page cannot be clicked |
| Comments and reader replies | Cut, or quoted deliberately with permission | Different medium, different rights |
| Post-by-post chronology | Thematic order | The archive order reflects your publishing schedule, nothing more |
| Standalone conclusions per post | One argument across chapters | This is the actual difference between the two forms |
A themes report on your archive
Send a batch of posts and we'll email back what the material is actually about — themes, best statements, and the repetition clusters. Free.
The repetition problem is bigger than you think
Across years of blogging you have explained your central ideas dozens of times, slightly differently each time.
That is correct blogging — new readers arrive constantly and repetition is how a blog teaches. In a book it is fatal: the reader gets your framework in chapter two and meets it again in five, nine and fourteen.
You cannot find these clusters by rereading, because you remember your ideas rather than their forty appearances. Seeing them laid out — this concept appears in these nineteen posts, here is the clearest version — is what makes the archive usable.
The ratio
Ten to twenty per cent of an archive, typically, plus 20–30% newly written connective material.
So a book from a blog is not a compilation. It is a new book that draws on an archive, and the sooner you accept that the faster it goes.
What survives: ideas, stories with a shape, the pieces you keep linking back to, anything that surprised your readers. What does not: topical posts, housekeeping, the ones that were good because of when they landed.
Rights, briefly
Check what you signed. If posts appeared on a publication's site rather than your own, the rights may not be entirely yours, and syndicated pieces sometimes carry exclusivity terms.
If you quote reader comments, ask. They are other people's words.
And if the blog stays online, decide whether that matters. For most books it does not — the book is a different product — but some publishers care, and it is worth knowing your position before a conversation rather than during one.
What Your Book Pro does here
Your Book Pro is a British book-writing platform. You bring a book — an idea, a folder of notes, half a draft, or a finished manuscript written somewhere else — and it gives you the editorial process a publisher would run: a plan, structured feedback, a simulated beta read, a line edit, a proofread, a cover, a blurb and a print-ready file. You can type it, upload it or speak it. The tools sit in one place and work on the same manuscript, so the feedback compounds instead of arriving as twelve disconnected opinions.
Plus lets you upload a manuscript you wrote anywhere, run whichever tool you actually need, and export it again. Word files, Google Docs, a Scrivener compile, eleven chapter documents, a decade of blog posts, forty voice memos. Nothing needs rewriting to be looked at, and a plain export of your own words is free forever. Export the archive, however messy, and upload it.
Themes from Bulk Audio reads across the whole thing and reports what the material is actually about — the recurring themes, where each is stated best, and the repetition clusters that make chronological collections unreadable. That is the step that turns an archive from a burden into a resource.
Plan Feedback tests the structure you build from those themes. Light Edit handles the rewriting pass. Detailed Editorial Feedback reviews the assembled draft.
What stays yours: deciding what the book argues. The archive shows you what you have written about; only you can say what the book is for.
Upload a manuscript written anywhere
Run a whole-book review
Email me the reportQuestions people ask
- How many blog posts make a book?
- Fifty good ones is plenty of raw material — you will use a fraction. More posts means better selection, not a longer book.
- Should I keep the blog up after publishing?
- Usually yes. It is a different product for a different reader, and it is the best marketing the book has.
- Do I need to rewrite every post?
- Most of them, substantially. Blog voice and book voice differ, and the connective material is entirely new.
- Will readers buy something they can read free?
- Regularly, if the book is genuinely a book — organised, argued, complete. They will not buy a printout of the archive, and rightly.