How to Write Blog Posts That Rank on Google

Blog posts that rank on Google tend to share one trait, and it is seldom how elegantly their owners write. Each answers one question more usefully than any other page in the results, and it is the question people actually ask rather than the one the business would like to talk about. A landscaping firm in Surrey found this out from two posts published a month apart. The first, celebrating ten years in business, drew warm comments from loyal clients and not one visit from a stranger. The second, a short piece on when to lay turf in autumn, kept bringing in homeowners planning their gardens long after it went up. Both were well written, but only one matched something people actually type into a search box. Build each post on what people search rather than what you want to announce, see it through to a revision months after it goes live, and every post becomes easier to get right than the last.

Ranking starts before you write a single sentence, with the choice of what to write about. Our guide on how to find keywords for your website explains where topic ideas come from, and once you hold a list of questions your customers ask, the task is to turn one of them into a post that can reach page one. The first filter is competition, because some questions are answered by national newspapers, government departments and huge retailers, and a small site will struggle to outrank them however good its post is. Before you commit to a topic, check keyword difficulty for free with our Keyword Difficulty Checker, which also tells you how many people search the phrase each month and which related searches sit around it. A lower difficulty with a steady, modest number of searches is a better target for a young site than a famous question with enormous demand. Once you have a question you can realistically win, the real work begins.

How to write blog posts that rank on Google: study page one first

Search for your chosen question on Google, in the country your customers live in, and read the top five results properly. You are looking for three things: what kind of page Google prefers for this search, what every good result covers, and what they all leave out. An electrician in Birmingham searching why a fuse box keeps tripping might find that the top results are all practical explainers rather than sales pages, which tells him a page selling his services would struggle there. He might notice that every result lists the usual causes, so his post must cover them too, simply to be in the conversation. And he might notice that none of them explains what an electrician actually checks on a visit, or what the repair usually involves. That gap is where his post can be better than anything already on page one.

What you have just studied is what search specialists call intent, meaning the job the searcher wants done. Someone typing the best time to visit Zanzibar wants a month-by-month answer about weather and crowds, not a history of the island, and someone searching wedding cake prices in Lagos wants figures, not a gallery. If the results are mostly maps of local businesses, the searcher wants to hire someone nearby, and a well-kept Google Business Profile may serve you better than any article. If the results are mostly videos, a written post will have a harder time than one with a short video of your own near the top. Google ranks pages that satisfy the searcher, and a brilliant answer to a different question does not count. Write the intent down in one line before you start, and check your finished draft against it.

Plan the post before you write it

A post that ranks usually reads as if it was planned around the reader's questions, because it was. Take the main question and list the smaller questions a person asking it would have next, using the related searches from the Keyword Difficulty Checker and the questions Google shows on the results page. A dog trainer in Cape Town writing about how to stop a puppy biting might end up with why puppies bite, at what age it tends to ease, what to do in the moment, what makes it worse and when to get professional help. Each of those becomes a subheading, in the order a worried owner would want them answered. The outline is also a test, because if you cannot fill a subheading with something useful from your own experience, it is better dropped than padded. Keep only the subheadings that earn their place, however few that leaves.

Before writing, note down what you can add that the existing results cannot, because this is what lifts a small business post above the generic ones. It might be your own photos of the job, prices from your actual quotes, a mistake you see customers make every month or a detail that only applies in your area. A roofer in Kisumu writing about gutter repairs can explain what the long rains do to cheap gutters in his town, which no national website will ever mention. Google's own guidance for site owners puts weight on first-hand experience and expertise, and details like these are exactly what that looks like on a page. They are also what makes a reader trust you enough to call. A post built from your own knowledge is harder to copy and more likely to be the one people remember.

Writing the post itself

Open with the answer. A reader arriving from Google wants to know within a few lines that they are in the right place, so the first paragraph should state the core answer in plain words and then say what the rest of the post adds. The dog trainer might begin by saying that puppies usually bite less once their adult teeth are through, and that how owners react in the meantime makes a big difference, then promise a routine for the weeks ahead. Put the main question's words into that opening naturally, since it helps both the reader and Google see what the post is about. Leave out long introductions about the history of your business or how common the problem is. Every sentence spent warming up is a sentence in which the reader might go back to the results.

