Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Start From the Search, Not the Sentence
An SEO-friendly blog post answers one query thoroughly, which means the work starts before the first sentence: pick one target query, read what currently ranks for it, and decide what your post adds that those pages lack. A post that is a rearrangement of the current top ten has no reason to outrank any of them.
The addition can take several forms. An angle the incumbents avoid, data you have and they do not, specificity where they stay generic, or plain honesty where they hedge. A plumber writing "what does a water heater replacement cost" with real local prices beats a national roundup of ranges, because the searcher wanted a number, not a disclaimer. If you read the top results and cannot name what your post will do better, you have the wrong query or the wrong post.
This pre-writing read takes twenty minutes and saves hours. Open the top five results for your query, note what every one of them covers, and note what none of them covers. The overlap is your table stakes; the gap is your reason to exist. Weak results in that top five, a Medium post or a forum thread ranking on domain strength alone, are the clearest signal a well-built post can take the spot.
Choosing that query is its own skill, and it does not require paid tools. The workflow in our keyword research guide for small businesses covers finding queries with real demand using autocomplete, Search Console, and competitor gaps. Do that step first; everything below assumes you arrive with one query and a reason to win it.
Structure: Headings That Match Questions, Answers That Come First
Use one H1, then H2s phrased the way people search the sub-questions of your topic, with a direct two-to-three sentence answer immediately under each heading before any background. Readers scan headings to find their question; a heading that matches their phrasing stops the scroll, and an answer that arrives instantly keeps them.
The same structure is exactly how AI systems lift citations. When Google's AI Overviews or a chat assistant quotes a page, it quotes a passage: a heading plus the sentences directly beneath it, pulled out of context. A self-contained section survives that extraction. A section that opens with two paragraphs of wind-up and buries the answer in paragraph four does not, because the liftable passage is the wind-up. Buried answers were always a reader problem; now they are a visibility problem too.
You are reading the pattern right now. Every section in this article opens with the direct answer inside a highlighted block, then earns the detail afterward. Steal the shape: question-shaped H2, answer first, evidence and nuance second, one idea per section.
The On-Page Elements That Still Move Rankings
| Element | What good looks like | Common mistake |
|---|---|---|
| Title tag | Under 60 characters, query near the front, a reason to click | Stuffing every keyword variant into one title |
| Meta description | Under 155 characters, states the value proposition | Duplicating the intro paragraph word for word |
| URL | Short and descriptive, like /blog/water-heater-cost | Dates and filler words baked in forever |
| Intro | The answer within the first 150 words | Throat-clearing before the point |
| Headings | Question-shaped, one idea each | Clever-but-vague labels nobody searches |
| Internal links | 3 to 6 contextual links with descriptive anchors | A "click here" dump at the bottom |
| Images | Descriptive alt text a screen reader could use | Keyword-stuffed alt text written for bots |
| Length | As long as the answer requires; commonly 1,000 to 2,000 words for substantive topics | Padding to hit an arbitrary word count |
None of these elements is exotic, which is the point: the posts losing to Medium articles and forum threads are usually losing on these basics, not on some advanced technique. Work down the middle column before publishing and you clear the bar most competitors miss.
Writing for the Second Reader: AI Extraction
AI models quote passages that stand alone: concrete nouns instead of pronouns, numbers with sources, lists and tables for anything enumerable, definitions stated plainly. Fluff is not just boring now, it is invisible, because extraction systems skip prose they cannot lift cleanly.
The practical test for any paragraph: could this be quoted on its own, out of context, and still make sense? "It depends on several factors" fails. "A title tag should stay under 60 characters with the query near the front" passes. Whenever content is enumerable, put it in a list or a table, because rows and items are the easiest units for a model to lift and attribute. Whenever you define a term, define it in one plain sentence before elaborating. And attach sources to numbers: a figure with a named origin is quotable, while an unsourced claim gives both readers a reason to doubt you.
The encouraging part is that this is not a second job. The structure that gets a section quoted by a model is the same structure that gets it read by a human in a hurry. For the Google-specific mechanics, see how to appear in Google AI Overviews; for chat assistants like ChatGPT and Perplexity, see how businesses get recommended by ChatGPT. Both channels reward the same page.
The Pre-Publish Checklist
Before any post goes live, run it against ten checks: one query, answer up front, extractable structure, tight metadata, and a reason the post deserves to exist. The list below is the compressed version of this entire guide, built to be copied into your workflow and reused every time.
- One target query confirmed, with a reason you can win it
- The answer appears within the first 150 words
- Every H2 is question-shaped with a direct answer immediately under it
- Title tag is under 60 characters
- Meta description is under 155 characters
- At least 3 internal links placed in context, not dumped
- One table or list wherever content is enumerable
- Alt text written for every image
- At least one fact or number a competitor page lacks
- A real next step for the reader at the end
Items one, two, and nine do the heavy lifting. A post can survive a slightly long title; it cannot survive answering no confirmed query or adding nothing the reader could not get one result up. Check those three first, and treat the rest as polish that compounds.
Keep It Alive After Publishing
Publishing is the midpoint, not the finish. Watch Search Console for the queries the post actually attracts, which are often not the one you targeted, retitle if impressions arrive without clicks, and refresh on a schedule before decay sets in.
Give a new post a few weeks to settle, then read its query report. A post written for one phrase frequently earns impressions for a neighboring one; a small retitle toward the query Google already associates with the page is the cheapest win in SEO. Impressions without clicks warrant a closer look at the title, snippet, position, and query mix. Use the title-tag and meta-description guide before changing the page’s promise. And every post decays eventually, so put refreshes on the calendar: the method in our guide to updating old blog posts recovers lost traffic for a fraction of the cost of a new post, and our publishing cadence guide covers how to balance new writing against maintenance.
Questions People Ask About SEO Blog Writing
- How long should an SEO blog post be?
As long as the answer requires and no longer. Substantive topics commonly land between 1,000 and 2,000 words, but length is not itself a ranking factor: a 700-word page that answers the query completely beats a 3,000-word page that circles it. Write until the question is answered, cut the padding, and stop.
- How many keywords should one blog post target?
One primary query plus its natural variants. A post about choosing accounting software will pick up dozens of related phrasings on its own because they share one intent. The rule that keeps a site clean is one page per intent: if two keywords mean different things to the searcher, they deserve two pages.
- Do blog posts still work for SEO in 2026?
Yes, and the ceiling is higher than it used to be, because a well-structured post now earns visits from two channels at once: classic rankings and citations in AI answers. What stopped working is undifferentiated posting. A post that answers a real query with something the current results lack still compounds for years.
- Should I use AI to write SEO blog posts?
For drafting, yes. For publishing unreviewed, no. Google evaluates quality and accountability, not authorship, and its spam policies target scaled content shipped primarily for rankings regardless of who or what wrote it. Keep a human review gate between the draft and the publish button, and AI becomes leverage instead of liability.
