FishingSEO
SEO Strategies

Published vs. Updated Dates on AI Content: What to Show

By FishingSEO••7 min read

For most AI-assisted articles, show both dates. Show the original publication date. Add a clearly labeled "Updated" date only after a meaningful change to the content. Use the same dates in your structured data. Never change a date just to make a page look fresh.

How you drafted the page, with AI or without, doesn't change the date rules. The rules depend on what happened to the content and when. The rest of this guide covers what search engines document, how to decide which date to show, and how to keep your signals consistent.

What search engines actually document

The facts below come from official documentation. They are not ranking theories.

Google estimates a "byline date" from several signals. Google's byline date documentation says it "doesn't depend on a single date factor because all factors can be prone to issues." It also says Google "doesn't guarantee" that any date will appear in search results.

Google recommends visible, labeled dates. The same page suggests showing a prominent date and labeling it with text like "Published" or "Last updated." It also says "You can provide a publication date and/or a last updated date."

Structured data should match what users see. Google recommends datePublished, dateModified, or both, in a CreativeWork type such as Article or BlogPosting. It also advises you to "Make your dates and times consistent" between the visible page and the markup. In Google's Article structured data docs, both properties are listed as recommended, not required.

Dates describe the page, not the events in it. Google says the dates "must describe the publication or update date of the page, not the stories or events described therein." It also says not to use future dates.

Fake freshness is called out directly. Google's helpful content guidance asks: "Are you changing the date of pages to make them seem fresh when the content has not substantially changed?" It also says that adding or changing content mainly to seem "fresh" for rankings won't help.

Sitemap lastmod should reflect significant updates only. Google's sitemap documentation says it uses <lastmod> only if the value is "consistently and verifiably" accurate. Changes to main content, structured data, or links usually count as significant. A copyright-year change does not. Bing has also stressed accurate lastmod values. It called out a common mistake: using the date the sitemap file was generated instead of the date the page changed.

Published, updated, and reviewed: what each date means

  • Published date: when the page first went live. It should not change, even after many revisions.
  • Updated (last modified) date: when the content last changed in a meaningful way.
  • Reviewed date (optional): when someone checked the page and confirmed it was still accurate, even if nothing changed. Google's byline documentation doesn't describe a "reviewed" date. If you use one, treat it as a note for readers and keep it separate from your dateModified value.

Which date to show: a practical decision guide

The recommendations below are our editorial view. They are based on the documentation above.

SituationWhat to show
New article, no revisions yetPublished date only
Facts, steps, prices, screenshots, or recommendations changedPublished date and "Updated" date
Typo fixes, formatting, image compression, new internal links onlyKeep the existing dates
Page fully rewritten for a different intentConsider a new URL, or show both dates and explain the rewrite in a note
Checked for accuracy, nothing changedOptional "Reviewed on" note; don't change dateModified
Evergreen reference page where readers care most about how current it isShow the "Updated" date prominently, and keep the published date somewhere on the page

Why show both on most posts? Readers get context from both: how long the advice has been around, and whether anyone has kept it current. Google's guidance explicitly allows either date or both.

When might one date be enough? News items and announcements tied to a single moment often only need the published date. Showing only an updated date can work for living reference pages. Even then, keeping the original date visible somewhere is more transparent.

What counts as a "substantial" update for AI-assisted content

AI tools make it easy to rephrase a whole article in minutes. Rewording alone is not the same as updating. As an editorial rule of thumb, a change justifies a new updated date when it changes what the reader learns or does. For example:

  • Correcting or replacing outdated facts, figures, or sources
  • Adding a new section that answers a question the page missed
  • Changing recommendations because tools, policies, or search features changed
  • Replacing screenshots or examples that no longer match reality
  • Restructuring the page after a search intent shift (see How to Audit Search Intent Drift With AI in 45 Minutes)

These changes usually don't qualify:

  • Running the text through an AI tool to "refresh" the wording
  • Swapping synonyms or changing the order of paragraphs
  • Updating the footer, copyright year, or sidebar widgets
  • Adding keywords without adding information

A simple test: could you write a one-sentence change note that a reader would find useful? If you can't, leave the date alone.

Dates are not an AI disclosure

Dates tell readers when something happened. They don't tell readers how the content was made. Google's helpful content guidance treats these as separate questions. It says AI or automation disclosures are useful "for content where someone might think 'How was this created?'" Google's guidance on AI-generated content focuses on quality and purpose, not on how the content was produced.

In practice:

  • Use dates for timing.
  • Use a byline, an editorial note, or an "About this article" line to say how AI was used, where readers would reasonably expect it.
  • Don't let an AI-driven rewrite quietly move the date forward without a real content change.

For more on transparency signals, see 7 Ways to Build Trust Signals Into AI Content and How to Turn AI Drafts into E-E-A-T Content in 7 Days.

A hypothetical example

This scenario is illustrative and not based on a real site.

A blog publishes a guide to setting up a reporting tool on March 10, 2025. In September 2026, the tool's interface changes. The editor replaces four screenshots, rewrites two steps, and removes a deprecated feature. The page now shows:

Published March 10, 2025 · Updated September 22, 2026 Update note: Steps 3 and 5 and all screenshots revised for the new interface.

The BlogPosting markup uses the same two dates. The sitemap lastmod changes to September 22, 2026.

A month later, the editor fixes a typo and adds two internal links. None of the dates change.

Implementation checklist

  1. Label visible dates clearly, for example "Published" and "Updated." Avoid an unlabeled date that could mean either.
  2. Place dates near the title or byline, where readers and crawlers expect them.
  3. Add datePublished and dateModified in ISO 8601 format, ideally with an accurate timezone, as Google recommends.
  4. Match markup to the visible dates. Check that your CMS or SEO plugin doesn't change dateModified automatically on every save.
  5. Tie sitemap lastmod to significant changes, not to template edits or the date the sitemap was generated.
  6. Minimize competing dates on the page, such as comment timestamps or "related post" dates near the byline. Google suggests this when the wrong date keeps appearing.
  7. Keep a short change note for meaningful updates, especially on pages that give advice.
  8. Add date checks to your pre-publish QA, alongside the other items in Stop Publishing AI Content Without These SEO Checks.

Conclusion

For AI-assisted content, the date question is really an honesty question. Keep the original publication date. Add an "Updated" date only when the substance changes. Make sure the visible dates, structured data, and sitemap all say the same thing. Search engines say they cross-check date signals and ignore inaccurate ones, so accurate dates are both the safest and the most useful choice for readers.

References

Back to all posts