How to Write SEO-Friendly Blog Posts

"SEO-friendly writing" has an unfortunate reputation, and it earned it. A decade of keyword stuffing, 2,000-word padding, and paragraphs written for crawlers produced a lot of unreadable pages - and most of them no longer rank, because the thing that changed is that search got better at noticing.

What works now is close to what worked for readers all along, with a few deliberate structural choices layered on top. This is the process I follow: pick a query you can realistically win, answer the actual question, structure it so it can be scanned, and make it good enough that someone would link to it.

Before writing: choose the right question

The single biggest determinant of whether a post ranks is decided before the first sentence.

Pick a query you can actually win

New sites cannot compete for broad queries. "Flutter" is contested by Google's own documentation; you will not win it, and it is not even a useful query - someone typing it wants something, and you do not know what.

Specific queries are winnable and better qualified. "Flutter unbounded height error" has a clear intent, less competition, and a reader you can actually help.

The pattern holds generally: the narrower the query, the lower the competition and the higher the intent. Ten specific posts will beat one broad one, and each gives search a distinct thing to match.

Where to find them, in order of usefulness: Search Console for queries you already appear for on page two - the cheapest wins on the internet; autocomplete and People Also Ask for how people actually phrase things; and your own inbox - a question you have answered twice is a post.

Work out what the searcher actually wants

Intent is the difference between a post that ranks and one that is merely correct. Four rough shapes:

Informational - "what is technical seo". They want an explanation.
Navigational - "next.js docs". They want a specific place.
Commercial - "flutter vs react native". They want a comparison and a recommendation.
Transactional - "hire flutter developer". They want to act.

The reliable way to check is to search the query and look at what already ranks. If the first page is all comparison tables, that query wants a comparison, and a tutorial will not rank no matter how good it is. Search is telling you the format it expects.

Writing: structure carries as much weight as prose

With the question chosen, the structure does much of the work.

The title is the highest-leverage sentence

It is your strongest on-page signal and the headline in results. Three rules:

Front-load the topic. "How to Write SEO-Friendly Blog Posts" - not "Some Thoughts on Writing for Search".

Keep it near 60 characters, or search truncates it.

Make it a promise a person would click. Matching the query is necessary; being worth clicking is what actually earns traffic.

Answer early

Someone arriving from search has a question and limited patience. Give them the answer, or a clear statement of where it is, within the first two paragraphs.

This runs against the essay instinct of building to a conclusion. On a search result, that structure loses - the reader leaves before your point arrives, which search notices.

The introduction should establish: this page is about your query, here is the short answer, here is what follows.

Structure for scanning

Almost nobody reads a search result top to bottom. They scan for the part that matches their problem.

Headings that describe content, not clever ones. "Rendering: the JavaScript problem" beats "A Wrinkle in Time".
Short paragraphs. Two to four sentences. A wall of text gets skipped regardless of quality.
Lists and tables where the content really is a list or a comparison - they are the most scannable formats there are.
Code blocks for anything technical, so the answer is copyable.

Good heading structure also produces your table of contents, feeds jump-to links in results, and gives the page a shape a crawler can parse. It is one piece of work with four payoffs.

Use the words people search - naturally

Include your main query in the title, the first paragraph, and at least one heading, because those are the places a machine weights and a reader checks.

Then stop thinking about it. Modern search understands synonyms and related concepts; repeating an exact phrase adds nothing and reads badly. If you have written thoroughly about the topic, the vocabulary is already there.

Keyword density is not a thing. Nobody at Google has suggested it is a thing in fifteen years, and the tools reporting on it are selling a metric they invented.

Length follows the question

There is no magic word count. The right length is however long it takes to fully answer, and no longer.

Padding is now actively harmful: it delays the answer and makes readers leave. If a query can be answered in 800 words, answer it in 800 words. If it needs 3,000, the reader will happily read 3,000 - provided all of them are doing work.

A useful check: could you delete any section without the reader losing something? Then delete it.

After writing: the part most people skip

Publishing is not the last step.

Link it into your site immediately

A new post has nothing pointing at it. You are the only person who can fix that on day one.

Add two or three links from older, related posts, with descriptive anchor text - "how Google renders JavaScript" rather than "read more". This helps discovery, passes some authority, and tells search what the new page is about.

This takes five minutes and is the most reliably skipped step in blogging.

Get the metadata right

Unique <title> and description - the description is the ad copy under your link.
Self-referencing canonical.
Article structured data with author and date, so it can appear as an article rather than a generic page.
An Open Graph image, or every share of your post looks broken.

If your site is built properly, these are automatic. Verify anyway - metadata bugs are silent.

Update rather than republish

Search rewards pages that stay accurate. Updating a post that already ranks is almost always higher-return than writing a new one on the same topic - it keeps accumulated links and history rather than competing with itself.

Revisit anything with a version number or a "current best practice" claim annually.

Key takeaways

Choose the query before writing. Specific queries are winnable and better qualified than broad ones.
Check what already ranks - it tells you the format the query expects.
Front-load the topic in the title, keep it near 60 characters, make it worth clicking.
Answer in the first two paragraphs. Building to a conclusion loses search readers.
Structure for scanning: descriptive headings, short paragraphs, lists and tables where they fit.
Use the query naturally, then stop. Keyword density is not real.
Length follows the question. Padding delays the answer and costs you readers.
Link new posts from old ones immediately - the most-skipped five minutes in blogging.
Update what ranks rather than writing a competing post.

FAQ

How long should a blog post be?

As long as the question needs. Longer posts correlate with ranking because thorough answers tend to be longer - not because length itself is rewarded. Padding a short answer makes it worse.

How many keywords should one post target?

One primary query plus its natural variations. Two actually different topics means two posts, both of which will do better than one page covering both vaguely.

Should I use AI to write posts?

As a drafting and editing aid, yes. As the author, no - generic output ranks poorly because it says nothing new, and readers can tell. The value you have is specific experience, which is exactly what a model does not have.

Does publishing frequency matter?

Consistency matters more than volume. A thorough post monthly beats five thin ones weekly, both for readers and for how your site is assessed. Frequency without quality is how sites get buried.

Should I add a table of contents?

For anything over about 1,500 words, yes. It helps readers jump, and Google sometimes uses the structure for jump-to links in results.

How do I know if it worked?

Search Console, after a few weeks. Look at impressions before clicks - impressions rising means you are being considered for queries, which comes first. Position 11-20 with impressions is a page worth improving rather than replacing.

Conclusion

Writing for search and writing for people stopped being different jobs some time ago. The overlap is now almost total: answer a real question clearly, structure it so it can be navigated, and be accurate enough to be worth citing.

What remains actually SEO-specific is small and mostly mechanical - pick a winnable query, front-load the title, get the metadata right, link it from your existing work. Perhaps an hour per post, on top of the writing.

The writing is still the hard part. That is the right way round.

What Is SEO? for the fundamentals, On-Page SEO vs Off-Page SEO for where content sits among the other signals, and How Google Search Works for what happens to a post once you publish it.