Data anomalies in Search Console

What's up with my graph?

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.


Product-wide notes

June 21—July 10 (New users only)

All first-time Search Console users who joined Search Console during this period will be missing site data during this period. First-time users who joined before or after this period are not affected.

Remove URLs Report

January 24-25, 2018

The Remove URLs Report was undergoing some improvements and may not have been available during this period.

Search Analytics Report & Performance Report

Dec 14-18, 2017

There was an error in counting AMP non-rich results impressions and clicks. The issue did not affect AMP appearance in search results, but you might see a drop in your data during this period.

Aug 14-15 2017

You may see a very slight decrease in numbers due to an internal logging issue.

July 14 - onward

An  incremental improvement in Google's logging system now provides better accounting for results in lower positions. This change might cause increase in impressions, but also a decrease in average positions. This change only affects Search Console reporting, not your actual performance on Google Search.   

March 24—27 (Image search)

Some data for clicks and impressions in image search was dropped. This was a logging issue, not a traffic issue.

February 7 (Image search for Germany and France only)

The design and behavior of Google image search results was standardized to match the design and behavior in all other locations. As a result, there may be an adjustment in click counts for image search result data for searches from Germany and France.

September 20, 2016

Search results on mobile devices have begun to direct users to the equivalent AMP page, in preference to the equivalent app or web page. This might result in a decrease of traffic to your app pages when an equivalent AMP page exists. 

July 28 – August 5, 2016

All traffic in Search Analytics was erroneously labeled as "Desktop" traffic in the "Devices" grouping category. This mislabeling was corrected on Aug 5 and has since been retroactively corrected for current queries.

April 27, 2016

We refined our standards for calculating clicks and impressions. As a result, you may see a change in the click, impression, and CTR values in the Search Analytics report. A significant part of this change will affect website properties with associated mobile app properties. Specifically, it involves accounting for clicks and impressions only to the associated application property rather than to the website.

Crawl Errors/Crawl Status Report

February 20-21, 2018

Some users may see lower than usual levels of time spent downloading in the Crawl Stats report during this time period. This was a reporting issue only and did not affect site appearance on search. 

January 23, 2017 (mobile apps only)

Search Console has improved the accuracy of reporting the number of app pages with URIs. This is not a change in the number of actual pages indexed, but rather an accounting change that will show a more accurate number of indexed app pages.

November, 2016 onward

(Apps only) Crawl data for apps will be updated every 3-4 days, rather than daily, in order to improve system performance.

July 4, 2016 (mobile apps only)

Some apps may see a drop in the number of pages indexed and number of indexing errors. This is due to a bookkeeping error on our part. The data now shows a more accurate count of pages that have been indexed. This change does not affect your impression or click counts.

Mobile Usability Report

August 23, 2016

App install interstitials will no longer trigger an error in the Mobile Usability report; therefore, you may see a drop in errors in this report. However, although no longer reported as an error, the presence of all types of intrusive interstitials are used as a ranking factor for pages in mobile search results.

Blocked Resources Report

January 16 - February 22, 2018

Users may see decreased counts of pages with blocked resources. This is due to a processing error on our side. Page counts should return to their correct levels within a few weeks.

Index Status / Indexed Pages

November 20, 2016

Internal index updates. These changes should have a minimal affect on end users.

May 15, 2016

A data anomaly caused a dip in the data on this day.

February 5 and 8, 2016 (mobile apps only)

Internal index updates. These changes do not affect end users so you should see no change on impressions.

Accelerated Mobile Pages Report

January 23 - February 3, 2018

Some users may see elevated levels of errors of the type "Major content mismatch" due to a processing error on our side. Correct error counts should return to their actual levels within few days.

November 13, 2017

We fixed a bug in counting content mismatch errors, therefore some users may see an increase in the number of AMP errors for their site. If you see an increase, check your site for content mismatch errors.

December 13, 2016

Search Console performed an infrastructure update that may cause a change in your data.

September 19, 2016

You might see a fluctuation in your AMP data, due to a change in our scanning process.

August 1, 2016

Some AMP pages may see a drop in errors reported. This is because the "missing structured data" and "invalid structured data" issues have been downgraded from errors to informational notes. This downgrading was done because, in the future, AMP pages will no longer need a structured data element to appear in search results.

Rich Cards Report

November 7, 2017

The Rich Cards Report no longer shows data for Jobs listings that are too stale to be eligible as Jobs rich results. Therefore you may notice a drop in the number of reported Jobs in the Rich Card report. This is a reporting change only; Search results are not affected by this change.

December 14, 2016

Search Console performed an infrastructure update that may cause a change in your data.

Was this article helpful?
How can we improve it?