3 ms·
Wouldn't that just be because OP's comment appeared on the article, which was posted ~1h ago, and the Google result link is to the article, not the comment dire
by cipherboy 4y ago
Wouldn't that just be because OP's comment appeared on the article, which was posted ~1h ago, and the Google result link is to the article, not the comment directly, hence has the earlier timestamp?
- taftster 4y agoAh yes, OK. My bad. That definitely sets the world back to normal then.
- thaumasiotes 4y agoIt's still a bit off; Google's index clearly contains content that wasn't present on the page at the "time of indexing". Whatever content appeared on the page after Google indexed it is something Google shouldn't know about.
- danielheath 4y agoGoogles indexing defers javascript execution. If comments are loaded via JS, they'll appear on the index with the timestamp the page was fetched, not the time its script was executed.
- metadat 4y agoHN uses notoriously scant amounts of JS, and not at all for comments, so this doesn't explain the puzzle of odd indexing behavior.