Data anomalies in Search Console
On rare occasions, there might be an event in Search Console that could affect your report data. For example, if we change our data aggregation methods or there is a logging error, you might see a dip or bump in your chart. This page records known issues that might affect your data.
April 9-25, 2019
Search Console experienced a data outage that ceased on April 26. The outage affected all reports except the Performance report. All missing data from April 9-25 was replaced with the data from April 26, when data began to be available again.
April 5, 2019
Because of internal management of our Search index, some pages of your websites might have been dropped from our index for a period of a few days without any action on your part. The matter has been resolved, no further action from your side is needed.
April 3, 2019
For most enhancement reports, data is now being collected from more pages than previously reported. Because of this, you might see an increase in issues and affected items/pages on these reports.
January 24-25, 2018
The Remove URLs Report was undergoing some improvements and may not have been available during this period.
Some image search statistics were not captured during this period due to an internal issue. Because of this, you may see a drop in your image search statistics during this period. The change did not affect user Search results, only the data reporting.
All data from January 10, 2018 onward was converted to use canonical URLs.
December 1 - December 3
Some data for clicks in Google Images from mobile devices was dropped. This change only affects Search Console reporting, not your actual performance on Google Search.
May 29 onward
Job posting data is now being collected from more search results pages than previously reported. Because of this, you might see an increase in your clicks and impressions for job postings.
November 26, 2018 onward
Properties that have been migrated to mobile first indexing as part of the mobile-first indexing initiative may see a change in their index coverage status. (Migrated properties have been notified by email.) In particular, the error counts and new issues will reflect the status of mobile-first indexing. Indexed page counts are not affected by this change. This is a reporting change only; it does not reflect any changes on your site.
July 14 - August 1, 2018 onward
The Index Coverage report switched to a new, more accurate system. Because of this, you may see changes in your reported index coverage. This does not reflect any changes in your site, but a more accurate accounting system.
The system switch began on July 14 and finished on August 1, during which we were not able to record index coverage data. Index coverage data between July 14 to August 1 was estimated from the known August 1 values.
Some users may see elevated error levels of type "Crawl Issue" on their AMP URLs due to a processing error on our side. The issue is now fixed and error counts should return to their actual levels within few days
December 10, 2018 (ongoing)
The AMP enhancement report will now combine some over-specific issue types into fewer generalized issue types. When the migration is complete, you will see an increase in generic issue types with a corresponding decrease in the specific issue types that were combined into the general type. As an example, the following two issues would be combined as shown:
|Old specific issues||New generic issue|
||The attribute 'title' in tag 'a' is incorrect|
This will simplify issue types into more manageable groups for you. You should see very little overall change in your instance count. During migration you will not be able to verify issues as fixed in Search Console. To help ease the transition, we will update the previous three months of data (starting in September) to conform to this new system.
August 13, 2019 onward
Product, Sitelink Searchbox, Unparsable types
Some new issue types have been added to these rich result reports. The ability to report on these issues is new; the issues reported may or may not be new.
April 10, 2018 onward
The generic "missing or invalid field" error has been replaced by more specific error types. Existing instances of this error will be replaced by a more specific error type in this report. Items previously tagged as "missing or invalid field" will still appear in the report, but with zero instances for the remainder of the issue lifetime.