Guide · Content

How to Write a Blog Post That Ranks on Google

To write a blog post that ranks, pick one real search query, match its intent, and answer it in the first paragraph. Then cover the topic more completely than the pages already on page one. Use clear headings and place your keyword where it reads naturally. Rankings follow usefulness, not word count.

Aim for 1,500 to 2,500 words on informational posts. Use the free Word Counter to keep track while writing.

By Shreyas Bagal Published 23 June 2026 Updated 14 September 2026 Read ~13 min Topic Content · SEO

Most blog posts never rank because nobody checked what people actually search before writing a word. I write and edit content for clinics, shops and founders across Pune every week, and the posts that climb are never the longest or the most polished ones. They pick one real query, answer it fast, and go deeper than whatever's already on page one. I run the same nine-step process every time, in the same order, whether the post is about root canals or roofing, because skipping a step early is the single biggest reason a genuinely well-written post never ranks. None of it is clever. It's closer to a checklist than a writing trick, which is exactly why it's repeatable across a dental clinic, a real estate agent and a D2C brand without changing the underlying method.

The nine-step process for writing a blog post that ranks

Here's the sequence, in the order I actually run it. Each step earns its place because skipping it breaks something a later step depends on.

Step 1: Pick a query you can actually win

Research comes before writing, always. Pick one primary query you can realistically win this quarter, usually a specific long-tail or local phrase rather than a broad head term chasing national brands. "Root canal cost in Pune" is winnable. "Dental treatment" is a vague topic nobody searches and a battle you can't win yet. Find real queries for free through Google autocomplete, "People also ask" boxes, and your own Search Console data; my keyword research for beginners guide walks through prioritising them. Pin one keyword per post before writing a sentence. A post chasing five queries at once ranks for none of them.

Step 2: Match the intent before you draft anything

Every query has a goal behind it: to learn, to compare, or to buy. Search your keyword in an incognito tab and study what's already ranking. If page one is guides, write a guide. If it's service pages with a booking button, a blog post will never break in no matter how well it's written. This is where most DIY content quietly fails: a well-written 1,500 word article aimed at a commercial query Google wants answered with a service page, not an essay.

Step 3: Outline from what's already on page one

Open the top five ranking pages for your keyword and list every sub-question, angle and step they cover. Your outline is that list, plus whatever they're missing. Pull extra angles from "People also ask" and fold them in as their own headings. For an Indian audience, the gaps are usually local ones that national blogs skip entirely: real rupee figures, local landmarks, specific neighbourhoods. Outlining this way means you're never guessing what belongs on the page. You're building from what Google has already told you it wants to rank.

Step 4: Open with a direct answer, not a warm-up

Write the opening paragraph as a self-contained 40 to 70 word answer to the exact question in your title. Bottom line up front: no throat-clearing, no "in today's fast-paced world." This wins featured snippets, and it's increasingly what gets a post quoted inside an AI Overview or a ChatGPT answer, since both tools tend to lift the first clean, complete answer they find on the page. Write that opening as if a machine will copy and paste it as the entire answer, because it very well might.

Step 5: Build depth through sub-structure, not word count

Depth isn't a word count target, it's coverage. Break the topic into clear H2 sections, each owning one sub-question, with the first sentence under every H2 able to stand alone as an answer. A 1,200 word post with eight tightly focused sections that each fully answer their own question will out-rank a padded 2,500 word post wandering around the topic without ever quite landing anywhere. Structure is what lets Google, and a reader on a phone, find the exact section they need without reading the whole thing.

Step 6: Handle the on-page basics

Use your keyword in the title, H1, first paragraph, and at least one subheading, plus natural variations, without stuffing it in anywhere it doesn't belong. Keep the meta description under 160 characters and make it earn the click. My meta tags for SEO guide and free website SEO checker cover the rest of this list, titles, headings, alt text, in about five minutes per page. None of this ranks a post on its own, but skipping it caps a post that would otherwise have climbed.

Step 7: Link it into the rest of your site

