# how to write an introduction
Meta Description: Learn how to write an introduction that hooks readers in the first 40 words, answers their question immediately, and earns citations from AI Overviews.
The best introduction states your answer in the first 40–60 words, gives the reader one concrete reason to keep reading, and previews what they'll learn. It doesn't start with a question, a statistic, or a story about your journey. It starts with the payoff, the single most useful thing this article delivers, stated plainly, then expands outward.
Most writers treat the introduction as a warm-up lap. It's not. It's the only part of your article most people will read. The average reader spends under 15 seconds deciding whether to stay on a page, and that decision happens entirely in the first screen. If your introduction buries the answer, the reader leaves, and Google's passage-ranking systems notice the bounce.
The introduction has one job: resolve the reader's question fast enough that they trust you with the next 1,200 words. Here's the exact structure that does that.
A strong introduction answers the reader's question in the first 40–60 words, states one concrete claim they can verify, and tells them exactly what the article covers. It does not begin with "In today's fast-paced world" or a rhetorical question about the importance of writing.
The opening paragraph is the highest-leverage block on your page. AI Overviews lift cited passages almost always from the first paragraph under a heading, and the same logic applies to human readers: the first screen determines whether they scroll or leave. If the answer appears in paragraph nine, both the reader and the extraction model have already moved on.
The structure that works:
- **The payoff (40–60 words):** State the answer directly. No throat-clearing. - **The proof (2–3 sentences):** One checkable fact or mechanism that shows you've done this. - **The map (1–2 sentences):** Tell the reader what they'll learn and why it matters to them specifically.
A weak introduction says "this article will explore the importance of introductions." A strong one says "the introduction answers the query in the first 40 words, or the reader never reaches paragraph two." The difference is specificity, and specificity is what both readers and ranking systems reward.
The hook is not a question, a statistic, or a confession. It's a specific, concrete claim that creates a knowledge gap, something the reader didn't know they didn't know, stated in the first two sentences.
The "curiosity gap" mechanism is well-documented in content research. When a reader encounters a statement that contradicts their assumption, their brain releases dopamine and they keep reading to resolve the mismatch. A hook like "Your introduction is the reason your article doesn't rank" works because it's specific, slightly uncomfortable, and immediately actionable.
Here's what separates hooks that work from hooks that flop:
**Weak hook:** "Writing a good introduction is important for engaging your readers."
That's a restatement of the obvious. No reader learns anything, and no gap opens.
**Strong hook:** "The average reader spends under 15 seconds deciding whether to stay on your page, and the introduction is the only thing they see in that window."
This works because it names a specific number, makes a testable claim, and implies the reader is currently losing readers they don't know they're losing.
The hook should also set up the article's structure. If your article covers three mistakes, the hook should hint at the cost of those mistakes. If it covers a process, the hook should name the outcome the process delivers. The reader should be able to predict what comes next, and want it.
An introduction should be 100–200 words for a standard article, or roughly 5–10% of the total length. That's enough to state the answer, prove you know what you're talking about, and map the article, and short enough that the reader reaches the first heading inside 30 seconds.
The 5–10% rule is a ceiling, not a target. For a 1,200-word article, that's 60–120 words. For a 2,000-word guide, 100–200. Anything longer starts competing with the body, and the introduction's job is to get out of the way once it's done its job.
Three structural mistakes inflate introductions past their useful length:
1. **The throat-clearer:** "In today's digital landscape, content is more important than ever." That's 12 words that say nothing. Cut it. 2. **The thesis restatement:** Repeating the title in the first sentence. The title already told them the topic; the introduction has to tell them something new. 3. **The scope dump:** Listing everything the article covers in exhaustive detail. One sentence on the map is enough, "This covers the hook, the structure, and the three mistakes to avoid," not a paragraph.
The introduction ends when the reader knows the answer, trusts you to deliver it, and has a reason to keep reading. That's three to five sentences. If you're past 200 words, you're writing the body and calling it an introduction.
The first paragraph should include the answer, one concrete proof point, and the promise of what's next. That's it. No background, no definitions, no "this article will explore."
The answer comes first, always. If the query is "how to write an introduction," the first sentence states the method. If the query is "how much does X cost," the first sentence names the price range. The reader asked a question; the introduction answers it before they finish scrolling.
The proof point is where most writers stumble. You can't claim "this works" without evidence, but the evidence doesn't have to be a statistic. A mechanism works just as well: "The introduction answers the query in the first 40 words because that's the block AI Overviews lift for citation and the only block most readers see before deciding to leave." That's a causal claim the reader can verify by testing it, and it doesn't require inventing a study.
The promise closes the paragraph: "Here's the exact structure, the hook patterns that work, and the three mistakes that kill most introductions." The reader now knows what they're getting and can decide whether it's worth their time.
One thing the first paragraph should never include: a question. "Have you ever wondered how to write an introduction?" is the most common opener in weak content, and it fails because it assumes engagement instead of earning it. The reader is already there; they typed the query. Asking them to wonder about it is redundant.
The most common introduction mistake is starting with background instead of the answer. Writers feel obligated to set the scene, explain why the topic matters, define terms, establish context, before they deliver the payoff. That's backwards. The reader came for the answer; background they can get later, and only if they're still reading.
The second mistake is the fake statistic. "Studies show that 80% of readers decide whether to stay based on the introduction" — no, they don't, and no, a study didn't show that. Fabricated numbers are the fastest way to lose a reader who knows the topic, because one wrong detail discredits everything that follows. If you don't have a verifiable figure, use mechanism instead: "Readers decide in the first screen whether to stay, and the introduction is the only thing they see in that window."
The third mistake is the rhetorical question opener. "Have you ever struggled to write an introduction?" is a template tell; it appears on thousands of low-quality pages, and readers have learned to recognize it as a signal that the content will be generic. Opening with a question also wastes the highest-value real estate on the page: the first sentence.
The fourth mistake is the promise without a payoff. "In this article, we'll explore the key strategies for writing effective introductions" tells the reader nothing except that the author is about to write 1,500 words of theory. The introduction should deliver something usable in the first paragraph, a specific claim, a named mechanism, a checkable fact, not a preview of what might come later.
The fix for all four is the same: write the answer first, then the proof, then the map, and cut everything that doesn't serve one of those three jobs.
The core structure stays the same across formats, answer, proof, map, but the length and emphasis shift depending on what you're writing.
**Blog posts and articles (100–200 words):** The full structure applies. Answer first, prove it, map the article. This is the format where the curiosity gap matters most, because you're competing with a search results page that offers ten other options.
**Academic papers (150–300 words):** The answer becomes the thesis statement, the proof becomes the gap in existing research, and the map becomes the paper's structure. The hook is less about curiosity and more about establishing why the question matters, but the principle is identical: state the contribution before you describe the context.
**Emails and memos (30–60 words):** The introduction is the first sentence. State the purpose, state the ask, give the deadline. No hook, no map, no background. The reader is already committed; they just need the information.
**Product documentation (50–100 words):** The answer is the quick-start. State what the feature does, how long it takes to set up, and what the reader needs before they start. The map is a one-line list of the steps covered.
**Video scripts (15–30 seconds):** The introduction is the cold open. State the payoff immediately, "Here's how to fix your introduction in 40 words," then deliver. The viewer decides in the first five seconds whether to keep watching, which is even faster than the reader's 15-second window.
The format changes the length, not the principle. Every introduction answers the question first, proves it can be trusted, and tells the reader what comes next.
- The introduction answers the reader's question in the first 40–60 words, then proves it, then maps the article. - The hook is a specific claim that creates a knowledge gap, not a question, a statistic, or a confession. - An introduction runs 100–200 words for a standard article, or 5–10% of the total length. - The first paragraph contains the answer, one proof point, and the promise of what's next, nothing else. - The four common mistakes are background-first openings, fabricated statistics, rhetorical questions, and promises without payoff. - Different formats change the introduction's length, not its structure: answer, proof, map.
An introduction should be three to five sentences for a standard article. That's enough to state the answer, give one proof point, and map the article, and short enough that the reader reaches the first heading inside 30 seconds. If you're past 200 words, you're writing the body.
No. Opening with a question assumes engagement instead of earning it, and it's a template tell that readers recognize on low-quality pages. The reader already typed the query; they don't need to be asked whether they've wondered about it. Start with the answer instead.
The hook is the first one to two sentences; the introduction is the whole opening block. The hook creates the curiosity gap that pulls the reader in, and the introduction delivers the answer, proof, and map that keeps them reading. A hook without an introduction is clickbait; an introduction without a hook is a textbook.
A research paper introduction states the thesis, identifies the gap in existing research, and maps the paper's structure, in that order. The answer is your contribution, the proof is the gap you're filling, and the map is the section outline. It runs 150–300 words, longer than a blog post because the context matters more.
Most introductions lose readers because they put background before the answer. The reader came for the payoff, and if it's not in the first screen, they leave. Cut the throat-clearing, remove any fabricated statistics, and move the answer to the first sentence. The fix is the same for every format: answer, proof, map.
Open a blank document and write the answer to your reader's question in the first sentence, before you write anything else. If you can't state the answer in 40 words, you don't know it yet, and the introduction will fail no matter how strong the hook is. That's the test. Run it tonight on your current draft.