How do I turn a sermon into a blog post?

Start with an accurate transcript of the sermon, then work in stages: find the one idea the message was really about, pick the two or three strongest supporting points, and rewrite them as written English at roughly 600 to 1,000 words. Cut the spoken scaffolding, like recaps, asides and announcements, and add the context a reader who wasn't in the room needs. Finish with a clear title, and have the pastor read it before it goes up.

Should I post the full sermon transcript or a rewritten article?

Ideally both, for different jobs. A full transcript is great for accessibility and for people who want the whole message. A rewritten article is what people actually read and share. Publishing the transcript on the sermon's page and the article on your blog gives you the strengths of each.

Can software write the blog post for me?

Some tools will draft one, but we'd be careful. Condensing a sermon is editing; inventing illustrations, applications or claims about Scripture the pastor never made is something else. SermonKeep doesn't write blog posts: it gives you the transcript, the Scripture the sermon used, a summary and the most quotable moments, and the writing stays with a person who can be traced back to the pulpit.

Does the pastor need to approve the blog post?

Yes, with a quick read before it's published. Because a post condenses and rearranges, it's easy to sharpen a point past what the pastor actually said. Five minutes of review protects the teaching and usually improves the post.

Guide

How to Turn a Sermon Into a Blog Post (Step by Step)

Q: How long should a sermon blog post be?

Around 600 to 1,000 words. A 40-minute sermon runs 5,000 to 6,000 spoken words, but a blog post isn't a shorter sermon; it's one idea from the sermon, developed for a reader. 800 words is a comfortable target: long enough to develop the point, short enough that people finish it.

By the SermonKeep team · October 9, 2026

Every week your pastor spends hours preparing a message, studying, praying, writing, and delivers it to whoever could be in the room that Sunday. By Tuesday, for everyone else, it may as well not have happened.

Turning that message into a blog post is one of the highest-value, least glamorous jobs in church communications. Done well, the sermon keeps teaching all week: the member who was out sick, the visitor who wants to know what your church believes, the neighbor who found you through Google. This guide walks through the process we’d hand a media volunteer, from recording to published article, entirely by hand. No writing degree required.

One framing note first: the whole process rests on the transcript. That’s your raw material, the pastor’s actual words in text. Get it right and everything after is editing, not authoring.

Step 1: Start from an accurate transcript

Don’t write the post from memory or from your own notes. You’ll paraphrase without noticing, and paraphrase drifts. Start from a transcript of what was actually preached.

You have three options: type it yourself (a 40-minute sermon takes most people three or four hours), pay a human transcription service, or use a sermon transcription service that turns the recording into text in minutes. Full disclosure: SermonKeep is ours. The steps below work however you get the text.

If your transcript keeps every “um” and false start, don’t clean it up yet. You’ll cut most of the text anyway, and you’ll fix the sentences you keep as you rewrite them.

And since transcript quality starts with audio quality, record close to the preacher, not from the back row. Our guide to recording sermons on an iPhone covers the basics.

Step 2: Find the through-line

Read the transcript once, start to finish, without editing anything. You’re looking for one thing: the single idea this sermon was about.

Every good sermon has one, even when it makes six points on the way. It’s usually visible in the introduction, restated near the end, and it’s the sentence the pastor would give you if you asked “what did you want people to walk away with?” Write that sentence at the top of a blank document. That’s your post.

This is the step people skip, and it’s why so many sermon blogs read like meeting minutes: a faithful list of everything said, and no reason to keep reading. A blog post isn’t a compressed sermon. It’s one idea from the sermon, developed for a reader.

As you read, mark three more things: the two or three strongest supporting points, the best single story or illustration, and one or two sentences where the preaching really landed. Everything you didn’t mark is material for another week, and one sermon usually holds several posts. Our guide to repurpose sermon content has more ways to use it.

If you use SermonKeep, two things speed this step up. The summary gives you the sermon’s main points and applications in order, which is most of the way to a through-line. And Clips & quotes lists the most quotable moments with their exact words, which is your shortlist for the line to set off in the post.

Step 3: From spoken words to written words

Here’s the math that makes this step feel drastic: a 40-minute sermon is roughly 5,000 to 6,000 words. A good blog post is 600 to 1,000. You’re keeping about one word in six, and that’s correct, not a compromise.

Spoken and written English are different. A congregation can’t scroll back, so preachers repeat, recap and signpost (“as I said earlier,” “turn with me to…”). Readers can scroll back, so on the page that scaffolding is dead weight. Cut, without guilt:

Announcements and housekeeping
Recaps of last week and previews of next week
Repetition that helped listeners follow live
Asides to the room (“I see some of you nodding”)
Long warm-ups: sermons often take five minutes to get going; posts get one paragraph

Then rebuild what’s left in a reader’s shape:

A hook: the story or tension the sermon opened with, in two or three sentences
The through-line, stated plainly
Two or three supporting points, each with its Scripture reference and a sentence or two of the pastor’s explanation
The best quote, word for word, set off so it’s easy to spot
The application: what the sermon asked people to do

Short paragraphs, subheadings, and Scripture references written out (John 15:5) so readers can look them up. SermonKeep lists every passage the sermon used, including the ones alluded to but never named, which makes this part quick.

Step 4: Edit for the reader who wasn’t there

Now read your draft as a stranger. The person who finds it on Google didn’t hear the service, doesn’t know who “Dave from the mission trip” is, and may not know your church at all. Fix everything that assumes they were in the room:

Add context. “As we saw in this series” becomes a one-line summary or a link to the previous post.
Introduce people. “Dave” becomes “a member of our team in Guatemala.”
Adjust the tone. Preaching rhetoric (“Are you hearing me, church?”) reads oddly in print. Keep the warmth; drop the call-and-response.
Keep the pastor’s voice. This matters more than polish. If your pastor says “walk with God” and your draft says “cultivate spiritual disciplines,” you’ve edited the person out of their own sermon. When in doubt, go back to the transcript and use the actual words.

A word about software, because this is where people ask. Some tools will happily draft the whole post for you. Tidying sentences and suggesting an order is one thing; adding an illustration, an application or a claim about the text that was never preached is another. The teaching in the post should be traceable, sentence by sentence, to the pulpit.

Then the non-negotiable: the pastor reads it before it’s published. Condensing can accidentally sharpen a point past what was said. Five minutes of review protects everyone.

Step 5: Publish, with the basics of search

You don’t need to become a search expert. You need five habits:

A title people actually search for. “What Does the Bible Say About Anxiety?” gets found; “Sunday Reflections, Week 34” doesn’t. Name the question the sermon answers.
A one-sentence description for the page, written for a person deciding whether to click.
Headings, like the ones in this post, so it’s easy to skim.
One image, your sermon graphic is fine, with alt text.
Links to the sermon recording, the series page and related posts, so a reader can go deeper.

Publish it on your church website, then let the post feed everything else: the newsletter gets the intro and a link, social media gets the quote, and small group leaders get the application.

The honest time budget

With a transcript in hand, a practiced volunteer can do steps 2 to 5 in 60 to 90 minutes. Without one, add three or four hours of typing, which is why most churches that start this habit by hand quietly stop by February. The transcript is the difference between a weekly rhythm and a good intention.

If that’s the missing piece for your church, our sermon transcription service does your first sermon free, up to an hour, no card required, with the summary, Scripture references and quotable moments included. Upload Sunday’s recording and try this process on a real message this week. The sermon already exists. It deserves more than one hearing.