How to Write a Blog Post for SEO, AEO and GEO

Most blog posts that fail to gain any traffic aren't badly written, they're built on a decision nobody actually made: should this topic be an article at all. Before you draft a single sentence, work out whether the question in front of you deserves a blog post, whether it's better answered on a permanent page on your site, or whether it isn't worth writing about at all. Getting that call right saves more traffic than any amount of polishing afterwards.

Step one: decide if this is actually a blog post

A blog post is the right format when the topic is a question, a comparison, an explanation, or something time bound, like how much does X cost this year, or X versus Y for a small business. It's the wrong format when someone is trying to find you to buy something, book something, or find your location, opening hours, or service area. Those belong on a permanent service or location page, not a post that will scroll off your blog index in six months.

Ask yourself two questions before you commit to writing:

• Does a real, identifiable group of people search for this, and would they actually act on what they read: book, call, buy, decide.
• Can you say something here that a generic search result doesn't already say, based on what you actually know from doing this work.

If the honest answer to either is no, that's useful information. Not writing a weak post is a better outcome than publishing one, both for your own time and for what Google Search Central's guidance on creating helpful, reliable, people-first content actually asks: whether visitors leave feeling they've had a satisfying experience.

Step two: find the real question behind the query

Search intent is often narrower than the keyword makes it look. Someone searching how much does a boiler service cost might be trying to work out whether they need one this year, what happens if they skip it, or whether a quote they already have is fair. The keyword is the same, the underlying question isn't.

Before writing, look at what's already ranking and ask what job that content is doing for the reader: comparing options, explaining a process, reassuring someone before a purchase, or solving a problem step by step. Check whether the searches people actually use match what you assumed, using your own Search Console queries if you already have traffic, or by reading the related searches on the results page. Write to the question people are actually asking, not the one that's easiest to answer.

Answer the real question early, then earn it

Once you know the real question, answer it in the first few sentences, in plain language, before you explain your reasoning. This isn't just a courtesy to a reader in a hurry, it's also how both traditional search snippets and AI-generated answers tend to pull content: from clear, self-contained statements near the top of a page, not from paragraphs that build slowly toward a conclusion.

Weak opening:

When it comes to boiler servicing, there are a lot of factors to consider, and the answer isn't always straightforward. In this article we'll explore the various elements that go into it.

Stronger opening:

A standard boiler service typically costs between sixty and one hundred and twenty pounds, depending on your boiler type and location. Servicing under forty pounds usually means a stripped-down check, not a full service. Here's what should actually be included, and how to tell the difference.

The second version answers the question immediately, states a specific and checkable fact, and gives the reader a reason to keep reading anyway. That combination, a direct answer plus a genuine reason to stay, is what both a human skimmer and an AI system summarising the page are looking for.

Structure the page around the question, not around your outline habits

Use headings, h2 for main sections, h3 for sub-points within them, that describe the actual question each section answers, not vague labels. "What affects the price" is more useful, to readers and to machine parsing alike, than a heading like "Pricing Factors". A heading structure that mirrors real questions makes it easier for a reader to scan to the part they need, and easier for a search engine or an AI system to identify which section of your page answers which query.

Cover the supporting questions a reader would naturally have next, in the order they'd ask them, rather than listing every related keyword you can think of. If there's a genuinely common follow-up, what happens if you skip a service, how to tell if you're overpaying, give it its own section. If you're adding a section only because a keyword tool suggested it, that's a sign it's filler, not coverage.

First-hand experience is the hardest thing to fake, and the most valuable

Google's own guidance on people-first content puts specific weight on experience: has the person or business actually done the thing they're writing about. A generic explanation of how boiler servicing works is available from a hundred sources. What isn't available anywhere else is what you've actually seen: the specific fault you find most often on ten-year-old combi boilers in your area, the mistake most homeowners make before you arrive, the question customers ask that reveals what they're really worried about.

That's not a stylistic flourish, it's the hardest thing for a competitor or an AI-generated article to reproduce, because it isn't information, it's a track record. A real example, a real number from your own work, or a genuine before-and-after is worth more to both a reader and a ranking system than another paragraph of general explanation.

Back up claims with evidence, and link to it

Where you're stating a fact that isn't your own first-hand observation, cite something reputable: a manufacturer's guidance, a regulator, an industry body, official statistics. Link to it. This does two things: it lets a sceptical reader verify what you're saying without leaving the page unconvinced, and it signals to a search engine, and to an AI system building an answer, that your page is willing to be checked, not just asserted.

Don't link out to competitors' commercial pages, and don't link out reflexively to pad the page. Every external link should be there because it genuinely strengthens a specific claim. If you're building the habit of finding good sources to cite, and eventually earning links back the same way, this guide on finding quality backlink opportunities covers how that works from the other direction.

Link inward, deliberately

Once the post is answering its main question well, link it to other relevant pages on your own site: a service, a related post, a location page, wherever a reader genuinely benefits from going next. This isn't only about spreading authority between pages on your site, it's about keeping a reader who arrived through search moving deeper into your site instead of bouncing straight back to the results. Internal Linking for Small Businesses covers how to do this without turning a post into a wall of links.

Be explicit about what the article is actually about

