April 14, 2006
With our
recent infrastructure changes,
we’ve made some minor changes in how we process the
lastmod attribute.
If you omit the time portion, it defaults to midnight UTC (00:00:00Z). If you specify a time, but
omit the timezone, you’ll get an invalid date error. You’ll also get an invalid date error if you
specify an invalid date or time (like February 80th) or the date isn’t in the correct format.
You’ll no longer see errors associated with future dates.
Dates must use
W3C Datetime encoding,
although you can omit the time portion. For instance, the following are both valid:
- 2005-02-21
- 2005-02-21T18:00:15+00:00
How we apply this
Google announcements age. We keep this post here for the record, and we note for clients whether the behaviour it describes still applies today or has since been superseded.
Related services