How to rank a blog post
A blog post ranks when it is the most useful result for one specific query and the rest of the blog points to it. Publishing a good post and waiting is often not enough, because a new post starts with no internal links and no history, and Google has to decide it is better than pages that have ranked for years.
Most of the outcome is decided before you write: whether the query is one this post can own, whether your blog has covered the topic before, and whether the format matches what already ranks. After publishing, the job is connecting the post to the blog and giving it time.
Choose a query the post can own
Before drafting, search the query you have in mind and look at the first page.
- Is it one question or several? If the results mix definitions, product pages and tutorials, the query is ambiguous. Pick a narrower phrasing.
- What format wins? Step-by-step guides, lists, comparisons or short answers. RankWave AI's anatomy of a how-to guide is a useful model when the results are tutorials.
- Do you already have a post on it? If yes, improve that one instead. Two posts on one query compete; see fixing cannibalization.
- Can you add something the top results lack? Your own test, photos, numbers, mistakes you made. If not, pick a different query.
Posts that fit the blog's main subject rank more easily than one-off posts on unrelated topics, because the rest of the blog supports them. The SEO for bloggers page covers building that focus.
Write, publish and connect the post
- Outline from the searcher's sub-questions. List what someone would ask next after the main question, and make those your subheadings.
- Answer the main question early. A direct answer in the first paragraph serves readers and is the text most likely to be used in a snippet.
- Put in the first-hand material. Screenshots of your own setup, results you measured, what went wrong. Google's helpful content guidance asks whether content shows first-hand expertise and experience.
- Write a title that states the benefit plainly. Keep the main query near the start and check it fits without truncation.
- Describe images with alt text and compress them; slow, oversized images are common on blogs.
- Show the author and date. A byline linked to an author page answers the "who" in Google's who, how and why questions.
- Link to the post from three or more older related posts, using anchor text that describes it. This is the step most bloggers skip, and it is the one that tells Google where the post fits.
- Link out to sources where you cite a fact.
Hydrogen SEO gives each post an on-page SEO score covering length, focus keyword use, readability, links and alt text. It is an editorial prompt, and the docs are clear that search engines never see it.
The first eight weeks after publishing
In Search Console, filter the Performance report to the post's URL. Our typical experience on a blog Google already crawls often, offered as a guide rather than a promise:
- Week 1 to 2: the post is indexed and may show scattered impressions at low positions.
- Week 2 to 6: impressions widen to more queries as Google tests it; position moves around a lot.
- Week 6 to 8 and after: positions settle. For a well-chosen specific query, page one is a reasonable hope. For a competitive one, the post may need months, links and a refresh.
Blogs that publish rarely or are new sit at the slow end. If the post is not indexed after two weeks, inspect it before changing anything. If it settles on page two, the page-two playbook covers the next moves. Review the queries it attracts: they often show a better title or a missing section.
Blogging habits that hold posts back
- Posting and moving on. A post with no internal links is effectively hidden from both readers and crawlers.
- Writing near-duplicates. A new post on a topic you covered last year splits signals between the two.
- Updating the date without updating the content. Google's guidance names this as a practice to avoid.
- Indexing every tag archive. Dozens of thin tag pages compete with your posts; see noindexing tag and category archives.
- Writing for a word count. Google says there is no preferred length. Cover what the searcher needs and stop.
- Rewriting after one week. Early position swings are normal. Wait for the data to settle.
Publish-day list for every post
- One primary query checked against the live results.
- No existing post targets the same query.
- The answer appears in the opening paragraph.
- At least one piece of first-hand material.
- Author byline and publish date visible.
- Three or more internal links pointing to the post, added the day it goes live.
- A reminder to review in Search Console four weeks after indexing.
Common questions
How long does it take for a blog post to rank?
It varies with the blog's age, how often Google crawls it and how competitive the query is. On an established blog a specific post often settles within about two months. New blogs and contested queries take longer, and no timeline is guaranteed.
How long should a blog post be to rank?
Google says there is no preferred word count. The right length is whatever fully answers the query better than the current results, without padding.
Should I request indexing for every new post?
It is not needed if your sitemap is submitted and the post is linked from other pages. Save manual requests for important posts or ones you have just fixed.