Add three to five internal links to closely related pages, using descriptive anchor text instead of "click here", so readers go deeper and Google can see how the post fits into a wider topic. A post sitting in isolation, with nothing linking to or from it, works far harder to rank than one woven into a cluster of related pages. My internal linking strategy guide covers how to decide which pages deserve the most links pointing in.

Step 8: Add schema before you publish

Mark the post up with Article schema at minimum, and FAQPage schema if you've got a genuine FAQ section, so both traditional search and AI answer engines can read exactly what the page is, who wrote it, and when it was last updated. My schema markup guide covers each type in plain English, and it takes less time to add than most people expect once you've done it once.

Step 9: Publish, then request indexing

Publishing isn't the finish line, it's the point where Google needs to find the page before any of the previous eight steps can matter. Submit the URL through Search Console's URL Inspection tool and request indexing rather than waiting for a crawl to happen on its own. Then check back after a few days to confirm it says the URL is on Google rather than crawled but not indexed, which is common enough on new or low-authority sites that it's worth understanding on its own; my guide on what crawling in SEO actually means explains why that gap happens.

The 2026 realities: AI Overviews, first-hand experience and author signals

Search changed shape in 2026, and pretending otherwise wastes effort. AI Overviews now sit above the organic results on a large share of informational searches, generated by reading the top-ranking pages and summarising them with citations underneath. Getting cited there rewards the same fundamentals as ranking well organically, matching intent, answering directly, structuring cleanly, plus content that gives an AI system something concrete to lift: a specific number, a clear step, a real example, rather than a vague paragraph. My guide on how to appear in Google AI Overviews goes deeper if that's your main goal for a page.

First-hand experience matters more than it used to, and it's one of the few advantages a solo writer has over a large content operation. Google's own guidance is explicit about rewarding content that shows real, lived knowledge of a topic rather than a rewrite of what's already ranking. When I write about paid social, I can say plainly that a well-run Meta campaign lands leads around Rs 20 to 25 per lead in the right niche, a specific number a generic rewrite won't commit to. That kind of detail is what separates a page that reads as genuinely useful from one that reads as one more summary of other summaries.

Author signals round out the picture. A visible author with a real name, a photo, and credentials that are actually true, not invented, gives both readers and AI systems a reason to trust a page over an anonymous one. Every post on this site carries an author bio with verifiable credentials and results for exactly this reason. It's a small, one-time setup that quietly supports every single post published after it.

None of this means avoiding AI tools while writing. I use them constantly for outlining and first drafts. It means the finished post has to carry something an AI couldn't have written without you: a real number from a real campaign, a specific local detail, an opinion earned from doing the work. A post that reads as though nobody with actual experience touched it struggles to rank and struggles to get cited, regardless of which steps in the process got followed correctly.

A worked example: a Pune clinic targeting "root canal cost in Pune"

Here's the nine steps applied to one real scenario. Say a Pune dental clinic wants a blog post that brings in patients researching treatment costs before they call. Step one: "root canal cost in Pune" beats "root canal treatment" because it's specific, local, and has real buyer intent behind it, someone that close to a decision is close to booking. Step two: searching it in an incognito tab shows a mix of thin clinic blog posts and a couple of generic national articles, which means a genuinely useful, specific guide can compete within a few months, not years.

Steps three and four: the outline covers what the top five pages already answer, average cost range, what affects the price, insurance, plus what they miss: EMI or payment plan options, what a Pune-specific price range actually looks like compared to Mumbai or Bangalore, and what happens if the tooth needs a crown afterward. The opening paragraph states the average cost range in Pune in the first sentence, no backstory about tooth anatomy first. Steps five through seven: the post is broken into sections, each answering one sub-question directly, kept tight rather than padded, and linked internally to the clinic's appointment booking page and a related page on dental insurance.

Steps eight and nine: FAQPage schema mirrors the visible FAQ section word for word, and the page gets submitted for indexing the same day it's published rather than left to wait for a crawl. That's the whole process, the same nine steps I'd run for a roofing contractor or a real estate agent, just with different local specifics filling in each step. The framework doesn't change by industry. Only the research does.

How long it realistically takes to rank a new post

