The first three sentences of a blog post decide whether the reader keeps reading past them. Most blog intros are bad in identical ways: throat-clearing, generic context-setting, a “did you know” question nobody actually asked. Readers bounce, and the rest of the post, however good it might be, never gets read at all. This is how to write intros that earn the rest of the post instead of losing the reader before it even starts.
What weak intros do
A handful of patterns reliably 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 already knows this. They’re already here, reading the post. They didn’t need the scene set for them.
2. The rhetorical question
“Have you ever wondered how some bloggers manage to grow their audience while others struggle?”
This tends to land hollow. The reader’s internal response is usually something like “no, I’m here for an answer, not another 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 even 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 like this read as marketing copy rather than genuine help. The reader looks for specifics, sees none, and leaves.
5. “Hi, welcome to my blog!”
This particularly hurts on a single post, as opposed to the homepage. The reader didn’t come for a greeting. They came for the content itself.
What strong intros do
Strong intros handle three jobs, in this order:
1. Name the problem specifically, in one sentence
The problem statement shouldn’t be generic. It should be specific to a real situation the reader recognizes immediately.
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 along right away.
2. Agitate the problem slightly, in one or two sentences
This means acknowledging what makes the problem real, why it matters, and what’s actually at stake. Just enough to make the reader feel the problem rather than merely acknowledge it.
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, in one sentence
Tell the reader exactly what they’ll get from continuing. This should be specific and concrete, never vague.
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 up front. The reader continues because they know exactly what’s coming next.
The pattern in practice
Total intro length should land around 60 to 120 words, spread across three short paragraphs, though sometimes one combined paragraph works if you can pull it off concisely.
Read your existing intros against this benchmark. If they run past 200 words before getting to the actual point, they’re too long and need trimming.
What about the “hook” that grabs attention
Some writers add a one-sentence hook before the problem statement. This is useful when a few conditions line up:
- The hook is genuinely surprising or specific, not generic.
- It stays short, under 15 words.
- It connects directly to the problem statement that follows it.
Bad hooks slow the intro down. Good hooks accelerate it instead. The useful test here: would removing the hook make the intro weaker? If the answer is 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 instead of stating the problem outright.
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 well for posts that solve a problem the reader has actually lived through. The recognition itself does the agitation work without needing to explain anything further.
Don’t force scene-openings into posts that don’t naturally fit them, though. A how-to on backup strategy doesn’t need a dramatic opener to work.
The summary box question
Some bloggers put a short “key takeaway” callout somewhere inside a long post to serve the skimmer who wants the answer immediately. Used well, that’s a genuinely useful pattern, distinct from a proper intro: it should hold one standalone, self-contained tip, not a compressed rehash of the post’s entire argument sitting at the very top. The intro still has to do its job regardless of whether a callout like that appears further down. It earns the read; the callout is a bonus for skimmers, never a replacement for it.
What to cut from existing intros
If you’re editing an old post, a few cuts nearly always help:
- Cut “in today’s fast-paced world” and every variant of it. Always.
- Cut “did you know that…” openings. Always.
- Cut the historical setup. Most posts genuinely 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.” They add nothing.
Often the strongest version of an existing intro is simply what remains after removing the first 80 words entirely.
The “single line of context” exception
Some posts need exactly one sentence of setup for the reader who landed cold with no prior context. “WordPress now powers roughly 43% of all websites” is useful context when the topic isn’t universally known, according to current W3Techs usage data. That’s one sentence, not three paragraphs of history.
How to know if your intro works
Two tests are worth running:
1. The “would I read past this” test
Imagine landing on the post from a search result cold. Read just the intro. Do you actually want to continue?
If the intro promises the rest of the post will deliver, it’s working. If it doesn’t make the rest feel necessary, the intro is failing at its one job.
2. The bounce rate signal
If a post’s bounce rate is unusually high and the post itself is genuinely solid, the intro is the likely suspect. This tracks with how people actually behave online: Nielsen Norman Group’s research on reading behavior found that the large majority of readers scan a new page rather than reading it word for word, deciding within seconds whether to keep going. Strong posts with weak intros lose readers in that first window of scanning. Rewriting just the intro often fixes the bounce rate dramatically without touching the body at all. If you want to dig deeper into what your numbers are actually telling you, bounce rate is more nuanced than most bloggers assume, and worth understanding before you chase it.
Earn the next sentence, then the one after that
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 to 120 words total, is usually enough. Cut the throat-clearing. Cut generic scene-setting. Cut the rhetorical question. Get to the point within three sentences, and the rest of the post has a real chance to be read the way it deserves. Aurora’s typography defaults are built to make that opening paragraph readable at a glance too, since a strong intro still needs decent contrast and spacing to actually get scanned. Once you’ve nailed the opening, the same discipline applies at the other end of the post: a strong conclusion is what makes the whole read feel worth it. The intro decides whether the rest of the post gets read at all. It’s worth more rewrite time than most bloggers ever give it.
