Google may show a date next to your result, but it estimates that date from several signals. This guide covers what Google documents about byline dates, structured data dates, and sitemap lastmod, and why changing a date without changing the content is a bad idea.
Google calls the date shown in results a byline date. It defines this as the date Google estimates the page was published or last updated. Google may show it when it seems useful to users, and it does not guarantee display.
Google says it uses several factors to work out the date, because all factors can be prone to issues. That means no single field decides it. Your job is to give clear, consistent signals so the estimate is right.
Google's first recommendation is a visible date. Show it prominently and give it a clear label, such as Published or Last updated. You can show a publication date, an update date, or both. Google's examples include Posted Feb 4, 2019, and Updated Feb 14, 2019 8pm ET.
Use the date that reflects when the page was published or updated. Google says not to use future dates or the date of an event described on the page. For events, use Event markup. If Google picks a wrong date, Google suggests considering removing other dates from the page.
Pages meant for Google News should also follow the additional guidelines for that product. Google's byline date page links to them. The dates guidance above applies to Search more broadly.
The second recommendation is structured data. Use a CreativeWork subtype such as Article, BlogPosting or VideoObject, and set datePublished, dateModified, or both. Google's Article documentation marks both as recommended, not required. Both use ISO 8601 format, for example 2024-01-05T08:00:00+08:00.
Include a time zone. Google says that if you do not, it uses the time zone of Googlebot. A time is optional, but adding time and time zone adds precision. If you give a time zone, make sure it is correct, including daylight saving time where it applies. The visible date and the structured data date should match.
Dates sit next to bylines, so mind the author markup as well. Google's Article documentation recommends an author property of type Person or Organization. Mark up every author shown on the page, each as a separate entry. The author name field should hold only the name, without job titles, honorifics or words such as posted by. Add an author URL that points to a page identifying the author, such as a bio page.
Google's guidance on creating helpful content lists a warning sign under search engine-first content. The question it asks is whether you are changing the date of pages to make them seem fresh when the content has not substantially changed. The page was last updated 2026-10-05.
This is a quality warning, not a technical rule. Google does not state a specific penalty in that sentence. The safe approach is to update the date only when the page has real changes, and to say what changed.
An XML sitemap can carry a lastmod value for each URL. Google's sitemap documentation says Google uses it if it is consistently and verifiably accurate, for example when it matches the page's last modification. It should reflect the last significant update. Changes to main content, structured data or links generally count. Changing a copyright date does not.
If lastmod does not match real changes, Google may ignore it. Google also ignores the priority and changefreq values. One sitemap is limited to 50MB uncompressed or 50,000 URLs. Lastmod applies to XML sitemaps. The page does not mention it for RSS, Atom or text sitemaps.
Show one clear Published date and, if you update, one Last updated date. Mirror both in datePublished and dateModified with a time zone. Drive sitemap lastmod from the same real edit timestamp, and do not bump it for template or copyright changes. Keep a short note on the page describing what changed. Review old posts before editing dates: if the content has not substantially changed, leave the date alone.
Sources were last checked on October 13, 2026. Documentation changes, so confirm any detail that matters to a decision against the source itself.
Indexive Research. (2026, September 16). Publication dates and content updates in Google Search. Indexive AI. https://indexive.ai/research/publication-dates-and-content-updates
Straight answers about how we work. Still have a question? The free audit is the fastest way to get one answered for your site.
No. Google says it may show a byline date when it seems useful to users, and it does not guarantee display.
A free execution audit: your prioritized backlog, effort estimates, and what we'd ship first. Read-only access, no contract.