How to fix a blog post stuck on page 2 of Google: 7 underrated checks
By Yurii Vasyliev7 min read

On this page
If you have a blog post stuck on page 2 of Google, the cause is usually fixable without a full rewrite. Page two means Google already finds the post relevant, so you sit closer to traffic than a post that never ranks. The gap tends to come from mismatched intent, internal competition, or a lack of anything new. Here are seven checks, in the order that wastes the least time.
What a blog post stuck on page 2 of Google tells you
Zenweb's guide to page-two pages argues that most are held back by a content and intent gap rather than a technical bug. That fits how ranking works in general. Google picks the pages that answer the query best, so a close second earns far fewer clicks. Be honest about the timeline, though. Changes need weeks to be recrawled and reassessed, and some posts never reach page one because stronger sites own the query.
Work through the checks in order. Each one is cheap to test, and the early ones can save you from rewriting a post that only needed a better link. Keep a note of the date you change each thing, because you will need it later.
1. Confirm the post really sits on page two
Open the Performance report in Google Search Console, filter by the page URL, and look at the Queries tab. The average position for a page blends every query it appears for, so one number can hide a lot. A post might rank ninth for its main query and fortieth for everything else. Check the position for the query you care about, and ignore results you see while logged in, since those are personalised. Also note impressions, because a page-two post with healthy impressions has demand worth chasing.
2. Match the search intent of page one
Search your target query in a private window and read page one as a visitor would. Notice the format: step-by-step guides, comparison lists, tool pages or forum threads. If every result is a how-to and your post is a long opinion piece, Google has a reason to rank you lower. Rework the structure to match the dominant format, and answer the question in the first few lines. Matching the format costs far less than adding another thousand words.
3. Look for another page on your site competing with it
When two of your pages target one keyword, Google may rank only one of them. A reply in the Dumb SEO Questions group on Facebook describes exactly this: a homepage and a blog post aiming at the same keyword, so Google does not rank both. Search site:yourdomain.com keyword to see which pages Google associates with the query. If a weaker page outranks your post, merge the two, or shift the weaker page's focus and link from it to the stronger one. Our guide to checking why a blog gets no traffic from Google covers related diagnosis.

4. Add information the top results leave out
Matching what page one covers earns you a seat, but adding something new gives Google a reason to move you up. Ahrefs' explainer on information gain defines it as the extra information a page contributes beyond what already ranks. It also notes that Google has never confirmed a literal information gain score. The practical logic holds anyway. A reworded copy of the top results lands in the same semantic spot as the originals. Read the top five results, list the points they share, then ask what all of them leave out.
Original data is one of the most defensible additions. Ahrefs cites an On-Page.ai study of 150 top-3 pages, in which pages with 15 or more unique data points averaged an information gain score of 62, against 40 for pages with one or none. Padding a post with junk numbers will not work, though. Picture a small bakery supplier's blog with a post on proofing dough. Adding its own log of proofing times at three kitchen temperatures gives readers something no other result offers.
5. Point stronger internal links at the post
Internal links tell Google which pages matter, and they pass authority along. Backlinko's guide to getting more blog traffic says internal linking sends authority to key pages and also helps readers find older posts buried in the feed. Find your three strongest posts by traffic and add a contextual link from each to the stuck post. Use anchor text that names the topic, not "read more". A content hub that groups related posts gives you a natural place to do this. Links from other sites help too, but your own pages are the part you control this week.
6. Rewrite the title and opening for clicks
A page-two post earns few impressions per query, so a weak title costs you twice. In Search Console, compare its click-through rate with your other pages in similar positions. Rewrite the title so it states the outcome and puts the main query near the start. Then check the introduction. Search Engine Journal's piece on writing blog introductions advises using the target keyword in the opening lines and making a clear promise about what the reader will learn. Keep the title short enough that Google does not truncate it.
7. Update in one batch, then wait and measure
Make your changes together, record the date, and then leave the post alone for several weeks. Editing every few days makes it impossible to tell what worked. After a meaningful update, you can request reindexing with the URL Inspection tool in Search Console, which prompts a recrawl but promises nothing. Then compare position, impressions and clicks for the target query across equal date ranges before and after.
If the post needs a deeper rebuild, Search Engine Land's 10-step guide to writing a blog post is a reasonable outline to work from. For site-wide habits, our WordPress blog post SEO checklist separates what to do before and after publishing. Expect results in weeks to months. A few posts will stay on page two because bigger sites own the query.
A worked example from a small site
Imagine a garden centre's blog with a post on pruning roses that sits at position 14. Page one is full of step-by-step guides with photos, while the post reads as a general essay. The owner restructures it into steps, adds a table of pruning dates from her own regional records, and links to it from her three most visited posts. She also rewrites the title, notes the date, and checks Search Console six weeks later. The post might reach page one, or only the bottom of page two, and either result tells her what to adjust next.
Action steps
- Pull the real position: Filter Search Console by the post's URL and check its position for the main query, not just the page average.
- Compare against page one: Search the query in a private window and note the dominant format, then restructure your post to match it.
- Hunt for internal rivals: Use a site: search for the keyword and merge or refocus any page that competes with the stuck post.
- Add one original element: List what the top five results share, then add your own data, example or angle that none of them include.
- Link and retitle: Add contextual links from your three strongest posts, and rewrite the title and opening lines for clarity and clicks.
- Record, wait and compare: Note the change date, leave the post alone for several weeks, then compare equal date ranges in Search Console.
Frequently asked questions
Does being on page two mean Google has penalised my post?
Not usually. Page two most often means Google finds the post relevant but sees stronger answers elsewhere. Penalties are a separate issue, and Search Console would report a manual action in its own section.
How long does it take to move from page two to page one?
It varies. Google needs time to recrawl and reassess the page, so think in weeks to months rather than days. Some posts never move because stronger sites own the query.
Should I build backlinks to a page-two post?
Links from other sites can help, but start with what you control: intent, internal links, title and added information. Avoid shortcuts that trade links in bulk, since quality and relevance matter more than quantity.
Should I rewrite the post or publish a new one?
Update the existing post first. It already has some visibility and history. A new post on the same keyword can compete with it, so merge duplicates instead of publishing a second version.