The first three sentences of a blog post decide whether the reader keeps reading. Most blog intros are bad in identical ways: throat-clearing, generic context-setting, a “did you know” question nobody asked. Readers bounce, and the rest of the post — however good — never gets read.
This is how to write intros that earn the rest of the post.
What weak intros do
The patterns that lose readers:
1. Generic scene-setting
“In today’s fast-paced digital world, having a strong online presence is more important than ever…”
The reader knows. They’re already here. They didn’t need the scene set.
2. The rhetorical question
“Have you ever wondered how some bloggers manage to grow their audience while others struggle?”
Hollow. The reader’s internal response is “no, I’m here for an answer, not a question.”
3. Long context before the actual topic
“Blogging has been around since the early 2000s, originally starting as personal online journals. Over time, it has evolved into…”
The reader bounces before the post arrives at its actual subject.
4. Promises with no specifics
“In this post, I’m going to share some tips that will completely transform your blogging journey…”
Generic claims read as marketing copy. The reader looks for specifics, sees none, leaves.
5. “Hi, welcome to my blog!”
Particularly on a single post, not the homepage. The reader didn’t come for a greeting. They came for the content.
What strong intros do
Three jobs, in this order:
1. Name the problem specifically (1 sentence)
Not generic. Specific to a real situation the reader recognizes.
Weak: “Many bloggers struggle with writing intros.”
Strong: “The first three sentences of a blog post decide whether the reader keeps reading.”
The specific version states a real claim that gets the reader nodding.
2. Agitate the problem slightly (1–2 sentences)
Acknowledge what makes the problem real. Why it matters. What’s at stake. Just enough to make the reader feel the problem.
Example: “Most blog intros are bad in identical ways: throat-clearing, generic context-setting, a rhetorical question nobody asked. Readers bounce, and the rest of the post — however good — never gets read.”
3. Promise a specific payoff (1 sentence)
Tell the reader what they’ll get from continuing. Specific. Concrete.
Weak: “In this post, I’ll show you some tips.”
Strong: “This is how to write intros that earn the rest of the post.”
The specific version sets a clear expectation. The reader continues because they know exactly what’s coming.
The pattern in practice
Total intro length: 60–120 words. Three short paragraphs. Sometimes one combined paragraph if you can do it concisely.
Read your existing intros against this. If they’re 200+ words before getting to the actual point, they’re too long.
What about the “hook” that grabs attention
Some writers add a one-sentence hook before the problem statement. Useful when:
- The hook is genuinely surprising or specific.
- It’s short. Under 15 words.
- It connects directly to the problem statement that follows.
Bad hooks slow the intro. Good hooks accelerate it. The test: would removing the hook make the intro weaker? If no, remove it.
The “show, don’t tell” version
For posts about a specific experience, the intro can drop the reader directly into a scene.
Example: “You open a theme marketplace, filter by ‘blog,’ and suddenly you’re staring at 847 options. They all look great in the demo. They all promise to be fast, beautiful, and easy to use.”
This works for posts that solve a problem the reader has actually lived through. The recognition does the agitation work without explaining.
Don’t force scene-openings into posts that don’t fit them. A how-to on backup strategy doesn’t need a dramatic opener.
The “summary box” alternative
Some bloggers (including this one) put a “Short answer” box at the top of long posts. This serves a different reader: the skimmer who wants the takeaway immediately.
The intro still does its job above the box. The box is a bonus for skimmers, not a replacement for the intro.
What to cut from existing intros
If you’re editing an old post:
- Cut “in today’s fast-paced world” and variants. Always.
- Cut “did you know that…” openings. Always.
- Cut the historical setup. Most posts don’t need it.
- Cut any sentence that doesn’t name the problem, agitate it, or promise the payoff.
- Cut “let’s dive in” and “without further ado.” Add nothing.
Often the strongest version of an existing intro is what remains after removing the first 80 words.
The “single line of context” exception
Some posts need one sentence of setup for the reader who landed cold. “WordPress is the open-source software that runs about 40% of websites.” Useful when the topic isn’t universally known.
One sentence. Not three paragraphs.
How to know if your intro works
Two tests:
1. The “would I read past this” test
Imagine landing on the post from search. Read just the intro. Do you want to continue?
If the intro promises the rest of the post will deliver, it works. If it doesn’t make the rest feel necessary, the intro is failing.
2. The bounce rate signal
If your post’s bounce rate is unusually high and the post itself is solid, the intro is the suspect. Strong posts with weak intros lose readers in the first 10 seconds. Rewriting the intro often fixes the bounce rate dramatically.
The honest summary
Strong intros name the problem in one specific sentence, agitate it briefly so the reader feels seen, and promise a specific payoff. Three short paragraphs, 60–120 words total. Cut throat-clearing. Cut generic scene-setting. Cut rhetorical questions. Get to the point in three sentences. The intro decides whether the rest of the post gets read — it’s worth more rewrite time than most bloggers give it.
