How To Resolve Misattributed Errors In The New Google Search Console

Our team put together this guide to help resolve errors with Google Search Console enhancements that are not shown in Google’s Structured Data Testing Tool. In multiple instances, our clients have seen errors for enhancements, such as Job Posting or Events, within Google Search Console that are not being shown in Google’s Structured Data Testing Tool. So, which one should we believe? Well it takes a bit of investigating, but there are a few things to look out for if you are facing this issue. First you will need to navigate to the enhancements section of Search Console to the relevant rich result to see any errors that might exist, for example Job Posting or Events.

You will then see a list of specific errors that are occurring, such as the example below with the different “Missing field” errors. When clicking on the specific url instance of an error, it will display the offending code that is prompting the error. For example, it may indicate that a property is missing, and show a code snippet where the property is in fact not there. However, if it is the same case with your website, when you navigate to the live page and run Google’s Structured Data Testing Tool, or inspect the page, you see the code is present.

First, let’s cover how to see the code in these two ways. To check this, If you are using Schema App to generate your schema markup, you can run the structured data testing tool, click on the entity on the page and then the @type property to see where the markup begins in the code. We place a comment tag above the markup, which differs depending on which content management system you use.

Alternatively, as mentioned you can view the code in your browser with the inspect function. If you are unfamiliar with the inspect functionality on different browsers, you can take a look at what’s in the code by right clicking on the web page and clicking on the option “Inspect”. From here, you will see the console pop up and then will be able to perform a search of the code with the key command Ctrl+F to find whichever item is prompting the error and confirm whether it is missing.

Our team has investigated a couple of instances where this search verifies that the markup is there, despite the disagreement with Search Console and has found a solution, where the errors decline steadily over the course of a few days, as seen here:

To resolve these occurrences, you will need to click on the error to get further details, and then click on “Validate fix”.

This can take a bit of time to run the validation, depending on the number of errors and pages. Additionally, in our experience, it will not necessarily resolve all of the errors on the first validation, thus you may need to rerun the validation to resolve the remaining issues. In each case that our team encountered we were able to resolve all of the errors after running the validation a few times and each validation can take a few days to run.

In the first example, the latest validation is still running to resolve 7 errors, but the previous few validations you can see the impact of in the decline in errors the few days prior. Whereas, in the following example the first validation was ran a few days prior to the 22nd and steadily fell up until the 29th, in which it passed the validation and showed no errors.

, , , ,
Previous Post
Schema Markup News Oct 23rd, 2018
Next Post
Structured Data & The New Google Search Console