How to Write a Blog Post That Can Actually Rank, Starting From the Search Results Page

Most advice on how to write content that ranks in search engines starts with the writing: keyword placement, word counts, headings. The better starting point is the search results page itself. The pages already ranking for your keyword show what searchers are being given, and what they still lack.

This article walks through one process you can repeat for every post. All you need is a web browser and a place to take notes, such as a plain text file or a spreadsheet. No paid tools are required.

Why most posts never rank: they answer a question nobody checked

A typical beginner post begins with a topic the writer finds interesting or a product they want to promote. The writer drafts it, adds the keyword a few times, publishes, and waits. The post then sits on page six of the results, or nowhere at all.

The usual cause is a mismatch. Someone searching “best way to start a blog” may want a step-by-step setup guide, while your post is a comparison of hosting companies. Both are good content, but only one answers that search. Search engines try to show the pages that satisfy the people typing the query, so a post that answers a different question loses to one that answers the right one.

A second cause is sameness. If your post says what the ten pages above it already say, in the same order and at the same depth, there is no reason to place it higher. A new site usually has less authority than the established pages, so it needs something those pages lack.

Both problems can be checked before you write, by looking at what is already ranking. Posts about the early missteps of a business model, like the ones covered in common mistakes new affiliate marketers make, have the same exposure: if the angle was never compared against what the first page offers, the post is a guess.

Read the first page of Google before you write a word

Pick one keyword and search for it. Use a private or incognito window so your own search history affects the results less. Results still vary by location, device and time, so treat what you see as a sample and not a fixed truth.

Then read the page like a researcher. Open a text file and record the following for each of the top eight to ten results:

  • The page type. Is it a how-to guide, a list, a product review, a category page, a forum thread, a video?
  • The title as shown in the results. Note any numbers, years, or promises in it.
  • The main headings. Scroll the page and write down the H2 headings, or the equivalent section titles.
  • The depth. Is it a quick answer or a long walkthrough? A rough sense is enough, you do not need exact word counts.
  • The date, if one is shown, and whether the advice looks current.

Do not skip the page types. If the first page is mostly product pages and you are writing a long educational article, that is useful to know. The reverse is also true: if every result is a detailed guide and you plan a 400-word summary, expect to lose.

Also look at the features around the results. The “People also ask” box lists related questions. The “Related searches” at the bottom of the page shows other phrasings. Typing your keyword slowly into the search bar shows autocomplete suggestions. Copy all of these into your notes. They are real wording from searchers, which makes them better raw material than guesses.

This takes time at first, but the notes are the groundwork for everything below. Twenty focused minutes on one results page often produces more usable direction than an hour of reading general SEO advice.

Match search intent: what the reader needs when they type your keyword

Search intent is the reason behind a query. Two people can type similar words and want different things, and the results page reflects whichever intent search engines have seen most often. You can read that intent directly from the page type column in your notes.

Intent usually falls into one of a few groups:

keywords. writing pad and pen.
  • Learning: the person wants an explanation or instructions. Results are guides, tutorials and explainers.
  • Comparing: the person is choosing between options. Results are reviews, “best of” lists and comparisons.
  • Buying: the person is ready to purchase. Results are product pages, pricing pages and sometimes reviews.
  • Finding a specific site or page: the person already knows where they want to go.

Look at your notes and ask what the majority of the first page is doing. If seven of ten results are step-by-step tutorials, the searcher wants to do something, and your post needs to be a tutorial. If most are comparisons, a single-product review will probably not fit, however well written.

Then describe the reader in one sentence. For example: “A person who has a site with no traffic and wants to know what to change in their next post.” If you cannot write that sentence, you do not yet know who the post is for, and the draft will drift.

For affiliate marketers this matters a lot. A post written for a buyer will not satisfy a beginner who is still learning the basics, and a post written for a learner will convert poorly if the searcher was ready to choose a product. Match the post to the intent first, and decide where a recommendation fits second.

Find the gap the top results leave open

Now compare the pages against each other. You are looking for what none of them does well. Go through your notes with these questions:

  • Do they all assume the reader already knows the basics, or do they all explain basics the reader may already have?
  • Is the advice outdated? Check dates and any references to tools or steps that have changed.
  • Do they give instructions without examples, or examples without instructions?
  • Do any of them name the downsides, costs, or the situations where the advice does not apply?
  • Is there a question from “People also ask” that none of the pages answers directly?
  • Are they written for a different audience than yours, such as experienced professionals while you write for beginners?

Mark every gap you find, then choose one or two that you can fill with real substance. A gap only counts if you can fill it. If the missing piece is an original data you do not have, or hands-on results you have not collected, leave it. Do not pretend to have them, because readers notice and the post gains nothing.

Good gaps for a small site tend to be practical: a clearer step order, a plainer explanation for newcomers, a worked example, a decision guide (“choose this if…, choose that if…”), or an honest limitations section. These are things you can produce by thinking carefully about the reader.

Write the gap as a single sentence at the top of your notes, for instance: “The top results explain what a meta description is but never show how to write one for a specific post.” That sentence now guides the whole article.

