If you want to know how to write a good blog post for SEO, the useful answer is shorter than the industry makes it. Most of the work happens before the first sentence: deciding who the post is for, what they typed, and what they expect to find. The rest is clear writing with a few deliberate placements of the phrase you are targeting.
The framework below follows Yoast’s guide on how to write a blog post, written by Brendan Reid. It holds up because it treats search optimisation as the last layer on a well-made piece, not the first.
How to write a good blog post for SEO starts before you write
Yoast’s first instruction is to know your audience and the search intent behind the query. A post that answers the wrong question will not be rescued by anything that happens later in the process. If the results for your phrase are all step-by-step guides, an opinion essay is the wrong format, however well it is written. Our guide to search intent covers how to read a results page for this before you commit to an outline.
Then research. Read what already ranks, note what each result covers and what it skips, and gather your own material: data, screenshots, examples from work you have done. The gap between what ranks and what you can add is the reason the post should exist.
On keywords, Yoast’s advice is specific: “choose one main keyphrase and a few related ones.” One phrase gives the post a single job. The related terms describe the same topic from other angles and tend to appear naturally once you write about the subject properly. If two phrases need different pages to satisfy them, they belong in two posts, which is the question keyword clustering answers.
Structure the post with real headings
Every post needs an introduction, a body and a conclusion. That sounds like school advice, but a surprising number of blog posts open with three paragraphs of context and end mid-thought. The introduction should tell the reader what they will get; the conclusion should tell them what to do with it.
Yoast is firm that headings must be real heading blocks, H1, H2 and H3, not paragraphs set in a bigger font. A styled paragraph looks like a heading to a reader but carries no structure for search engines or screen readers. One H1 for the title, H2s for the main sections, H3s only where a section genuinely has parts.
A useful test: read only the headings, in order. If they summarise the argument, the structure works. If they read as a list of vague labels such as “Overview” and “More thoughts”, the post probably lacks a clear point.
Write short, plain sentences
Yoast’s style guidance comes down to two lines worth pinning above a desk: “keep your sentences short and direct” and “write as you would speak to a customer.” Long sentences are not wrong in themselves, but they make readers work harder, and on a phone screen a long sentence becomes a wall.
Keep paragraphs short, too, and vary sentence length so the text does not read like a metronome. Use transition words, such as “however”, “because” and “for example”, to show how one idea connects to the next. They are small, but they turn a list of statements into an argument.
A note on readability scores. Tools that grade sentence length and passive voice are writing aids, not ranking signals. They are useful for catching a paragraph that runs on, but chasing a green light can flatten good prose. If a long sentence is the clearest way to say something, keep it.
Where the keyphrase goes, and where it does not
Yoast’s optimisation checklist is short. Put the keyphrase in the title, in the first paragraph and in at least one subheading. Use related terms naturally through the text. Link to trusted sources. Show experience and expertise, the qualities Google groups under E-E-A-T, which our E-E-A-T examples post makes concrete.
| Stage | What Yoast recommends | Common mistake |
|---|---|---|
| Before writing | Know the audience and search intent; research; “choose one main keyphrase and a few related ones” | Targeting several unrelated phrases in one post |
| Structure | Introduction, body, conclusion; real H1/H2/H3 heading blocks | Bold or large text standing in for headings |
| Style | “Keep your sentences short and direct”; short paragraphs; varied length; transition words | Long paragraphs that become walls on mobile |
| Optimisation | Keyphrase in title, first paragraph and at least one subheading; related terms; links to trusted sources; E-E-A-T | Repeating the exact phrase until it reads oddly |
| Maintenance | “Review your posts at least once a year” | Publishing and never returning |
What the checklist does not say is “use the phrase as often as possible”. Three or four natural uses in a post of normal length is plenty. Beyond that the text starts to read as if it were written for a crawler, and readers notice before search engines do.
Links to trusted sources do two jobs. They let a reader check your claims, and they show you did the research rather than paraphrasing the first result. Link to the primary source where one exists: the documentation, the study, the original announcement.
The word-count myth, and the yearly review
The received wisdom is that a post must clear a set length to rank. Yoast’s guide sets no minimum word count, and that is the right call. Length should follow the question: a narrow query deserves a short, complete answer, while a broad topic needs room. Padding a post to hit a number adds reading time without adding value. Our post on blog post length and SEO covers why the correlations people quote do not prove what they claim.
The step most writers skip is the last one. Yoast’s instruction is to “review your posts at least once a year.” Facts date, screenshots go stale, better pages appear, and the intent behind a query can shift. A yearly pass to update, merge or remove keeps the archive honest.
Trimming is part of that review. Old posts tend to collect caveats and asides that made sense at the time. Cut sentences that no longer earn their place, check every link still resolves, and make sure the first paragraph still answers the query as it is searched today. Our content refresh guide covers how to choose which posts to revisit first.
Here is the limitation. These are editorial best practices from a plugin vendor, not measured ranking factors. Following every one of them will not make a post rank if it adds nothing that the existing results lack, and plenty of posts rank while ignoring half the list. Treat the checklist as a floor for quality, not a formula for position.
The practical order of work is simple. Settle intent and the keyphrase first. Outline with headings that state the argument. Draft plainly, as if explaining to a customer. Place the keyphrase where it belongs, link your sources, then put a review date in the calendar. Most posts that fail do so at the first step, so give that step most of your time. More planning guides sit in our strategy archive.
Frequently asked questions
How do you write a good blog post for SEO?
Match the search intent, choose one main keyphrase and a few related ones, use real headings, write short, direct sentences, link to trusted sources and review the post at least once a year.
Where should the focus keyphrase appear?
In the title, the first paragraph and at least one subheading, with related terms used naturally through the text.
Is there a minimum word count for SEO?
No. Yoast’s guide sets none. Length should follow what the query needs, not a target number.
How often should I update blog posts?
Yoast recommends reviewing posts at least once a year, sooner for topics where facts change quickly.
The takeaway Good SEO writing is good writing with intent settled first. One keyphrase, real headings, plain sentences, cited sources and a yearly review do more than any word count.
