本文介绍了如何在产品提供聚合页面中处理 schema.org 微数据标记的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

示例页面是:http://www.uswitch.com/mobiles/deals/apple_iphone_4s/

此页面汇总了特定手机的所有合同交易,我希望在行中添加 schema.org 微数据,据我了解,似乎我应该用 schema.org/Offer 标记每一行

This page aggregates all contract deals for a specific handset, I am looking to add schema.org microdata on the rows and from what I understand, it appears I should markup each row with schema.org/Offer

这将导致类似:

报价 [itemOffered: x , price: a, ... 其他变体 ...]...报价 [itemOffered: x , price: b, ... 其他变体...]

Offer [itemOffered: x , price: a, ... other variations...]...Offer [itemOffered: x , price: b, ... other variations...]

这是最好的方法吗?

关于丰富片段产品"的 Google 指南:http://support.google.com/webmasters/bin/answer.py?hl=zh-CN&answer=146750&topic=1088474&ctx=topic 只列出了 AggregateOffer 的用法,但没有列出他们的指南页面上显示的每个优惠的标记.

Google guidelines for "Rich Snippets Products": http://support.google.com/webmasters/bin/answer.py?hl=en&answer=146750&topic=1088474&ctx=topic only lists the AggregateOffer usage but leaves out their guideline for the markup of each of the offers that appear on the page.

推荐答案

AFAICT,Google Rich Snippets 每页仅支持一个项目.这是有道理的,因为这完全是为了在搜索结果中更好地显示页面.因此,如果您的目标是让汇总页面在搜索结果中显示得更好,那么在汇总页面上标记各个优惠是没有意义的.

AFAICT, Google Rich Snippets supports only a single item per page. This makes sense because it's all about better displays of pages in search results. So if your goal is to have the aggregate pages display better in search results, then there's no point in marking up the individual offers on the aggregate page.

您当然可以在页面上为单个交易添加优惠标记.

You can of course till add offer markup on the pages for individual deals.

这篇关于如何在产品提供聚合页面中处理 schema.org 微数据标记的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-24 06:35