Skip to content

SEO

How to write SEO blog posts that get found and read

One question. Answered first. Linked to the page that sells.

To write SEO blog posts that work, pick one real question your buyers search, answer it plainly in the first two sentences, then use question headings, specific facts and links to the service the reader needs next. Google says it rewards content made for people, so the best SEO post is simply the most useful answer to that question.

Josef Winstone, Founder & Managing Director, Foundry Agency

By Josef WinstoneFounder & Managing Director · 7 min readUpdated

What makes a blog post good for SEO?

It answers one search better than anything else on page one. That's the whole test. Keywords, headings and links help Google understand the answer, but they can't make a thin answer rank.

Google's guidance on helpful content asks you to think about who wrote it, how it was made and why it exists. A post written by someone who does the work, with real detail, for a reader with a real question, passes all three.

How do you pick a topic that people search for?

Start from the questions your customers already ask you, then check how people phrase them in search. Your sales calls and inbox are a better source than any tool.

Then check the search itself. Type the question into Google and look at what ranks. If the results are product pages or a map, a blog post probably isn't what Google wants for that search. If they're guides and explainers, you're in the right place. Our keyword research guide covers this in detail.

How should an SEO blog post be structured?

A structure that works for readers, Google and AI assistants alike looks like this.

  • A title that says what the post answers, with the main search term near the start.
  • One H1, matching the title closely.
  • A two-sentence answer straight under the heading. Many readers stop here, and AI tools quote it.
  • A short summary list for people who skim.
  • H2s phrased as the follow-up questions people ask, each with a one or two sentence answer before the detail.
  • A numbered method where there's a process to follow.
  • FAQs at the end for the smaller questions, written as real answers, not teasers.

How do you write SEO blog posts step by step?

This is the order we write in. It keeps each post focused and quick to finish.

  1. Name the one question the post answers, and the reader who's asking it.
  2. Search it, and note what the top results cover and what they miss.
  3. Write the two-sentence answer first. If you can't, you don't know the answer well enough yet.
  4. List the follow-up questions and turn them into H2s.
  5. Write each section answer first, then the detail, in short sentences.
  6. Add something only you can: a figure from your work, a real example, a step you've learned the hard way.
  7. Link to your related posts and to the service page the reader needs next.
  8. Write the title tag and meta description, add Article and FAQ schema, and publish with a date.
  9. Check Search Console after a few weeks, and update the post when the facts change.

How long should an SEO blog post be?

As long as the answer needs, and no longer. Google doesn't reward word count, and padding makes the answer harder to find.

A simple definition might need a few hundred words. A full how-to with a method, examples and FAQs might need well over a thousand. Look at what ranks for the search, then aim to be more useful, not longer.

Can you use AI to write SEO blog posts?

Yes, with care. Google says using AI isn't against its guidelines, but publishing lots of pages mainly to rank is spam, however they're made. AI is useful for research, outlines and first drafts. A person who knows the subject should check every fact and add what only they know.

What mistakes stop blog posts ranking?

Five habits waste the most effort.

  • Writing about what you want to say, not what people search for.
  • Two or more posts chasing the same question, so they compete with each other.
  • Burying the answer under a long introduction.
  • No links from the post to your services, so it brings traffic but no enquiries.
  • Publishing and forgetting. Out-of-date posts slide down the results.

How does Foundry write SEO content?

We start with the questions your buyers ask, then plan posts that each answer one of them and link to the service that fits. Each post is written answer first, with question headings, FAQs and schema.

We use AI tools for research and first drafts, and a person checks every word and adds the detail only you and we know. For BidScript, search impressions rose 389% in 6 months. You get a report on the 1st of every month.

Our averages. Not our best days.

Our averages

  • 7days

    To a first PR feature

  • 20mins

    Average reply timethis service

SEO blog post FAQs

  • As often as you can publish genuinely useful posts. A few strong posts a month that each answer a real question beat daily posts that repeat each other.

  • One main search, plus the close variations and follow-up questions that naturally come with it. Trying to rank one post for several different questions usually fails at all of them.

  • Yes, when they answer questions buyers ask before they choose a supplier and link to the service that fits. Posts with no route to a service bring visitors but few enquiries.

  • Yes. Updating a post that already ranks, with current facts and a clearer answer, is often quicker than writing a new one. Merge posts that cover the same question.

  • Google says it judges the content, not how it was made. Posts made mainly to rank, at scale, break its spam policies whatever wrote them.

  • Not always. Strong service pages come first. A blog helps when it answers the questions that lead to those services.

Want posts that bring enquiries? Get moving.

Tell us what you need. We'll reply within the hour (working hours), and most websites go live about 5 days after kick-off.

We'll reply within the hour (working hours).

Or email hello@foundryagency.co.uk

Analytics cookies are off until you accept. We use them to see which pages help. Cookie notice