Build an outline from the questions searchers ask, not from a template

A generic template, such as intro, five tips, conclusion, produces generic posts. Your notes already contain a better source: the common headings across the top results, the “People also ask” questions, and the related searches.

Build the outline in three passes:

  1. List the questions. Put every relevant question from your notes in a list. Merge duplicates, and drop the ones that belong in a different post.
  2. Sort them into an order a reader would follow. Definitions and context first, then the process, then the details, then edge cases. A beginner should never need information from a later section to understand an earlier one.
  3. Add your gap. Make sure at least one section exists only because the top results left something out. Give it a heading that says so plainly.

Each heading should describe what the section answers. “How long should a meta description be?” tells a reader and a search engine what follows. “Final thoughts” tells them nothing.

Keep the scope in check. If your outline has fifteen major sections, the post is probably two posts. Splitting it gives you a second article to publish and lets each one stay focused on a single intent.

Write the opening, headings and body so both readers and search engines can follow them

With the outline set, drafting becomes assembly. A few habits help the post serve both readers and search engines.

Answer early. Within the first few sentences, state what the post covers and who it is for. Mention the target keyword or a close variant once in a natural sentence, as in “this post explains how to write content that ranks in search engines by starting with what already ranks.” Readers who arrive from a results page want confirmation they are in the right place, and the opening is where they decide.

Use headings as an index. Someone scanning the page should be able to read only the headings and understand the path. Use H2 headings for main sections and H3 headings sparingly for subpoints. Work the keyword or a variation into one or two headings only where it reads naturally.

Write short paragraphs. Two to four sentences each. Long blocks are harder to read on a phone, and many searchers are on one.

Define terms once, in plain words. If you use “search intent” or “meta description,” explain it the first time. Beginners should not have to open another tab to follow you.

Use lists where the content is a list. Steps, options and checklists work as bullets. Arguments and explanations work as paragraphs.

Show the example. For every principle, give one concrete case. A reader who sees a weak title next to a stronger one understands faster than one who reads a rule.

Avoid repeating the keyword to hit a target count. Search engines understand related wording, so varying it (“ranking content,” “writing for search,” “posts that rank”) reads better and loses nothing. When a sentence sounds strange because of the keyword, rewrite it.

Add titles, meta descriptions and internal links that earn clicks, including links to your earlier posts

Ranking is only half of search traffic. The other half is whether people click your result, and that depends on the title, the description, and the address shown beneath it.

The title. Put the main topic near the front and say what the reader gets. Compare your draft against the titles in your notes. If every result opens with “How to” and a number, you might match that pattern or deliberately differ by naming your audience or your angle. Keep it readable, since long titles may be cut off in the results.

The meta description. This is the short summary that can appear under the title. Search engines sometimes replace it with text from the page, so do not rely on it, but a clear one often helps. Write one or two sentences that state what the post covers and who it is for. Use plain words and leave out hype.

The URL. Use a short address that describes the topic, with hyphens between words and no extra clutter.

Internal links. Links between your own posts help readers find related content and help search engines discover and understand your pages. When you publish a new post, look through your earlier ones for places where a reader would reasonably want more. For example, a post on starting with affiliate marketing could point to your guide on how to choose an affiliate program, because the next question for that reader is which program to join.

Use anchor text that describes the destination. “Our guide to choosing an affiliate program” tells the reader what they will find, while “click here” does not. Then go back to your older posts and add links to the new one where it fits. Many beginners link only forward and leave the older posts disconnected.

Link only where it helps. A handful of relevant links beats a long list that sends readers away from what they came to read.

Check, publish and revisit: how to tell if a post is working

Before publishing, read the post once against your notes. Does it match the intent you identified? Does it fill the gap you wrote at the top? Does the title tell the truth about the content? Check spelling, broken links, and whether the post reads well on a phone screen.

After publishing, set up Google Search Console if you have not, since it is free. It shows which queries bring impressions and clicks to each page, and the average position your pages hold. Rankings take time to settle, so judging a post a few days after publishing tells you little. Check back after a few weeks and compare over time.

Read the numbers by pattern:

  • Few impressions: the page is not showing up for much. Review whether the keyword is too competitive for your site right now, and whether the content covers what the results page expects.
  • Impressions but few clicks: the page appears but people skip it. Rewrite the title and meta description first.
  • Clicks but short visits: people arrive and leave. Check whether the opening confirms what the title promised and whether the answer is easy to find.
  • Queries you did not plan for: these show what else the post answers. Add a section for the strongest ones, or write a separate post.

Updating a post is part of the process. When you revise it, rerun the first step: look at the first page again, since the results change. If new pages cover something yours lacks, add it. Update the date only when the changes are real.

The same loop applies to every post: read the results, work out the intent, find the gap, outline from questions, write plainly, publish, check, and revise. Each pass teaches you what your niche’s searchers want.

Pick one keyword you plan to write about next, open Google, and spend 20 minutes on the first page of results using the process above before you draft anything.

Leave a Comment