我在哪里为我的网站上的产品添加微数据?
我是将其添加到实际页面上,例如 www.mysite.com/product/samsung-58-inch-tv.html,还是将其添加到产品的汇总列表中?例如 www.mysite.com/products/tvs.html - 还是我将它添加到两者?
汇总列表包含网站销售的所有电视的列表。
我在哪里为我的网站上的产品添加微数据?
我是将其添加到实际页面上,例如 www.mysite.com/product/samsung-58-inch-tv.html,还是将其添加到产品的汇总列表中?例如 www.mysite.com/products/tvs.html - 还是我将它添加到两者?
汇总列表包含网站销售的所有电视的列表。
它不会被视为“垃圾邮件”。
谷歌、必应和雅虎都同意使用http://Schema.org上的微数据格式
任何项目/乐队/歌曲/事件/评论/评级/评论/等等,可以干净利落地标记应该是。
并且应该在有足够数据让消费者能够判断“事物”是可能成为评论主题的相同“事物”的任何地方进行,或者可能有自己的页面,或者可能在商店有一个商品页面,但也可能在制造商的网站上有一个产品页面......
这些东西的所有种类都有模式。
但是你必须做一些阅读,并且在全速投入之前,你可能需要学习一些教程。
例如,我有一个乐队。
如果人们想查看事件源/事件小部件,我会将每场音乐会标记为自己的 MusicEvent。
如果人们想点击该音乐活动的专用页面并查看整页新闻稿或其他内容,我会将该数据标记为同一活动(确保我的所有信息拼写一致,并且一致地描绘,等等)。
<section id="concert-listings">
<!-- here's where all of our concert-listings go -->
<article itemscope itemtype="http://schema.org/MusicEvent" class="concert">
<h1 itemprop="name">
<a itemprop="url" href="//nerdswithguitars.ca/events/2013-04-01/nwg_at_rancho">
Nerds with Guitars@Rancho Relaxo w/ Rorry Taillon & the Old Souls
</a>
</h1>
<dl class="specs">
<dt>when:</dt>
<dd>April 1st, 2013
<meta itemprop="startDate" content="2013-04-01T21:30:00">
<meta itemprop="endDate" content="2013-04-02T00:30:00">
</dd>
<dd>doors at 8:30 - music starts at 9:30</dd>
<dt>where:</dt>
<dd itemscope itemtype="http://schema.org/EventVenue">
<article>
<h1 itemprop="name">
<a itemprop="url" href="//ranchorelaxo.biz/rancho_live.html">
Rancho Relaxo
</a>
</h1>
<ul itemprop="address" itemscope itemtype="http://schema.org/PostalAddress">
<li itemprop="streetAddress">300 College St</li>
<li>
<span itemprop="addressLocality">Toronto</span>,
<span itemprop="addressRegion">Ontario</span>
</li>
<li itemprop="postalCode">M5T 1R9</li>
</ul>
</article>
</dd>
</dl>
<section class="details" itemprop="details">
<p>Join
<span itemprop="performer" itemscope itemtype="http://schema.org/MusicGroup">
<a itemprop="url" href="//nerdswithguitars.ca">
<span itemprop="name">Nerds with Guitars</span>
</a>
</span> and
<span itemprop="performer" itemscope itemtype="http://schema.org/MusicGroup">
<a itemprop="url" href="//rorytaillon.com">
<span itemprop="name">Rory Taillon & the Old Souls</span>
</a>
</span> as they... .... ....</p>
<p>...</p>
</section>
</article>
<!-- ......... -->
</section>
那里有很多,特别是考虑到这只是一个单一的(假的)事件,而且它只是一个需要知道的东西的简介。
门票信息甚至不包含在此处(但微数据也包含在内)。
如果您仔细观察,您会发现一个事件具有属性(名称、网站/页面、开始和结束时间)......但是它的一些属性可以具有属性。
音乐会在场地举行。
但是场地有一个名称、一个网址和一个地址。
一个地址有一条街道、一个地区、一个地区、一个国家、一个邮政编码......
音乐会也有表演者......
表演者可能是独奏者或乐队......
但每个人都可能有一个名字,可能有一个网站,会有成员 - 每个成员可能有自己的个人网站,姓名,年龄和住所(与它自己的地址),以及电话号码和在一个拥有自己的组织的日常工作
............
您可以将这些东西嵌套到永恒中。
不。
标记您希望 Google 查找、理解并返回链接的内容。
例如,如果我向 Google 提供了足够多的以 Nerds with Guitars 为特色的活动,当我这样做时,我将事件与 Nerds with Guitars 乐队联系起来,然后我将乐队名称与 NwG 网站联系起来,并与将 NwG 网站/内容添加到乐队成员的 Google+ 帐户,然后突然之间,搜索音乐可能会触发事件列表,并可能触发用户个人资料显示在搜索中,并且乐队的网站可能会显示搜索乐队正在演奏的知名活动等。
那不是垃圾邮件。
这就是所有相关且相互关联且独特的内容。
谷歌吃掉了这些东西。
这里的关键区别在于,谷歌现在采用合格的元数据(而不是旧的meta keywords
废话),并将它们捆绑在一起。
它也没有照原样。它正在对格式进行验证(以确保机器可读的东西,如日期和持续时间是机器可读的),并且还对它已经拥有的关于某事物的数据进行交叉引用。
如果有 800 个事件/视频/歌曲/t-shirts/etc 说 Nerds with Guitars 位于“//nerdswithguitars.ca/”,并且<link rel="author">
页面上指向 G+ 个人资料,那么现在一些 leet-haxx0r 会尝试将带有 Guitars url 的 Nerds 定义为“//uberhaxxed.ru/viagra-sales”,Google 很有可能会使用旧数据,而不是将这些数据包含在搜索结果中。
This is not a perfect technology, but basically, the more data gets shared, the more information Google has to work with, in terms of intelligently doing its "Big-Data" black-magic (which is pretty cool) on your stuff.
Hope that helps.
One other thing that Google doesn't really do an awesome job of telling you, on http://Schema.org, or in tutorials on the http://webmasters.google.com site (at least from what I've seen in the microdata FAQs):
An itemprop can be an itemtype, or can just be a URL/string...
It can also be BOTH an itemprop for the parent item (concert) and the itemtype wrapper (itemscope) for another item (band), at the same time.
If you were to leave an address as an itemprop, but fill the address out in a <ul itemprop="address">
, Google would take all of the text inside of that <ul>
and try to use it as the address.
You can have <a itemprop="url" href="...">
wrapped AROUND another itemprop (or even wrapped around a WHOLE sub-item, if you wanted).
<a itemprop="url" href="..."><span itemprop="name">Bob</span></a>
Also, if there's data that you really want to get in there, but doesn't make sense to put in, where it's human-readable: if you don't want to have 2013-04-01T21:30
as your actual date, for example, you can use <meta itemprop="startDate" content="2013-04-01T21:30">
.
Alternatively, for time/date properties, specifically, you can use <time datetime="...">
and Google will intelligently pull the info out of there, much as it is smart enough to pull the url
out of <a href="...">
or <link href="...">
, or <img src="...">
if you make them itemprop
s.
This isn't for stuffing entries with keywords, but rather for bridging gaps where it really just doesn't make sense to put something in plain sight, because people already have the context, but the machine doesn't.
An example: Nerds with Guitars is pretty much guaranteed to be on the bill at a Nerds with Guitars show. If you're on the homepage, looking at the widget, nobody needs to know that NwG is going to be there. Nor do they need a link back to the homepage, which they're already on.
People might like to know who else is on the bill, though. So those people should be mentioned and linked to.
In that case, you should still include meta information for the band, so that Google can link the event back.
Hope this helps a little.