Under each subheading, answer that one question fully before moving on. Use specific numbers from your own work where you can, such as how long a job takes, what it usually costs in your area or how often something needs doing, because vague answers lose to precise ones. Explain any trade term the first time you use it, since the people searching are rarely experts. Add your own photos where they help, and describe each one in its alt text so that Google and people using screen readers know what it shows. As for length, write as much as the question needs and no more, which might be six hundred words for a simple question and two thousand for a complex one. Padding a post to reach a word count makes it worse for the reader, and a long page that says little is not what Google is looking for.

You do not need to repeat the main search phrase over and over for Google to understand the post. Use it in the title, once near the start and in one subheading, and elsewhere write the way you would speak, with the natural variations people use. Placing keywords without overdoing it is a subject of its own, and our separate guide on using keywords without stuffing them covers it in detail. When the draft is finished, read it aloud from start to end. Anything that makes you stumble will make a reader stumble too, and anything you would not say to a customer across the counter should be rewritten. This single habit catches a surprising number of problems before anyone else sees them.

The finishing touches: title, description and links

The title is the first thing a searcher sees, so it has to match their question and promise a clear answer. Put the key words near the start and add what makes your post worth clicking, such as a local detail, the current year or a promise of steps, while keeping it short enough not to be cut off in the results. A travel agent in Mumbai might title a post about visa photo rules with the exact requirement and the words for Indian applicants, which tells the right searchers that this page is meant for them. Write a meta description of one or two sentences that sums up the answer and gives a reason to read on, since Google often shows it under the title. Keep the post's web address short and readable, built from the main words of the question rather than a string of numbers. None of this guarantees a ranking, but a weak title can waste a strong post.

Links inside your own website are the next finishing touch, and they matter for two reasons. They help Google discover the new post and understand how it relates to the rest of your site, and they move readers from reading to buying. From the post, link to the service page it naturally leads to, so the electrician's article about a tripping fuse box points to his page about electrical repairs in Birmingham. Then go back to two or three older posts or pages on related subjects and add a link to the new one, using words that describe it. End the post with a clear next step, whether that is booking a visit, requesting a quote or starting a chat. A post that ranks but leads nowhere brings visitors without bringing customers.

After you publish

Publishing is not the end of the process, because Google has to find the post before it can rank it. If your site is connected to Google Search Console, paste the new post's address into its inspection tool and ask Google to index it, which usually speeds up the first visit. Make sure the post appears in your sitemap and is linked from your blog's main page, so it does not sit on its own. Then give it time, since a new post on a young site can take weeks or months to settle into its position, and checking every day only creates worry. Mark a date two months ahead in your diary to look at it properly. Until then, move on to the next question on your list.

When that date comes, go to the Performance report in Search Console and filter it to the new post. It shows the searches the post has appeared for, how often it was shown and its average position, and it often reveals questions you did not plan for. If the post sits on the second page for a search that fits it, add a section that answers that search directly, or strengthen the part of the post that covers it. If it is shown often but rarely clicked, rewrite the title and meta description to make the promise clearer. A dog trainer who finds her puppy post appearing for searches about biting at night could add a short section on bedtime routines and watch how it responds. Small improvements like these are often worth more than writing a new post from scratch.

Finally, treat your best posts as living pages rather than finished ones. Prices change, rules change and your own experience grows, so revisit each post once a year and bring its facts and photos up to date. Only change the published date when you have made real changes, since readers notice when a new date sits on old content. If you find two of your posts answering nearly the same question, combine them into one stronger post and redirect the weaker address to it, so they stop competing with each other. Twenty strong, current posts will serve a small business better than a hundred thin ones. The care you put into keeping posts fresh keeps paying back long after the writing is done.

Writing a post that ranks comes down to a sequence you can repeat: choose a question you can win, study what page one already offers, plan around the reader's follow-up questions, answer quickly and specifically from your own experience, finish the title and links properly, then measure and improve. None of those steps needs a big budget, and every one of them gets faster with practice. Start with one question from your list this week and follow the process from beginning to end, however long it takes the first time. Before you publish, run the page through our AI SEO Tools to check its title, description and headings. Then note the date, move to the next question and come back to the first post when the data arrives. A year of posts written this way will do more for your business than any number written in a hurry.