Republishing content and changing dates: what Google reads, what is honest

Show one visible date on the page. Put the same date in your structured data as datePublished and dateModified where it fits. Google can read both, and prefers a page that says when it was last updated, as of 2026.

Do not bump a date without a real update. Google’s guidance says the date should reflect a significant change. A republished page keeps its URL.

• Visible date in the byline or header, for example “Updated 12 September 2026”.
• JSON-LD that names datePublished and dateModified with ISO dates, for example “2026-12-12”. This is an example format, not measured.
• Only one date format for people and machines. Do not hide dates with CSS or JS.

Change the modified date when the page got better for the query it serves. Small fixes do not count. Here is a working line between the two.

A fixed page shows an updated line near the top, plus clearer, current guidance in the body. For example, a refreshed “/guides/getting-started” adds a new step for the latest UI and removes a dead feature.

Do not change dates on a hunch. Find decay, then decide to refresh, merge or remove. Content decay is a steady loss of clicks and impressions over months while the rest holds. It happens when the results page shifts, rivals publish better work, or your facts and screenshots go stale.

1. 1

   Open Search Console, Performance, Pages

   Compare the last three months to the previous three months. If your site is seasonal, compare to the same period a year before.

2. 2

   Sort by clicks difference

   Pick falling pages. Open each page’s Queries tab.

3. 3

   Judge demand vs page fall

   If the queries lost impressions, demand fell. If impressions hold and position worsened, your page fell behind.

4. 4

   Mark decisions in a sheet

   List each URL with its clicks, impressions, date, purpose and one decision: keep, refresh, merge, redirect or remove. Repeat this audit each quarter and judge on the next quarter’s figures.

A refresh is the same URL. You update facts, rewrite weak sections for the current intent, answer new People also ask items, retake screenshots, fix dead links, and revise the title if the results page moved. Then change the modified date. A refresh is not a rewrite from scratch, and not a new URL.

Most republishing keeps the same URL. You only create a new URL when the topic changed or the intent split. Merge when two pages chase the same queries and neither does well.

When you merge, keep the URL with more links and clicks. Fold in what the other page had that was better. Redirect the other with a 301. When nothing close exists and a page has had no clicks, no impressions, no links and no purpose for a year, remove it with 410 or 404. Use a 301 only when a close equivalent exists.

Be clear with people first. Put an “Updated” line near the top. Add a brief change note if the update is material. Use the same date in markup. Do not hide the original publish date if it helps context.

• At the top: “Published 14 March 2024. Updated 12 September 2026.”
• If change is big: add a short note, for example “Added steps for the new dashboard and removed the Legacy tab.”
• If the audience needs history: add a small changelog at the end.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Republishing content and changing dates: what Google reads, what is honest",
  "datePublished": "2024-04-14",
  "dateModified": "2026-12-12",
  "author": {"@type": "Person", "name": "Your Name"},
  "mainEntityOfPage": {"@type": "WebPage", "@id": "https://yourproduct.com/blog/republish-content"}
}
</script>

A fixed “/pricing” might show new plans, a dated note on taxes, and an updated line. The JSON-LD carries the new dateModified. The URL does not change.

Do not stuff the current year into every title. Only do it where freshness is the intent, for example “2026 salary bands template”. Most evergreen guides read better without a year in the title tag.

• Keep the title under about 60 characters so it shows well.
• Update the meta description when the angle changes. Keep it honest to the new body.
• If the results page shows dates and freshness matters, make sure your visible updated line is near the top so Google can pick it up.

1. 1

   Read the current results page for your head term

   Search your head query in quotes, for example “republish content”. Note what wins, what formats appear, and the questions People also ask shows.

2. 2

   Map gaps to your page

   Mark sections that no longer match. Add answers the results page now shows. Cut lines that no longer help. Retake screenshots where the UI changed.

3. 3

   Fix links and examples

   Replace dead links. Update commands, code, and prices. Swap vague claims for worked examples, for example “/guides/getting-started” with a before and after.

4. 4

   Revise the title and intro

   Align to the current intent. Keep the URL. Keep the promise clear. Avoid clickbait.

5. 5

   Edit the update line and markup

   Set the visible updated date. Set dateModified in JSON-LD. Do not change datePublished unless the original was wrong.

6. 6

   Ship, then check Search Console

   Watch clicks and impressions over the next 28 days. If position lifts and impressions hold, the refresh worked. If not, revisit the gaps.

This approach pays off when content decay is the cause. If demand fell across the query, a date change will not move it. Consider a new topic or a different angle for that audience instead of a cosmetic update.

It can mislead readers and lose trust. Google discourages this. As of 2026, freshness signals sit with core ranking, so weak attempts at freshness do not help and can be ignored.

• If nothing changed, returning visitors spot the trick and bounce.
• Search engines can compare snapshots and links. A new date with no body change is a weak signal.
• Scaled date bumps across many pages look like manipulation rather than help. This risks falling under spam policies on scaled content abuse.

A small site wins by being useful. A page family earns when each page holds data or an answer of its own that a reader would want. Keep that bar, and your dates will read true as a side effect.

Make republishing a habit tied to your data. Keep a living sheet. Decide per page, then check the outcomes next quarter. This is what that looks like for a founder who ships alone.

1. 1

   Pull 12 months of clicks and impressions by URL

   Add inbound links, publish date, last modified date, and the page’s purpose.

2. 2

   Decide: keep, refresh, merge, redirect, remove

   Use the rules above. Add a one line reason. For example “refresh, section on pricing is 2024 and now wrong”.

3. 3

   Batch work by theme

   Refresh related pages together so internal links make sense. Link from stronger pages to refreshed ones.

4. 4

   Publish with visible update notes and JSON-LD

   Keep the same URL unless the scope truly changed.

5. 5

   Review 28 days later, and next quarter

   Log gains or misses. If a refresh missed, check intent again or consider a merge.

If you need a quick read on where to start, Porteur can scan your site and rivals from a URL and surface three findings to act on now.