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

What is the benefit of ImageObject schema org markup for images?

· 52CE 我爱测

Is there anything to indicate that marking up images as ImageObjects has any positive effect on indexing or search engine ranking or anything related (eg, rich cards/snippets)? My experience I dynamically marked up all the images…

问题原文

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

Is there anything to indicate that marking up images as ImageObjects has any positive effect on indexing or search engine ranking or anything related (eg, rich cards/snippets)?


My experience

I dynamically marked up all the images on a site with full ImageObject schema.org structured data markup in the microdata format.

The result was hundreds of entries per page, like this:

image   
    @type   ImageObject
    name    Widget
    url     https://widgetcorp.com/some-image-1.jpg
    width   
        @type   Intangible
        name    40           
    height  
        @type   Intangible
        name    40

On Search Console/Google Webmaster Tools, the Structured Schema sections showed literally 100's of thousands of ImageObjects. No errors for any of them. When any individual page type on the site was tested with Google's Structured Data Test, again, all the images perfectly passed validation without errors or warnings, along with all the rest of the schema objects that were present on the page.

Yet, I couldn't detect any difference whatsoever in ranking or indexing of images or anything at all search engine related. Have you had a different experience with marking up images as ImageObjects?

EDIT 1:
Didn't mean to leave off the image filename off the URL. Just a typo - on site, I was properly passing an image file URL.

已采纳解答

原帖链接 · unor · CC BY-SA 3.0

First of all, for the image property, Schema.org expects either an URL value or an ImageObject value. This is typically the case for other properties taking an image value, too.

So for the image property, you could as well use:

<div itemscope itemtype="http://schema.org/Thing">
  <img itemprop="image" src="image.png" alt="" />
</div>

So why should an ImageObject value be used instead?

If you want to provide data about the image, you have to use ImageObject, because you can’t add properties to an URL value. Such data could be the height and width of the image, or its author, or its caption, etc.

Like it’s always the case with structured data: some consumers care about this additional data, some don’t (and ignore it).

In case of Google Search

For its image-related search features, Google typically (probably even in all cases) requires an ImageObject value (instead of an URL value). See for example these questions:

So if you care about Google’s search features and you can provide the required additional data, you’ll probably want to use an ImageObject instead of an URL value.

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

资料来源与适用范围

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

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

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