{"id":95,"date":"2017-09-12T19:53:32","date_gmt":"2017-09-12T19:53:32","guid":{"rendered":"https:\/\/www.w3.org\/community\/gao\/?p=95"},"modified":"2017-09-12T19:53:32","modified_gmt":"2017-09-12T19:53:32","slug":"toyota-motor-europe-use-of-schema-org-and-auto-schema-org-vocabularies","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/gao\/2017\/09\/12\/toyota-motor-europe-use-of-schema-org-and-auto-schema-org-vocabularies\/","title":{"rendered":"Toyota Motor Europe use of schema.org and auto.schema.org vocabularies"},"content":{"rendered":"<p>Toyota Motor Europe (TME), led in the area of Semantic SEO by <a href=\"http:\/\/makolab.com\" target=\"_blank\" rel=\"nofollow\">MakoLab SA<\/a> and <a href=\"http:\/\/www.heppresearch.com\/\" target=\"_blank\" rel=\"nofollow\">Hepp Research GmbH<\/a>, has implemented elements of schema.org core and auto.schema.org extension vocabularies in their websites across Europe.<\/p>\n<h2>The scope of the vocabularies use<\/h2>\n<p>In particular, TME\u2019s Models and Specification Pages (e.g.\u00a0<a href=\"https:\/\/www.toyota.co.uk\/new-cars\/rav4\/index\/specifications\" target=\"_blank\" rel=\"noopener nofollow\">Spec1<\/a> , <a href=\"https:\/\/www.toyota.de\/automobile\/auris\/index\/specs\" target=\"_blank\" rel=\"noopener nofollow\">Spec2<\/a>) and Grades Details Pages (e.g. <a href=\"https:\/\/www.toyota.dk\/new-cars\/aygo\/grade\/up1\" target=\"_blank\" rel=\"noopener nofollow\">Grade1<\/a>, <a href=\"https:\/\/www.toyota.bg\/new-cars\/aygo\/grade\/bgx-s\" target=\"_blank\" rel=\"noopener nofollow\">Grade2<\/a>)\u00a0contain schema.org markup with types and properties from both core of schema.org and the automotive extension. In some other pages (like the main car pages (e.g. <a href=\"https:\/\/www.toyota.fi\/autot\/yaris\/index.json\" target=\"_blank\" rel=\"noopener nofollow\">Main1<\/a>, <a href=\"https:\/\/www.toyota.fr\/new-cars\/yaris\/index.json\" target=\"_blank\" rel=\"noopener nofollow\">Main2<\/a>) there is schema.org markup targeting the display of Google Rich Snippets (price\/reviews).<\/p>\n<p>As an example of the use, let us see the use of the type <a href=\"http:\/\/auto.schema.org\/EngineSpecification\" target=\"_blank\" rel=\"noopener nofollow\">EngineSpecification<\/a> and the properties: <a href=\"http:\/\/auto.schema.org\/vehicleEngine\" target=\"_blank\" rel=\"noopener nofollow\">vehicleEngine<\/a> and\u00a0<a href=\"http:\/\/auto.schema.org\/vehicleConfiguration\" target=\"_blank\" rel=\"noopener nofollow\">vehicleConfiguration<\/a>in the following construct:<\/p>\n<pre>(\u2026)\r\n   \"@type\": [ \"Car\", \"ProductModel\"],\r\n    \"name\": \"Toyota AYGO x Hatchback 5-d\u00f8rs 1.0 VVT-i (69 hk) 5-trins manuelt\",\r\n    \"description\": \" \",\r\n    \"image\": \"https:\/\/images.toyota-europe.com\/dk\/ag\/width\/1200\/exterior-right-front.jpg\",\r\n    \"vehicleConfiguration\": \"AYGO 5-d\u00f8rs hatchback 1.0 VVT-i x\",\r\n    \"vehicleEngine\": {\r\n                       \"@type\": \"EngineSpecification\",\r\n                       \"name\": \"1.0 VVT-i (69 hk)\"\r\n                     },\r\n(\u2026)<\/pre>\n<p>While the use of auto.schema.org seems to be quite modest in its scope, the size of the set of URLs that contain elements of the markup is impressive: our post-implementation\u00a0assessment shows that objects of type Car are in almost 7000 URLs from the entire TME web landscape \u2013 already\u00a0indexed by Google!<\/p>\n<h2>What are the effects of the markup?<\/h2>\n<p>So far, the fundamental effect of the markup will be to feed Google\u2019s Knowledge Graph. For example, we can already see that Google is looking for this data as per example of the Knowledge Panel:<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-100 size-medium\" src=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg2-300x215.png\" alt=\"\" width=\"300\" height=\"215\" srcset=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg2-300x215.png 300w, https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg2.png 617w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a> <a href=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-99 size-medium\" src=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg1-228x300.png\" alt=\"\" width=\"228\" height=\"300\" srcset=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg1-228x300.png 228w, https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/kg1.png 581w\" sizes=\"auto, (max-width: 228px) 100vw, 228px\" \/><\/a><\/p>\n<p>It is expected and highly anticipated, that the manufacturer\u2019s websites with Schema.org markup will be very trustworthy source of information for Google, and the data in the Knowledge Panel will be coming from this source.<\/p>\n<p>However, as the life of the markup\u00a0has just started, we suspect that the data marked up with Schema might be used for example in Tabular Search Results or so called \u201cDirect Answers\u201d:<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/da1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-101\" src=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/da1.png\" alt=\"\" width=\"582\" height=\"320\" srcset=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/da1.png 932w, https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/da1-300x164.png 300w, https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/da1-768x421.png 768w\" sizes=\"auto, (max-width: 582px) 100vw, 582px\" \/><\/a><\/p>\n<p>Today we can see that the data comes from various websites\u2019 content (for example from Wikipedia, manufacturer\u2019s websites and other), but we suspect they might be soon based to a higher extent on the most reliable data which is the structured markup embedded into the pages of the manufacturer website.<\/p>\n<p>It also worth noticing that the use of schema.org in the TME pages brings Google Rich Snippets to life:<\/p>\n<p><a href=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/rs1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone wp-image-102\" src=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/rs1.png\" alt=\"\" width=\"582\" height=\"120\" srcset=\"https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/rs1.png 754w, https:\/\/www.w3.org\/community\/gao\/files\/2017\/09\/rs1-300x62.png 300w\" sizes=\"auto, (max-width: 582px) 100vw, 582px\" \/><\/a><\/p>\n<h2>Conclusion<\/h2>\n<p>Despite using a small part of the schema.org and automotive extension vocabularies in the TME websites the early results are quite promising and show the impact of the schema.org markup on the Customer Search Experience related to the manufacturer.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Toyota Motor Europe (TME), led in the area of Semantic SEO by MakoLab SA and Hepp Research GmbH, has implemented elements of schema.org core and auto.schema.org extension vocabularies in their websites across Europe. The scope of the vocabularies use In &hellip; <a href=\"https:\/\/www.w3.org\/community\/gao\/2017\/09\/12\/toyota-motor-europe-use-of-schema-org-and-auto-schema-org-vocabularies\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":6797,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"yes","footnotes":""},"categories":[1],"tags":[],"class_list":["post-95","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/posts\/95","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/users\/6797"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/comments?post=95"}],"version-history":[{"count":11,"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/posts\/95\/revisions"}],"predecessor-version":[{"id":110,"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/posts\/95\/revisions\/110"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/media?parent=95"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/categories?post=95"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/gao\/wp-json\/wp\/v2\/tags?post=95"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}