Why Google shows the wrong date on an article
Diagnose a wrong article date in Google Search by comparing the visible byline, structured data, timezone, and unrelated dates on the published page.
By Crawlito · 5 min read
In short
- Use separate fields for original publication and a meaningful update.
- The date of an event described in a story has a different meaning from the story's publication date.
- Google considers several signals when it estimates a byline date for a search result.
On this page
When Google shows the wrong date beside an article, compare its visible byline with datePublished and dateModified in the published HTML. Trace those values to the editorial record, including their timezone, and look for unrelated dates that dominate the page. Google estimates a byline date using multiple signals. A visible change in Search can follow a different timeline from a correction on your website. Google’s byline date guidance
Name the date you expected to see
A story published in August might cover a conference happening in November and receive a correction in September. An editor asking why Google shows “November” may mean the event date was mistaken for publication. Another editor asking why it still shows “August” may expect a correction to replace the original byline. Clarify the underlying timeline before touching the template. Three real dates can be present and only one can represent when the original article was first published.
Use a short record with the original publication, most recent material update, event or product date mentioned, and time of the current public fetch. Ask which ones are sourced from the CMS, a scheduling service, a migration, or the site build. If the entire archive acquired a new date on deployment day, the issue likely extends beyond the story that triggered the complaint. A harmless rebuild should be able to reproduce a stable article byline.
Compare the affected page with one that has never been updated and a third that has a genuine correction. Those three states force the template to show what it does with a missing update value. A fallback that uses the current time on every render can make an old story appear to change whenever the page cache expires. The content refresh guide discusses the editorial judgment behind recording a meaningful update.
Align human-readable dates and machine-readable times
Place a clearly labeled publication or update date where a reader expects to identify the article. If showing both, label them explicitly. The following example represents two different events in the life of a fictional guide. The timezone is part of the timestamp used by the system, and the human dates describe the same local calendar days.
<p>Published <time datetime="2026-08-14T09:00:00+03:00">14 August 2026</time>.</p>
<p>Updated <time datetime="2026-09-02T16:30:00+03:00">2 September 2026</time>.</p>Emit the corresponding datePublished and dateModified from the same authoritative values in the article's structured data. If you convert values to UTC for storage, preserve the intended instant through the conversion and render an intelligible editorial timezone. A story published just after midnight local time can belong to the previous calendar day in UTC. A CMS that drops the timezone and then parses the time again can introduce a one-day disagreement at exactly that boundary.
Check which entity owns the fields. A page can contain an article, related recommendations, breadcrumb data, and an event. The event's future start date can be perfectly accurate inside event markup while being wholly inappropriate as the article's publication field. Read the article structured data guide before applying one date globally to every item in a graph.
Find where the competing date originated
Examine the full response as an anonymous visitor. Look for the visible byline, event panel, related stories, automatically generated “last checked” text, comments, and any duplicated structured data. Record whether each date describes the article itself. Google advises providing a clear date and avoiding competing signals when incorrect dates persist. This does not require removing important dates from a timeline that readers need. Good labels and a clear hierarchy can make the purpose of those dates evident.
| Symptom | Test that narrows it down |
|---|---|
| Every old post shows the migration day | Compare imported publication values with the source archive |
| Only late-night articles are one day off | Inspect offsets before and after serialization |
| The visible date is correct while the markup is new | Check whether build time fills a missing modification field |
| A future event date appears beside a news story | Compare event and article entities and their visible labels |
Check the public feed and sitemap as supporting evidence about your publishing pipeline. If the feed also claims every old post was published today, the upstream mapping is a good place to investigate. The sitemap's lastmod has its own purpose; substituting it for an article's original publication date loses meaningful history. See the sitemap lastmod guide for that distinction.
Rehearse the fix across the editorial lifecycle
Write a small acceptance set using real publishing states. Include a never-updated article, one with a material edit, one scheduled near midnight in the publication's timezone, and one with an event date in the future. Inspect the visible and structured output after publication and after an unrelated rebuild. The same original timestamp should survive both. A correction should change the appropriate update field only when the editorial system records the change.
If the original timestamp was lost in a migration, use reliable records such as the old CMS export or an archived edition available to your team. Record the provenance in the editorial system. When a precise original time is unknown, do not invent minutes or manufacture a recent publication history. A defensible date that editors can explain is preferable to a perfectly formatted timestamp created from a deployment log.
After release, fetch the public article again and save the byline excerpt, its structured fields, and the release time. Compare the last indexed crawl in Search Console with the correction. A screenshot of a result is a separate dated observation, and Google may omit a visible date for some results. Your acceptance criteria should include what readers can verify directly on your page even when Search displays another estimate.
Inspect related-story cards in a real article template
A magazine may put a card for tomorrow's scheduled event immediately above the article byline. A syndication widget can also include a collection of newer headlines and dates before the main text in the document. A reader sees a clear visual separation, yet someone reading the document in order encounters several plausible dates with little explanation. Inspect the actual labels and boundaries in the published HTML in addition to the visual layout.
Use one article with an unambiguous publication date to test a template adjustment. Give related items their own clear heading, keep each card's date tied to its own headline, and make the primary article's byline easy to identify near its heading. Confirm on a phone that the primary date remains legible when the card stack changes position. Preserve dates that help readers understand the reporting. The objective is to attach each date to the thing it describes, which also makes a future debugging sample much easier to interpret.
Frequently asked questions
Should a spelling correction reset the original date?
Keep the original publication date. Use the publication's editorial standard to decide whether an update merits a separate visible modification date.
Can the date of a future event go in datePublished?
It belongs in the event information. An article's publication timestamp describes when the article itself became public.
Must a visible byline include the time and timezone?
Google's guidance allows some visible details to be omitted. When you supply equivalent dates or times in multiple places, keep them consistent.
Inspect an affected story
Use the free page check on a published article that shows the wrong date. Compare what a fresh fetch can read with the editorial dates you verified in the CMS.
Filed under Structure and schema. Topics: google, structured-data, content-refresh