Name the specific thing your article covers early and often, rather than relying on pronouns once you've mentioned it once. If the post is about combi boiler servicing in a specific town, say that, don't drift into "this kind of maintenance" for three paragraphs. This is sometimes called entity clarity: making sure a reader, a search engine, or an AI system parsing a chunk of your page in isolation can tell exactly what it's about without reading the whole page for context. Titles, headings, and the opening sentence of each section are where this matters most.

Say something that isn't already the top result

Before publishing, read your draft next to the page currently ranking first for your target question and ask honestly what your version adds. If the answer is better formatting or more words, that's not enough on its own. A genuinely original angle might be a real number from your own jobs, a mistake you see constantly that nobody else mentions, a straight opinion on which option is actually worth the money, or a process explained the way you'd explain it to a customer standing in front of you, not the way a textbook explains it.

Cut the filler, and don't stuff keywords

Every sentence should answer the question, support it with evidence, or help the reader decide what to do next. Sentences that only exist to hit a word count, or repeat a keyword phrase, don't help you, and Google has said plainly that content produced primarily to manipulate rankings rather than help people works against you. Say something once, clearly, and move on.

Use FAQs, tables and lists where they earn their place

A short FAQ section genuinely helps when it answers real follow-up questions you couldn't fit naturally into the main structure, the things a reader would type into Google next. It's padding when it's five questions that just restate the article in question-and-answer form to look thorough. Worth knowing: Google restricted FAQ rich results in search to a small set of authoritative government and health sites back in 2023, and has since removed them from general search results altogether, so an FAQ block is no longer likely to earn you the visual rich result it once did. It can still be genuinely useful to readers and to AI systems looking for a direct, self-contained answer, just don't add one purely for the schema markup.

Tables help when you're comparing options against consistent criteria: price ranges, features, timeframes. Lists help when steps genuinely happen in sequence or items are genuinely parallel. Both are wasted, and can look manipulative, when used to break up plain paragraph content that didn't need breaking up.

Show who wrote it, and why they're credible

A byline that names a real person or a real business, ideally with some indication of relevant background, is a small thing that does real work. It answers the "who" question Google's own guidance asks reviewers to consider: is it self-evident who's responsible for this content, and is there anywhere to find out more about them. You don't need invented credentials or a fabricated author bio, an honest line about who's writing and what they actually do is enough.

Keep it current, and say when you have

Prices, regulations and availability change. If a post covers something that can go stale, put genuine effort into reviewing and updating it periodically rather than leaving it to quietly become wrong, and update the visible date when you've made a real change, not as a cosmetic refresh with no actual edits underneath. A page that's honestly current is worth more than one that's freshly re-dated but unchanged.

SEO, AEO and GEO aren't three different jobs

SEO (search engine optimisation), AEO (answer engine optimisation: writing to be pulled into direct answers and featured snippets), and GEO (generative engine optimisation: writing to be cited by AI tools like ChatGPT or Google's AI Overviews) get talked about as if they need separate strategies. In practice they overlap almost completely. Google's own guide to optimising for its generative AI features is direct about this: the same fundamentals that earn a strong ranking, clear structure, genuine expertise, content built for people rather than algorithms, are what let AI systems find, trust and cite a page. It specifically warns against chasing AEO and GEO tricks instead of doing the underlying quality work.

What differs is emphasis, not method. Traditional search rewards a page that satisfies a searcher fully enough to convert. Answer and generative engines tend to favour content with clear, self-contained, checkable statements they can lift cleanly, which is exactly what a direct early answer, explicit naming of what the article is about, and cited evidence already give you. Do the fundamentals properly and you're largely covering all three at once.

What makes a piece worth citing

Both a human linking to your article and an AI system choosing to cite it are running the same calculation: does this page say something specific, checkable, and not available in identical form everywhere else. A specific number beats a vague range. A named source beats "studies show". A clearly stated opinion beats a fence-sat "it depends" with no follow-up. If you wouldn't feel comfortable being asked to back up a claim, don't publish it as fact.

Measuring whether it worked

Judge a post by what happens in Search Console's performance report over weeks, not days. Impressions, how often the page appeared in search results, tell you whether it's being found for the questions you intended. Clicks tell you whether the title and description are earning attention once found. A rising average position on your target queries over time tells you the page is being treated as a stronger answer. Don't judge a post by how it reads on publish day, or by traffic in the first forty eight hours, both are far too early to mean much.

A practical checklist before you publish

1. Confirmed this deserves a post rather than a permanent page, and that it wasn't better left unwritten
2. Identified the real question behind the search, not just the keyword
3. Answered that question directly in the opening, then supported it
4. Headings describe real sub-questions, not vague topic labels
5. Included at least one piece of genuine first-hand experience or evidence
6. Cited external sources for claims that aren't your own observation
7. Linked to genuinely relevant pages on your own site
8. Named what the article is about explicitly, more than once
9. Said something the top-ranking result doesn't already say
10. Removed sentences that exist only to pad length or repeat a phrase
11. Used FAQs, tables or lists only where they help comprehension
12. Attributed the post to a real, identifiable author or business
13. Set a reminder to review it when facts inside it might go stale

None of this is a formula that guarantees a result. Google is explicit that there's no fixed checklist that guarantees ranking well, only a body of work that consistently earns a reader's trust. Write the post because it genuinely helps someone make a decision, and treat the mechanics in this guide as the discipline that keeps you honest about whether it actually does.