Google indexing issues are resolved. Google just confirmed that yesterday’s indexing issues have been fully resolved. Google’s indexing issues are resolved and Google is once again able to both crawl, index and rank fresh new content within minutes. Google has now officially confirmed this and our tests seem to show that this is the case.
Google indexing issues are resolved
Google stopped displaying new content in its search outcomes in the early morning hours yesterday. If you filtered the news or web search results from sites that frequently published content, it would only show you content on August 8th, around 3 am ET. This was comparable to last May’s indexing problems.
Google has now confirmed that this story has been resolved and updated to reflect this. Here is a confirmation from Google:
We’re aware of reports of indexing issues that are impacting some sites beginning earlier today. We’ll provide another update when we have more information to share.
— Google Webmasters (@googlewmc) August 8, 2019
Now, if you filter content from news sites, Google will show content within minutes of publishing content. On my private blog, I was able to check it out and Google indexed the content in minutes. Here’s a screenshot of Google indexing a story I wrote this morning around 7:20 a.m. and showing it in the search results minutes later:
Google’s John Mueller believes it’s solved as well. John answered my tweet stating “We are still waiting for some final confirmations, but now I believe things look great.”
— Barry Schwartz (@rustybrick) August 9, 2019
If you saw a dip yesterday in your Google traffic, and a lot of your traffic usually comes from new content, you may have seen a drop in your Google News, Google Discover and other traffic sources from Google. Performance reports from your Google Search Console may also reflect the indexing issue.
Also Read: How to sign up for the Twitch Studio Beta
The issue appeared to be around 3:00 a.m. ET from 8 August to about 3:00 a.m. ET on the 9th of August. But again, on the specifics of the issue, we are waiting for an official response from Google.