Stay organized with collections
Save and categorize content based on your preferences.
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:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],[],[[["Google Search now defaults the lastmod attribute's time portion to midnight UTC if omitted and requires a timezone if a time is specified."],["Invalid date or time formats, including invalid dates (like February 80th) and incorrect formatting, will result in an error."],["Google Search now accepts W3C Datetime encoding for the lastmod attribute, allowing for date-only or full date and time with timezone specifications."],["Errors associated with future dates in the lastmod attribute will no longer be displayed."]]],[]]
