[null,null,[],[[["\u003cp\u003eAs of April 6, 2020, Google Search will no longer support data-vocabulary.org schema for rich results and will prioritize schema.org.\u003c/p\u003e\n"],["\u003cp\u003eSearch Console will issue warnings for pages using data-vocabulary.org to allow webmasters time to replace it with schema.org.\u003c/p\u003e\n"],["\u003cp\u003eGoogle uses structured data to understand web page content and enable special search result features.\u003c/p\u003e\n"],["\u003cp\u003eStructured data formats like JSON-LD, RDFa, and Microdata encode descriptive data, while schemas define terms and relationships for that data.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends converting data-vocabulary.org structured data to schema.org for continued rich result eligibility.\u003c/p\u003e\n"]]],["Google will stop supporting data-vocabulary.org markup for rich result features as of April 6, 2020, now postponed to June 2020 and then started rolling out on July 6 2020. Pages using this schema will receive Search Console warnings, signaling the need to transition to schema.org. Structured data schemas define terms for things like `Person` and `Event` and are used to understand page content and enable search result features. Converting data-vocabulary.org to schema.org is recommended to maintain eligibility for rich result features.\n"],null,["# Sunsetting support for data-vocabulary\n\nTuesday, January 21, 2020\n\n\nStructured data schemas such as [schema.org](https://schema.org/) and\n[data-vocabulary.org](https://data-vocabulary.org/)\nare used to define shared meaningful structures for markup-based applications on the Web. With\nthe increasing usage and popularity of schema.org we decided to focus our development on a\nsingle SD scheme. As of April 6, 2020, data-vocabulary.org markup will no longer be eligible for\n[Google rich result features](/search/docs/appearance/structured-data/search-gallery).\n\n\nAs a preparation for the change and starting today, Search Console will issue warnings for pages\nusing the data-vocabulary.org schema so that you can prepare for the sunset in time. This will\nallow you to easily identify pages using that markup and replace the data-vocabulary.org\nmarkup with schema.org.\n\nA bit more about structured data\n--------------------------------\n\n\nGoogle uses\n[structured data](/search/docs/appearance/structured-data/intro-structured-data)\nstandardized formats and shared schemas to provide information about a page and the things\ndescribed by the page. This information is used for two main purposes\n\n1. Understand the content of the page\n2. Enable special search result features and enhancements\n\nWhat are structured data formats?\n---------------------------------\n\n\nStructured data formats like JSON-LD, RDFa and Microdata define a small number of fixed\nstructures that can be used to encode descriptive data. They typically build upon lower-level\nstandards like JSON and HTML. To learn more about the supported and recommended formats, please\ncheck out our\n[developers guide](/search/docs/appearance/structured-data/intro-structured-data#structured-data-format).\n\nWhat are structured data schemas?\n---------------------------------\n\n\nAlongside the structured data formats, structured data schemas work like a kind of dictionary,\ndefining terms for types of thing (for example, `Person`,\n`Event`, `Organization`), and for\nproperties and relationships (for example, `name`,\n`worksFor`). By maintaining this separation between format and\nschema, it is possible for users of different formats to take advantage of the same, widely\nshared, schemas.\n\nData-vocabulary schema\n----------------------\n\n\nGoogle's \"Data Vocabulary\" project was an important milestone in the development of structured\ndata on the Web, because it led to our collaboration with other search engines to create\nschema.org. However it is now very outdated and it is generally preferable to use more widely\nshared vocabulary from Schema.org. Therefore data-vocabulary.org markup will stop being\neligible for Google search result features and enhancements.\n\n\nPlease note that this is the only consequence of this change. Pages using data-vocabulary schema\nwill remain valid for all other purposes.\n\n\nIn order to be eligible for Google rich result features we recommend converting your\ndata-vocabulary.org structured data to schema.org.\n\n\nFor example, here is how you would change the data vocabulary to schema.org\n\n### Data-vocabulary.org\n\n```\n\u003cdiv itemscope itemtype=\"https://data-vocabulary.org/Breadcrumb\"\u003e\n\u003ca href=\"https://www.example.com/dresses\" itemprop=\"url\"\u003e\n\u003cspan itemprop=\"title\"\u003eDresses\u003c/span\u003e\u003c/a\u003e\n\u003e\n\u003c/div\u003e\n\u003cdiv itemscope itemtype=\"https://data-vocabulary.org/Breadcrumb\"\u003e\n\u003ca href=\"https://www.example.com/dresses/real\" itemprop=\"url\"\u003e\n\u003cspan itemprop=\"title\"\u003eReal Dresses\u003c/span\u003e\u003c/a\u003e\n\u003e\n\u003c/div\u003e\n```\n\n### Schema.org\n\n```\n\u003col itemscope itemtype=\"https://schema.org/BreadcrumbList\"\u003e\n \u003cli itemprop=\"itemListElement\" itemscope itemtype=\"https://schema.org/ListItem\"\u003e\n \u003ca itemprop=\"item\" href=\"https://example.com/dresses\"\u003e\u003cspan itemprop=\"name\"\u003eDresses\u003c/span\u003e\u003c/a\u003e\n \u003cmeta itemprop=\"position\" content=\"1\" /\u003e\u003c/li\u003e\n \u003cli itemprop=\"itemListElement\" itemscope itemtype=\"https://schema.org/ListItem\"\u003e\n \u003ca itemprop=\"item\" href=\"https://example.com/dresses/real\"\u003e\u003cspan itemprop=\"name\"\u003eReal Dresses\u003c/span\u003e\u003c/a\u003e\n \u003cmeta itemprop=\"position\" content=\"2\" /\u003e\u003c/li\u003e\n\u003c/ol\u003e\n```\n\n\nYou can test any code snippet live on\n[Rich Results Test](https://search.google.com/test/rich-results)\nby pasting it into the search box. Try it out! And if you have any questions or comments, check out the\n[Google Webmasters community](https://support.google.com/webmasters/threads?thread_filter=(category:structured_data)).\n\n\nPosted by Dan Brickley, Standards Developer Advocate, and [Moshe Samet](https://www.linkedin.com/in/moshe-samet-5465326/), Search Console Product Manager\n\n*** ** * ** ***\n\n| **Update on 2020-04-06**: We have decided to postpone this change for the immediate future due to the Coronavirus situation. We will re-evaluate this matter in June 2020.\n| **Update on 2020-07-06**: We started rolling out the deprecation."]]
