问题原文
原帖链接 · chejnik · CC BY-SA 3.0
The website contains a bilingual dictionary with several thousand dictionary entries. Each entry is generated into own web page that is indexed by Search engines. (in other words, there are several thousand web pages)
Entry - the Name of the Dictionary
Url of the entry page
Information
The entry and the name of the Dictionary is correct (it is loaded from the name of the page). I would like to improve the Information section of the search result (now it shows the conjugation information that can be found later in the page).
Can I display the correct information by adding schema.org microdata? Are the items correctly nested inside the Book?
<div itemscope="" itemtype="http://schema.org/Book">
<div itemprop="name"> the Name of the Dictionary </div>
<div id="Entry" itemscope itemtype="http://schema.org/Thing">
<div itemprop="name"> Entry </div>
<div itemprop="description">
the whole Entry
</div>
</div>
</div>
Update I use meta description in the head of the document. Information there is general about the dictionary. It seems that this information is replaced by more relevant information directly from the web page.
<meta name="description" content="the Description of the Dictionary">
已采纳解答
原帖链接 · Bonk · CC BY-SA 3.0
After browsing the schema.org docs I could not find a suitable data type. If you can do without schema markup I would suggest using the definition list HTML element to markup your content. This will convey the context of the information on the page to search engines as a term with a definition. For example(from 2):
<dl>
<dt>Firefox</dt>
<dd>A free, open source, cross-platform,
graphical web browser developed by the
Mozilla Corporation and hundreds of
volunteers.</dd>
<!-- other terms and descriptions -->
</dl>
If you are set on using the Book item, which I don't believe to be valid, you may find using JSON-LD Schema formatting to be more efficient than inline schema format. An overview of the JSON-LD format can be found on the Google Schemas site. It is much more flexible since it is not directly tied to the HTML.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
