SEO blog post: the workflow from query to published page, and the structure that earns the position

An SEO blog post is a post written to answer one specific thing people search for, better than anything currently answering it. The workflow is five steps and they go in this order: pick one query, confirm what the searcher actually wants by reading what ranks for it, build the outline from the sub questions they have, write the direct answer in the first paragraph, and publish with the internal links and the update date in place. Skip the second step and you write a good article for the wrong intent, which is the most common reason a well written post never ranks.

This page covers the workflow and the structure for one post. For the eleven on page techniques in detail and the order to apply them, see our guide to on page SEO techniques, and for the question list a whole programme is built from, see our content marketing strategy guide.

Step one: one query, one post

Choose a single primary query and write the post for that. Three rules make the choice a good one.

• Pick a question, not a topic. A topic produces a sprawling page nobody finishes. A question produces a page with an answer at the top.
• Check you do not already own it. Search your own site for the query first. A second post on a query you already rank for splits the signals and both pages suffer.
• Size it, then confirm it. Use a browser extension or a planning tool for a first read, and confirm against Search Console if you already have impressions for the term.

Step two: read the results page before you write

The ranking set is the clearest available statement of what the searcher wants. Fifteen minutes here saves a rewrite.

• What format ranks? If the first page is guides, a product page will not break in. If it is comparison lists, an essay will not either. Match the format.
• How long are the ranking pages? Not as a target, as a signal of the depth the question needs. Some questions are answered in 600 words and padding them out loses the reader.
• What do they all cover, and what does none of them cover? The first list is your required coverage. The second is why your page deserves the position.
• Read People Also Ask and the related searches. These are your H2s and your FAQs, in the reader's own words.
• Note who ranks. If the whole page is the three biggest sites in your category, pick a narrower version of the query and win that first.

Step three: build the outline from questions

Write the H2s before the prose. Each H2 is a question the reader has, in the order they have it, and the body under it answers that question and stops. An outline that reads as a sensible table of contents is a post that will read well, and the reverse is also true.

Primary query:    [one query]
Search intent:    [informational | commercial | transactional]
The one job:      [the single thing this page does for the reader]
Direct answer:    [two or three sentences, written first, used as paragraph one]

H2  [the main sub question]
H2  [the next sub question]
  H3  [a sub point only if the H2 genuinely splits]
H2  [the comparison or the method, with a table if one helps]
H2  [what this page covers, and where to go for the rest]
H2  Common questions
  H3  [question in the reader's words]
  H3  [question in the reader's words]
  H3  [question in the reader's words]
  H3  [question in the reader's words]

Internal links out:  [two or three, named]
Internal links in:   [the pages that will link to this one]
Primary metric:      [impressions and position for the query, at 90 days]

Step four: write the opening that gets quoted

The first paragraph answers the query directly, in plain words, with no preamble. No history of the industry, no in today's market, no restating of the question. Google's own guidance on creating helpful, reliable, people first content asks whether the content provides a substantial, complete or comprehensive description of the topic and whether it leaves a reader feeling they have had a satisfying experience, and the fastest way to fail that test is a page that takes four paragraphs to start. Published at developers.google.com and checked 9 October 2026.

A practical test for the opening: if somebody read only the first paragraph, would they have the answer? If yes, write the rest for the reader who wants the detail. If no, rewrite the paragraph.

Step five: the structure that holds a reader

• Short paragraphs, two to four sentences. A wall of text loses a reader on a phone, which is most of them.
• One table where a table genuinely helps. Comparisons, stages, formats and before and after. A table of prose is worse than prose.
• Lists for things that are genuinely lists, with a bolded lead in on each item so the list is scannable.
• Subheadings every three hundred words or so, written as questions or as statements with content in them. A subheading that says Conclusion is a wasted line.
• Four to six FAQs near the end, each a real question people ask, each answered in two or three sentences. These are the parts most often quoted elsewhere.
• Two or three internal links in the body, with descriptive link text, pointing to the pages a reader genuinely needs next.
• One image or diagram that adds information, with real alt text. A stock photograph of a handshake adds weight and nothing else.

The publish checklist

• Title tag containing the query, written to be clicked, within a length that displays in full.
• One H1 that agrees with the title.
• URL short, lowercase, containing the query, and set once. Changing it later costs a redirect.
• Meta description written for this page, specific enough that it could not sit on any other post.
• Alt text on every content image, and sane file sizes.
• Internal links out added, and at least two existing pages updated to link in. This step is skipped more than any other and it is the one that gets the post found.
• Published date and a last updated date shown, and honest.
• Submitted in Search Console, and the query added to whatever you track positions in.

The ninety day loop

A post is not finished at publication. Three checks turn a library of posts into compounding work.

• At thirty days, check Search Console for the queries the page is picking up. The ones you did not plan for are the most valuable information you will get, and they often deserve their own H2 in this post or a post of their own.
• At ninety days, compare impressions and average position against the query you targeted. A page with impressions and a weak position usually needs better coverage of the sub questions and more internal links in, in that order.
• Every six to twelve months, update the facts, the dates and the screenshots, and add the questions readers have asked since. Then change the last updated date because you changed the page, not to look fresh.

Where people get stuck on SEO blog post

How long should an SEO blog post be?

As long as the question needs and no longer. Read the ranking pages for your query to see the depth the question demands, then cover it completely. Length is an output of thorough coverage rather than a target to hit.

How many times should the keyword appear?

Write naturally and use the query where it belongs: the title, the H1, the first paragraph, one subheading and the URL. After that, use the words your readers use, including the variants, because that is how the page covers the subject properly.

How many blog posts should I publish?

Fewer, better, and linked together. One strong post a week that covers a question completely and is linked from your other pages beats five thin posts that compete with each other.

Should every post have FAQs?

Include them where real questions exist that the body does not answer directly. Four to six, in the reader's own words, and never as a way to repeat what the article already said.

Is AI written content a problem?

Google's guidance focuses on whether content is helpful, original and written for people. Use whatever drafting process you like, then make sure the page has original thinking, accurate facts, a named author who stands behind it and an answer at the top.

How long before a post ranks?

Check at thirty days for the queries it is picking up and at ninety days for position. Competitive queries take longer and the internal links pointing at the post are the fastest lever you control.

The second reader of the same post

The ninety day loop in this guide assumes one reader, the person who finds your post in search. A second reader now works through the same page first: an assistant that lifts a sentence, drops the rest, and hands a buyer a summary with your company in it or not.

Test that reader directly. Paste the question your post answers into ChatGPT, then Gemini, then Perplexity, and read what each one says before you open your own page. If your opening paragraph is the right answer, you will often see its wording come back. AI Knows Us keeps a record of those replies and the sources behind them, so a quarterly update can start from what the assistants actually said.