4 ms·
> even weirder, Google says that they (currently) indexed it 56 minutes ago, when HN reports you posted it 23 minutes ago. Google is now apparently predicting t
by thaumasiotes 4y ago
> even weirder, Google says that they (currently) indexed it 56 minutes ago, when HN reports you posted it 23 minutes ago. Google is now apparently predicting the future 33 minutes in advance.
One interpretation is that Google is lying about the indexing time.
But it seems more likely in this case that they're reporting the indexing time of the page they link to ( https://news.ycombinator.com/item?id=33458756 https://news.ycombinator.com/item?id=33458756 ), rather than the indexing time of the comment you're responding to ( https://news.ycombinator.com/item?id=33459157 https://news.ycombinator.com/item?id=33459157 , which can only have been indexed half an hour ago).
In other words, they updated their cache of the page content without refreshing the indexing timestamp.
- sally_glance 4y agoYeah, they don't seem to make any guarantees at all about the date being displayed next to the search result... I'm too lazy to check the page source here right now on which meta fields are updated with comments, but this is what Google says about how they determine the date: > Google determines a date using a variety of factors, including but not limited to: any prominent date listed on the page itself or dates provided by the publisher through structured markup. > Google doesn't depend on one single factor because all of them can be prone to issues. Publishers may not always provide a clear visible date. Sometimes, structured data may be lacking or may not be adjusted to the correct time zone. That's why our systems look at several factors to come up with what we consider to be our best estimate of when a page was published or significantly updated. https://developers.google.com/search/blog/2019/03/help-google-search-know-best-date-for https://developers.google.com/search/blog/2019/03/help-googl...