Set expectations before you publish or you'll quit right before the payoff arrives. On an established site, a low-competition, long-tail post can show up within a few weeks. On a new site, or for a competitive head term, three to six months is normal while Google crawls, indexes, and gradually extends trust to the domain. That's not a failure of the post, it's how long it takes for a new page to earn its place, even when every one of the nine steps above was done correctly.

I've watched this exact process take a Pune dental clinic's page from around position 59 to the top five in two months, but that was a winnable local term with thin competition, not a national keyword against established brands. Target long-tail, specific queries first to see movement sooner, bank that early proof, then reach for harder keywords once the domain has some track record behind it. Chasing the hardest keyword in your category first, before you've won anything smaller, is the single most common reason a new blog gives up too early.

Track progress in Search Console, not by refreshing an incognito search every day. Watch impressions and average position for your target query monthly. A keyword moving from position 34 to position 14 hasn't sent a single visitor yet, but it's the clearest sign the post is about to. Most of my biggest wins come from noticing a post stuck in positions 11 to 20 and giving it one more focused update, not from publishing something new every week.

Mistakes that keep a good post off page one

A few of these show up in almost every post I'm asked to fix after the fact.

  • Writing the topic you like instead of the query someone actually searches. "Content tips" is a vibe. "How to write a blog post that ranks" is a real, searched phrase.
  • Padding to hit a word count. Depth comes from sub-structure and completeness, not from restating the same point three different ways to look thorough.
  • Burying the answer under a long introduction. If the first paragraph doesn't answer the title's question, most readers, and most AI Overviews, never get to the part that does.
  • Skipping internal links. A post with zero links in or out sits isolated, and isolated pages take far longer to earn Google's trust.
  • Publishing and walking away. Most of the biggest wins come from updating a post already sitting on page two, not from writing something brand new every time.

None of these are difficult to fix once you see them written down. They're also exactly why a checklist mindset beats a talent mindset here. Ranking is a process you can follow, not a gift some writers have and others don't.

Frequently asked questions

How long should a blog post be to rank on Google?

Long enough to fully answer the query, and no longer. There's no magic word count, and Google rewards completeness over length. Some queries are fully settled in 600 words, competitive ones might need 1,500 or more to match what page one already covers. Open the keyword, read the top results, and match their depth rather than padding to hit a number. A tight, complete 900 word post beats a padded 2,000 word one almost every time.

What is the fastest way to pick a query I can actually win?

Search your candidate keyword in an incognito tab and look at who's already ranking. If it's dominated by national portals, directories and long-established brands, it's too competitive for now. If it's a mix of small, thin, outdated posts, it's winnable within a few months. This five-minute check, step one of the nine-step process above, saves weeks of writing for a keyword that was never realistically in reach.

Do I need backlinks to rank a new blog post?

Not always. For low-competition, long-tail and local queries, a genuinely better post that matches intent can rank on content and on-page signals alone, no outside links required. Backlinks become the deciding factor mainly for competitive head terms where several strong pages are already tied on everything else. Start by winning the winnable keywords with a well-structured post, then earn a few real links through backlink building for a small business to push into tougher territory later. Don't wait on links to publish.

How long does a new blog post actually take to rank?

On an established site, a low-competition post can rank within a few weeks. On a new site, or for competitive terms, three to six months is realistic while Google builds trust in the domain. I watched a Pune client's local listing climb from position 59 to the top five in two months, but that was a winnable local term, not a national keyword. Target long-tail, low-competition queries first to see movement sooner, then reach for harder keywords once you've banked a few wins.

Does AI Overviews change how I should write a blog post?

It changes what gets rewarded, not the underlying process. AI Overviews and tools like ChatGPT tend to lift the clearest, most complete, most specific answer they can find, which is exactly what steps four and five of the process above already produce, a direct opening answer and sub-structured depth. Add clean schema markup and a visible author with real credentials, and the same post built to rank organically is already built to get cited by AI systems too.

Your next step

Pick one winnable query using step one above, then run the finished draft through my free website SEO checker before you publish. If you'd rather I write or fix a post for you, get in touch and tell me the keyword you're trying to win.

Related guides

Follow Shreyas in Google

Get new guides in your Google Search & Discover feed.

Work with Shreyas → ← Back to blog