# Republishing content and changing dates: what Google reads, what is honest You can republish content without gaming dates. This page shows what Google reads, when a change earns a new modified date, and when to keep the same URL. It is written for founders who ship their site and want a straight answer. Updated 2026-09-14 · Source: https://porteur.ai/guides/republishing-and-dates ## What Google reads on dates 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. > Rule: only change the modified date when the content itself changed in a way a reader would care about. ## What counts as a significant update 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. | Change | Counts for dateModified? | Why | | --- | --- | --- | | Rewrite or add sections to match search intent now shown on the results page | Yes | The answer is meaningfully different for the reader. | | Fact updates: dates, prices, steps, code samples, commands | Yes | The guidance would mislead if left old. | | New screenshots after a UI or tool change | Yes | Visual accuracy affects trust and task success. | | Fix broken links, add new references | Often | Mark as updated if the target resources are core to the page. | | Title revised to reflect the current query pattern | Often | If the body changed to match, update the date. Title-only tweaks, no. | | Typos, commas, spacing | No | No reader value. | | Swapping a sentence for style, same meaning | No | No reader value. | | Changing the visible date without edits | No | Discouraged by Google. | | Adding a paragraph about your offer unrelated to the query | No | Promotional, not an update to the answer. | 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. ## Find pages to republish: spot content decay first 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. **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. **Sort by clicks difference** Pick falling pages. Open each page’s Queries tab. 3. **Judge demand vs page fall** If the queries lost impressions, demand fell. If impressions hold and position worsened, your page fell behind. 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. ## Keep the URL, create a new one, or merge 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. | Case | What to do | Reason | | --- | --- | --- | | Same topic, stale content | Keep URL and refresh | Keeps links and history. Clear signal of continuity. | | Same topic, new angle that matches current intent | Keep URL and refresh | You serve the same need better. Avoids splitting signals. | | Two posts on one intent, both weak | Merge into the stronger URL, 301 the other | Consolidates relevance and links. | | A narrow how-to becomes a broad guide | Create a new URL, 301 old if fully covered | New scope and intent. Avoid bait-and-switch on the old URL. | | Feature removed, page has no purpose | Remove with 410 or 404 | Gone content should be gone. 410 is often processed a little faster. | 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. ## How to show updates on the page 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. ```html ``` 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. ## Titles, snippets, and dates 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. ## How to run a refresh that earns a new date 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. **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. **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. **Revise the title and intro** Align to the current intent. Keep the URL. Keep the promise clear. Avoid clickbait. 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. **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. ## Why bumping dates without changes backfires 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. ## A simple quarterly workflow 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. **Pull 12 months of clicks and impressions by URL** Add inbound links, publish date, last modified date, and the page’s purpose. 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. **Batch work by theme** Refresh related pages together so internal links make sense. Link from stronger pages to refreshed ones. 4. **Publish with visible update notes and JSON-LD** Keep the same URL unless the scope truly changed. 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. ## Questions ### Does changing the publish date help SEO? No, not by itself. Change dateModified only when you made a significant update to the content. Google can read dates and discourages date changes without real edits. If the page fell because the intent moved, fix the content and structure. Keep the URL. ### Should I show published or updated dates? Show both when it helps context. Put the updated date near the top so people and Google see it. In markup, use datePublished for the original and dateModified for the latest significant change. Use the same dates users see. ### When should I create a new URL for an updated guide? Keep the URL for the same topic and intent. Create a new URL when the scope or intent changed so much that the old promise would be broken. If the new page fully replaces the old, 301 the old URL to the new one. ### How often should I refresh content? Quarterly works for most small sites. Use your Search Console data to choose pages, not the calendar. Update when facts, screenshots or dominant results change, or when a page shows content decay. Do not bump dates for routine typo fixes. ### Do dates in titles help click-through rate? Only when freshness is the intent. News, annual roundups and time bound searches can earn a lift. Evergreen guides usually read better without a year in the title. Keep titles under about 60 characters either way. ### Is it safe to remove very old posts? Yes, when they have no clicks, no impressions, no links and no purpose for a year. Return 410 or 404. If a close equivalent exists, 301 to it. Pruning should be based on data, not a hunch. ## Read next - [How to refresh a page that lost its traffic](https://porteur.ai/guides/content-refresh): Find why a page lost clicks, refresh what searchers want now, and measure the result. Keep the same URL, update facts, sections, links and date. - [The Search Console performance report, column by column](https://porteur.ai/guides/search-console-performance-report): Every column in the Google Search Console performance report explained with the traps that trip small sites, and how to act on each. - [Content decay: pages that earned more before, and the refresh](https://porteur.ai/guides/content-decay): See how to spot content decay in Search Console, why it happens, and a clear refresh method. When to merge instead, and how to measure recovery. - [When to merge two pages, and how to do it without losing the ranking](https://porteur.ai/guides/when-to-merge-pages): Two pages target the same searches. Here is when to merge, which URL to keep, how to fold content, and how to redirect without losing the ranking. - [Delete or redirect an old page: 301, 404 or 410](https://porteur.ai/guides/delete-or-redirect-old-pages): Decide per page: 301 if a clear equivalent exists, else 404 or 410. Check links and clicks first, avoid home page redirects, and monitor what Google drops. - [Article schema: headline, images, dates and author, done right](https://porteur.ai/guides/article-schema): Use Article, BlogPosting or NewsArticle schema the way Google expects. Get headlines, images, dates and the author right, and test it before release. - [SEO for a newsletter: the archive is the content](https://porteur.ai/guides/seo-for-newsletters): Turn your newsletter into search traffic. Ship an indexable archive, clear titles, topic hubs, and the right domain setup. Works on Substack, beehiiv or Ghost. See which pages to refresh or merge: paste your URL and get a free thirty second read of your site, the searches around it and nearby rivals, with three findings shown whole. Free check: https://porteur.ai/