\n launched the Structured Data dashboard<\/a>
\n last year, it has quickly become one of the most popular features in Webmaster Tools. We’ve been
\n working to expand it and make it even easier to debug issues so that you can see how Google
\n understands the marked-up content on your site.\n<\/p>\n
\n Starting today, you can see items with errors in the Structured Data dashboard. This new feature
\n is a result of a collaboration with webmasters, whom we invited in June to>register as early
\n testers of markup error reporting in Webmaster Tools. We’ve incorporated their feedback to improve
\n the functionality of the Structured Data dashboard.\n<\/p>\n
\n An “item” here represents one top-level structured data element (nested items are not counted)
\n tagged in the HTML code. They are grouped by data type and ordered by number of errors:\n<\/p>\n
![\"Structured](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-79737a1cb9ff.png\")
<\/p>\n
\n We’ve added a separate scale for the errors on the right side of the graph in the dashboard, so
\n you can compare items and errors over time. This can be useful to spot connections between changes
\n you may have made on your site and markup errors that are appearing (or disappearing!).\n<\/p>\n
\n Our data pipelines have also been updated for more comprehensive reporting, so you may initially
\n see fewer data points in the chronological graph.\n<\/p>\n
How to debug markup implementation errors<\/h2>\n\n- \n To investigate an issue with a specific content type, click on it and we’ll show you the markup
\n errors we’ve found for that type. You can see all of them at once, or filter by error type using
\n the tabs at the top:\n <\/li>\n ![\"Over-time](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-971de5fa5e26.png\")
<\/p>\n
- \n Check to see if the markup meets the
\n implementation guidelines for each content type<\/a>.
\n In our example case (events markup), some of the items are missing a startDate<\/code> oder
\n name<\/code> property. We also surface missing properties for nested content types (for
\n example, a review item inside a product item)—in this case, this is the
\n lowprice<\/code> property.\n <\/li>\n- \n Click on URLs in the table to see details about what markup we’ve detected when we crawled the
\n page last and what’s missing. You’ll can also use the “Test live data” button to test your
\n markup in the
\n Structured Data Testing Tool<\/a>.
\n Often when checking a bunch of URLs, you’re likely to spot a common issue that you can solve
\n with a single change (for example, by adjusting a setting or template in your content management
\n system).\n <\/li>\n ![\"A](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-1de5e4b30d57.png\")
<\/p>\n
- \n Fix the issues and test the new implementation in the
\n Structured Data Testing Tool<\/a>.
\n After the pages are recrawled and reprocessed, the changes will be reflected in the Structured
\n Data dashboard.\n <\/li>\n<\/ol>\n\n We hope this new feature helps you manage the structured data markup on your site better. We will
\n continue to add more error types in the coming months. Meanwhile, we look forward to your comments
\n and questions here or in the dedicated Structured Data section of the
\n Webmaster Help forum<\/a>.\n<\/p>\n
\n errors we’ve found for that type. You can see all of them at once, or filter by error type using
\n the tabs at the top:\n <\/li>\n
<\/p>\n
\n implementation guidelines for each content type<\/a>.
\n In our example case (events markup), some of the items are missing a
startDate<\/code> oder
\n name<\/code> property. We also surface missing properties for nested content types (for
\n example, a review item inside a product item)—in this case, this is the
\n lowprice<\/code> property.\n <\/li>\n- \n Click on URLs in the table to see details about what markup we’ve detected when we crawled the
\n page last and what’s missing. You’ll can also use the “Test live data” button to test your
\n markup in the
\n Structured Data Testing Tool<\/a>.
\n Often when checking a bunch of URLs, you’re likely to spot a common issue that you can solve
\n with a single change (for example, by adjusting a setting or template in your content management
\n system).\n <\/li>\n <\/p>\n
- \n Fix the issues and test the new implementation in the
\n Structured Data Testing Tool<\/a>.
\n After the pages are recrawled and reprocessed, the changes will be reflected in the Structured
\n Data dashboard.\n <\/li>\n<\/ol>\n\n We hope this new feature helps you manage the structured data markup on your site better. We will
\n continue to add more error types in the coming months. Meanwhile, we look forward to your comments
\n and questions here or in the dedicated Structured Data section of the
\n Webmaster Help forum<\/a>.\n<\/p>\n