In CMS, News, SEO

As of April 6, 2020, data-vocabulary.org schema markup is no longer eligible for Google rich result features. As a preparation for the change and starting as soon as possible, Search Console will issue warnings for pages using the data-vocabulary.org schema so that you can prepare for the sunset in time. This will allow you to easily identify pages using that markup and replace the data-vocabulary.org markup with #schema.org

#Structured data #schemas such as schema.org and data-vocabulary.org are used to define shared meaningful structures for markup-based applications on the Web. With the increasing usage and popularity of schema.org google decided to focus their development on a single SD scheme.

Google uses structured data standardized formats and shared schemas to provide information about a page and the things described by the page. This information is used for two main purposes

  1. Understand the content of the page
  2. Enable special search result features and enhancements

If you have not converted to schema markup for your structured data, your rich results started to disappear from the search results page after April 6. This mean a loss in organic visibility and traffic.

Google has been issuing warnings to site owners about pages that use data-vocabulary.org markup since January. Check your Google Search Console messages to view any warnings and resolve issues as soon as possible.

What is rich results?
Rich results are designed to highlight key information and help search engines understand a page’s purpose as accurately as possible

Points to be noted

  • Google is focusing on schema markup due to its increasing usage and popularity.
  • There is an option for Site owners as they can use Google’s Rich Results Test tool to test live site.
  • This change only related to rich search results (highlight key information). Pages using data-vocabulary.org markup for other purposes will still remain valid.
Contact Us

Contact Us

Not readable? Change text. captcha txt
WordPress Vulnerability Report: January 2020WordPress Vulnerability Report: January 2020