Google Explains Why The Search Console Reporting Is Not Real Time

Feb 25, 2016 • 7:51 am | comments (0) by twitter Google+ | Filed Under Google Search Engine Optimization
 

Google's John Mueller has an excellent post on Google+ explaining why the reports in the Google Search Console are delayed or not real time.

People ask Google all the time, I fixed this error a day ago and it still shows as an error in the Google Search Console. Or that they went AMP friendly and there are no reports in the AMP reporting tool in the Google Search Console days later. This is all normal, Google Search Console is known to be at least two-days behind in terms of the reporting showing up.

But it is not just two days behind, there are two primary factors when it comes to how those reports are generated. John Mueller explained there is (a) latency from crawling to reporting and (b) per-URL crawl rates differ.

  • Latency from crawling to reporting. It takes a few days (to about a week) for Search Console to display data after it's been crawled. There are various processes that run over the data, and Search Console tries to reflect the final state -- which can take a bit of time to get. This is particularly visible with an abrupt change, such as going from "no AMP pages" to "lots of AMP pages".
  • Per-URL crawl rates differ. Some URLs are crawled every few minutes, others just every couple months, and many somewhere in between. If you go from "all URLs are broken" to "all URLs are fixed" (which is awesome if you have a way to do that!), it will take some time to drop to "zero errors" in the aggregated reports. This is probably too much, but I created a simple spreadsheet to show that, feel free to make a copy & play with it: https://goo.gl/1pToL8

click for full size

For most SEOs, this is known, but this is often a newbie question we see in the forums.

Forum discussion at Google+.

Previous story: Review Stars Returning To Google Search Results
 
blog comments powered by Disqus