This guide is for bloggers, small-business owners and content managers who have a pile of older posts and limited time. It covers how to find the posts worth working on, how to decide between updating, merging, redirecting or leaving a post alone, what a meaningful update involves, and how to treat dates honestly. It draws on Google’s own documentation, and where Google’s pages are silent, this guide says so.
Why refreshing is not the same as re-dating
Google’s guidance on creating helpful, reliable, people-first content includes a self-assessment list of warning signs. One of them is a direct question: are you changing the date of pages to make them seem fresh when the content has not substantially changed? The same page also warns against adding or removing content primarily because you believe it will help your search rankings.
The practical reading is simple. A refresh exists to make a post more accurate and more useful for readers. If the only thing that changes is the year in the title or the timestamp in the byline, you have not refreshed anything, and Google’s published guidance treats that as a red flag rather than a tactic.
Step 1: Find candidates in Search Console
The Performance report in Google Search Console shows clicks (how often people clicked through to your site from Google Search), impressions (how often your site appeared in results), click-through rate (clicks divided by impressions) and average position. Google’s help page notes that the default view covers the past three months, and that the date filter at the top changes the period. The page also points to a separate article for comparing periods, so check that article for the current comparison options.
- Open the Performance report for your property and select a date range long enough to smooth out short-term noise.
- Switch to the Pages view and note clicks and impressions for each URL.
- Repeat for an earlier period of the same length and put the two side by side, in a spreadsheet if needed.
- List pages where clicks, impressions or both have fallen. Add pages with high impressions but low click-through rate, since the title or snippet may be the problem rather than the content.
Keep Google’s own caveats in mind. The newest data can be preliminary and may change, search results vary by location, device and time, and chart totals can differ from table totals. Treat a decline as a prompt to investigate, not a diagnosis. For a related workflow, see our post on finding quick SEO wins in the Search Console Performance report. If the decline is sitewide rather than limited to a few posts, start instead with this guide to recovering from a rankings drop.
Step 2: Decide what each post needs
Not every declining post deserves a rewrite. Sort each candidate into one of four outcomes.
| Action | Use it when | Main risk |
|---|---|---|
| Update | The topic is still relevant, the post still matches what people want, but facts, steps or examples are out of date. | Light edits that change nothing of substance. |
| Merge | Several thin posts cover the same question and compete with each other. | Losing useful sections, or leaving the old URLs unredirected. |
| Redirect | A post is obsolete or fully replaced by a better page. | Sending readers to an unrelated page. |
| Leave | The post is accurate, still serves a small audience, or its decline is explained by lower interest in the topic. | Neglect if facts later change. |
Questions that help you choose
- Does the post contain easily verified factual errors? Google’s helpful content questions ask this directly, and errors are the clearest reason to update.
- Does it provide substantial value compared with other pages in the results? If competing pages are plainly more complete, an update needs to close that gap.
- Would you still write this post for your audience today? If not, merge or redirect rather than polish it.
- Is the topic one readers still ask about, or has interest simply moved on? A decline caused by falling demand is not a content defect.
Step 3: Make the update meaningful
A meaningful update changes what a reader gets from the page. Work through the post section by section.
- Verify every factual claim. Re-check numbers, product features, screenshots, menu names and links against current official sources. Remove or correct anything you cannot confirm.
- Re-read the search intent. Look at what currently ranks for the main query and note what readers seem to expect, such as a how-to, a comparison or a definition. Adjust the structure if your post answers a different question.
- Add what is missing. New steps, worked examples, trade-offs or common mistakes make a post more useful. Padding with extra words does not.
- Cut what is stale. Delete outdated sections instead of burying them under new ones.
- Improve the title and snippet. If impressions are healthy but clicks are weak, a clearer title that matches the content honestly can help. Do not add a year unless the content genuinely reflects it.
- Strengthen internal links. Link to newer related posts and make sure newer posts link back. Our guide to smart internal linking covers the mechanics.
- Check authorship. Google’s guidance suggests clear, accurate authorship information where readers would expect it.
Step 4: Handle merges and redirects correctly
When you merge posts, choose the strongest URL as the survivor, move the useful material into it, and redirect the retired URLs. Google’s redirect documentation explains the options.
- A 301 (or 308) status marks a permanent move, and Google treats the target as the canonical page. Use it only when you are confident the change will not be reverted.
- A 302 (or 303 or 307) marks a temporary move. The source page generally stays in results, so it is the wrong choice for a merge.
- Server-side redirects are the most reliably interpreted. Meta refresh and JavaScript redirects are fallbacks, and Google says JavaScript should be used only when the other methods are not possible.
Redirect each old post to the page that most closely answers the same question. Sending everything to the home page gives readers a poor experience. Google’s page does not discuss redirect chains or how long to keep a redirect, so those points are unconfirmed here. A sensible habit is to update your own internal links to point straight at the final URL, which avoids chains you created yourself.
Step 5: Treat dates honestly
Google’s page on influencing byline dates says a byline date is its estimate of when a page was published or updated, and that it uses several factors, including when a page was significantly updated. Following the guidelines helps Google find dates but does not guarantee one will be shown.
- Show a visible date and label it clearly, such as “Published” or “Last updated”. You can show one or both.
- Use
datePublishedanddateModifiedin structured data on an Article or BlogPosting type, and keep them consistent with the visible dates. - If you include a time, use the correct time zone.
- Dates should reflect when the page was published or updated, not the events it describes. Do not use future dates.
Google’s page does not say exactly how large a change must be before the modified date should move. Combine it with the helpful content guidance: move the “Last updated” date when the content has substantially changed, and leave it alone for typo fixes. Consider keeping the original publication date visible beside the update date, so readers can see both. Whatever theme or plugin you use, check that the visible dates and the structured data agree rather than assuming the defaults are consistent.
Common mistakes
- Changing the year in the title and the date without changing the content.
- Judging success after a few days rather than comparing like-for-like periods in Search Console.
- Deleting old posts with no redirect, leaving readers on error pages.
Key takeaways
- Google’s guidance lists changing dates to look fresh, without substantial content changes, as a warning sign.
- Use the Performance report to compare equal periods and shortlist pages with falling clicks or impressions.
- Choose between update, merge, redirect and leave based on reader value, not on a rankings hunch.
- Use server-side 301 redirects for permanent merges, pointing to the closest matching page.
- Keep visible and structured dates consistent, and move the update date only for substantial changes.
FAQ
Does updating the date of a post improve rankings?
Google’s documentation does not say so. Its helpful content guidance instead lists changing dates without substantial content changes as a warning sign. A date should record a real update.
Should I use a 301 or a 302 when merging posts?
Use a 301 for a permanent merge. Google says permanent redirects signal that the target should be the canonical page, while temporary ones leave the source page in results.
Does Google guarantee it will show my updated date?
No. Google states that following its date guidelines helps it find and process dates but does not guarantee a date will appear in results.
How do I know whether a decline is worth fixing?
Compare equal periods, check whether impressions or clicks fell, and ask whether the topic itself has lost interest. Remember Google’s caveat that results vary by location, device and time. If the drop is sitewide, read our rankings drop guide first.