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

Advantages / disadvantages of adding schema.org markups in excess?

· 52CE 我爱测

I've been adding schema markups on my customers' websites but I have a belief that we shall not add markups in excess on a particular page. Sometimes there are opportunities to add a lot of extra schema markups apart from the one…

问题原文

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

I've been adding schema markups on my customers' websites but I have a belief that we shall not add markups in excess on a particular page.

Sometimes there are opportunities to add a lot of extra schema markups apart from the one which is relevant to the page.

For eg. - If the page is about a Product or Service then I consider adding relevant structured data like Product or Service, along with breadcrumbs.

However, I can think of adding a lot of other schema markups on the same page but is it ethical or helpful?

  • Organization Logo, Website Social links, Sitename
  • SiteNavigationElements
  • WebPage schema with all links marked up
  • VideoObject schema(if there is a video in sidebar or description)
  • SearchAction markups (in JSON-LD)

I may let my clients feel that I added a lot of structured data on their website but I think adding duplicate markups on all pages would be spamming of structured data.

Would be really great if some expert can share thoughts on this.

已采纳解答

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

You decide how much structured data (whether with Schema.org or any other vocabulary) you provide, just like you also decide how much content you provide.

Just like there is no one that could dictate that your blog post must not cover more than 5 different topics, must not be longer than 10.000 words, or must not mention more than 50 persons, there is no one that could dictate that you must not provide more than 20 Schema.org entities, or must not use more than 50 properties.

In general, more good data is better than less good data, right? Consumers (whether humans or bots) can parse your documents and decide for themselves which of the structured data they are interested in, and ignore the rest. That’s the advantage right there: more structured data = possibly more/better use for consumers.

Disadvantages? None directly. Of course file sizes (and thereby, loading times) increase, and you have to invest more work (for implementation as well as maintenance), so you might want to do a cost–benefit analysis.

In the words of Schema.org

From their Getting Started documentation:

More is better, except for hidden text. In general, the more content you mark up, the better. However, as a general rule, you should mark up only the content that is visible to people who visit the web page and not content in hidden div's or other hidden page elements.

From their FAQ:

Q: Why should I add markup? What will I get out of it? How will the data be used?

Search engines are using on-page markup in a variety of ways. These projects help you to surface your content more clearly or more prominently in search results. Not every type of information in schema.org will be surfaced in search results — you can refer to each company's documentation to find specific uses — but over time you can expect that more data will be used in more ways. In addition, since the markup is publicly accessible from your web pages, other organizations may find interesting new ways to make use of it as well.

In the words of the consumer Google

From their Structured Data policies:

When you have multiple entity types on a page, we recommend you mark up all entities on that page to help Google algorithms better understand and index your content.

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

资料来源与适用范围

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

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

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