大网数据广告活动
网站运营与故障问答

Why does google.com search results show a newly published post as 2 days old?

· 52CE 我爱测

We have just put up a post, less than 2 hours ago. We usually rank pretty well, including in this case. Regardless, when I search on google.com for the post by name, it comes up as the first result. However, it says the post is 2…

问题原文

原帖链接 · Andre Bulatov · CC BY-SA 3.0

We have just put up a post, less than 2 hours ago. We usually rank pretty well, including in this case. Regardless, when I search on google.com for the post by name, it comes up as the first result.

However, it says the post is 2 days old, when it's no more than 2 hours old:

I have the Schema.org markup done pretty well, and I just checked the dateCreated and datePublished and everything seems to be in order:

Deleted this image showing proper dateCreated and dateModified schema.org markup as I am only allowed to post 2 links per post


I know it's difficult to know why Google does what it does, but has anyone had this problem before? I don't think it's a common problem because no matter how I rephrase the question, I am finding 0 relevant results.

Any ideas on why this mislabeling of the article's publish date could be happening?

Update:

I just got the headers and everything seems to be correct:

Receiving Header:

HTTP/1.1·200·OK(CR)(LF)
Server:·nginx/1.9.12(CR)(LF)
Date:·Fri,·04·Mar·2016·03:01:32·GMT(CR)(LF)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Content-Length:·133023(CR)(LF)
Connection:·close(CR)(LF)
Vary:·Accept-Encoding(CR)(LF)
X-Powered-By:·PHP/5.6.18(CR)(LF)
Vary:·Accept-Encoding,·Cookie(CR)(LF)
Cache-Control:·max-age=3,·must-revalidate(CR)(LF)
WP-Super-Cache:·Served·supercache·file·from·PHP(CR)(LF)
Last-Modified:·Thu,·03·Mar·2016·22:21:02·GMT(CR)(LF)
(CR)(LF)

I've looked everywhere I can think of for a time and then looked everywhere else and I can't find any leads.

Update 2

I believe the issue may have been hAtom (h-Atom) entries. This is my only solid lead.

The way I had the time displayed for these posts was "time that has passed since publishing," (eg, "2 hours ago"). The h-Atom markup was using this "time that has passed" time, rather than the proper ISO 8601 format UTC time (eg, 2016-03-06T19:48:15+00:00) I was outputting for the schema.org markup.

The time was like this:

Now it's like this:

I am suspecting this h-Atom marked up "time ago" time because I have 0 other leads. All metas, indexes, registrations, pings, headers and everything else I can think of and of the suggestions given here is and has been correct, 'cause that's just how I roll. Maybe Google somehow misunderstood "2 hours ago" to be some date or to be "2 days ago"? But of course, why wouldn't it properly parse "days" as "days"? :/ Again, no leads.

About 24 hours after I updated the h-Atom time to the ISO format, Google search results showed the proper time, and in this specific case, the time jumped from "5 days ago"(incorrect) to "2 days ago."

已采纳解答

原帖链接 · WiTon Nope · CC BY-SA 3.0

Google will read your posts' rich snippet and based on your defined parameters it will be then shown in the SERP. If you can send us the link of your website it can help to find out the reason.

You can refer to Google's documentation here: https://developers.google.com/structured-data/rich-snippets/articles

Check that nothing is defined in your meta header tags blocking Google bots from reading the dates. Besides you have to be sure that you have verified your website into Google's webmaster tools.

I hope this helps.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2016-03-03)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。