Most sites put their effort into publishing new content while older posts quietly lose ground. Information goes stale, competitors publish better pages, and search intent shifts. Updating an existing post is often the fastest way to gain traffic, because the URL already has history, indexing, and in many cases backlinks. A strong update keeps all of that and makes the page competitive again. This guide covers how to choose which posts to update, what to actually change, and how to handle publish dates honestly.

Why Update Instead of Writing Something New

Publishing a new post on a topic you've already covered creates two pages competing for the same searches, which is keyword cannibalization. It also starts the new page from zero: no links, no history, no established rankings.

Updating the existing post in place keeps everything the URL has earned and consolidates your effort into one stronger page. This is the approach we follow on TopWebPositions: when a guide needs refreshing, we update it at the same URL rather than publishing a new "updated" version.

Step 1: Find the Posts Worth Updating

Not every old post needs attention. Google Search Console shows you which ones will repay the effort.

Posts losing ground

In the Performance report, compare the last three months with the same period a year earlier and sort pages by the change in clicks. Posts with significant declines are the first candidates. Before rewriting one, confirm the decline is about the post itself and not a site-wide issue. The guide to diagnosing a traffic drop covers how to tell the difference.

Posts almost on page one

Posts with an average position between roughly 5 and 20 for valuable queries are already relevant in Google's eyes. A targeted update can often push them up. These are usually the highest-return updates.

Posts with outdated information

Any post that references old statistics, retired product features, changed guidelines, or past years needs updating regardless of traffic. Outdated advice undermines trust in the rest of your site.

Posts that should be merged

If you find two or more posts covering nearly the same topic, the right update may be combining them into one comprehensive post and redirecting the others. A content audit is the systematic way to find these.

Step 2: Study What Ranks Now

Search the post's main queries and look at the current top results. Ask:

• Has the intent changed? If the results now favor a different format, such as a checklist instead of an essay or a tool instead of a guide, your update needs to match.
• What do the top pages cover that yours doesn't? List subtopics, questions, and examples you're missing.
• What's more current about them? New data, recent screenshots, or updated recommendations.

The Competitor Analysis tool compares your page side by side with up to two of the pages outranking it, covering titles, headings, content depth, and technical signals. Use the Page Content Analyzer to compare readability and structure.

Step 3: Make Substantial Improvements

An effective update changes the substance of the page, not just the wording. Focus on what genuinely makes it more useful.

Fix what's wrong or outdated

Correct inaccurate information, replace old statistics with current ones and cite the source, update screenshots and instructions for current interfaces, and remove advice that no longer applies.

Fill the gaps

Add the subtopics and questions you found missing in Step 2. Expanding coverage is usually where an update earns most of its ranking improvement. Add only what serves the reader, though. As the guide to blog post length explains, length itself isn't the goal.

Improve the answer near the top

Make sure the opening section answers the main question clearly and directly. This helps readers and makes the page a stronger candidate for featured snippets and AI-generated answers. The upcoming guide to winning featured snippets covers how to structure answers.

Add experience and evidence

Original examples, real data, and first-hand observations are what generic competing content can't replicate. The E-E-A-T guide explains why these signals matter.

Improve structure and readability

Break up long paragraphs, add descriptive subheadings, and use lists where they help scanning. Check the outline with the Heading Structure Checker.

Step 4: Update the On-Page Elements

• Title tag: refresh it to reflect the improved content and current intent. Remove outdated years. Check length with the SERP Snippet Counter.
• Meta description: rewrite it to reflect what's new and useful about the page.
• Internal links: link from the updated post to newer related content, and add links to it from relevant newer posts.
• Broken links: older posts accumulate dead links. Check every link with the Broken Link Checker and fix or remove the broken ones.
• Images: replace outdated images and make sure each has descriptive alt text.

Step 5: Keep the Same URL

Don't change the URL during an update, even if the old slug isn't perfect. The URL carries the page's history and backlinks. Changing it means relying on a redirect, which adds risk for little benefit. If the old slug includes something misleading, such as a past year, weigh carefully whether changing it is worth it. If you do change it, set up a 301 redirect from the old URL.

Step 6: Handle Dates Honestly

Google's guidance on dates says to show clear dates to users, label them, for example "Published" or "Updated," and keep them consistent with your structured data. It supports showing a publication date, a last-updated date, or both.

Practical rules:

• Update the modified date only after a substantial update. Changing the date after fixing a typo misleads readers who expect meaningful changes, and it's the kind of freshness manipulation that erodes trust.
• Keep the original publish date. Show the update as a separate "Updated" date.
• Update structured data to match. Set dateModified in your Article markup to the update date and keep datePublished as the original.
• Consider a short editor's note at the top summarizing what changed, especially for major revisions.

Step 7: Request Recrawling and Measure

After publishing the update, use URL Inspection in Search Console to request indexing so Google sees the changes sooner. Record the date and what you changed.

Give it several weeks before judging. Compare the period after the update with an equivalent period before, looking at impressions, average position, and clicks for the post's main queries. Updates on posts that were already close to page one often show results first.

Make Updating a Routine

Instead of updating posts only when traffic falls, build a regular cycle. Each quarter, review your top posts and your declining posts in Search Console, choose a handful to update, and add them to your content calendar alongside new posts. A blend of new and refreshed content keeps a site growing. The upcoming guide to how often you should publish covers how to balance the two.