Refreshing old content beats writing new content

Positions five to fifteen are the zone where small improvements matter most. The page is clearly relevant, but something keeps it below the results people actually click: a missing answer, an outdated section, a weak title, or a competitor that matches the question more directly.

There's a quieter benefit too. Every new article you publish is another page to maintain, and content libraries rot. Refreshing first keeps your library smaller, more accurate and more useful, which is better for readers and for AI systems that quote you.

Open the Performance report, set the date range to the last three months, switch to the Pages tab and turn on impressions, clicks and average position. Sort by impressions and work down the list, picking pages whose average position falls in that range.

Then click into each page and open the Queries tab. You'll often see searches the page appears for but never answers directly, such as “cost”, “near me”, “for small business” or a comparison with an alternative. Those queries are your brief.

• High impressions, low click-through: the title and description need work
• Ranking for queries it doesn't answer: add a section for each
• Stats, prices or screenshots older than a year: update them
• Commercial pages that support enquiries: prioritise them over pure traffic pages

Restructure the page so each important question has its own heading and a direct answer in the first two sentences underneath. This helps readers skim, and it makes passages easier for Google's AI Overviews and other assistants to lift.

Then update everything that has aged: prices in ₹ or £, product names, platform features, screenshots and examples. Remove sections that no longer apply. Add internal links from newer related pages pointing back to the refreshed one, because new pages rarely link to older ones by default.

Google's documentation on byline dates recommends showing both a published and an updated date where it helps users, and matching them in your structured data. Its helpful-content guidance asks whether you change dates to make pages seem fresh when the content hasn't substantially changed.

The practical rule: if a regular reader would notice what's different, update the date. If they wouldn't, leave it. Use the dateModified field in your Article schema so the visible date and the structured date agree.

A URL like /blog/gst-guide-2023/ is tempting to change. But moving it means search engines have to re-evaluate the page, and any external links now go through a redirect. It's a cost you pay for a cosmetic gain.

If you must change it, say because the page now covers a different topic, add a permanent 301 redirect from the old URL, update internal links to point at the new one, and expect a temporary dip while the change is processed.

Rankings wobble for a week or two after significant edits, so don't judge the change too early. Use the compare option in the Performance report, filter to the single page, and look at clicks first: a better position that doesn't produce clicks usually points back to the title and description.

Keep a simple log of each refresh: the page, the date, what changed and the result. After a dozen refreshes you'll know which kinds of change move your pages, which is worth more than any general advice.