Yesterday, Google didn't index new content from many sites – including this one, the New York Times, Wall Street Journal, Fox News, and many others. Google has confirmed the problem, but has not yet confirmed that the indexing issues have been resolved. It seems to me that the indexing problems are indeed correcting. (See below, Google has confirmed that it is now resolved 4 hours after this story went live.)
In particular, I looked at a site command for both this site and NY Times and sorted the news by date and content that was not previously indexed from yesterday, and NY Times content is displayed as recently as an hour ago or less .
Here is content from the NY Times that appears (click to enlarge):
This is from Fox News (sorry if I upset someone because he only mentioned the NY Times):
Here is from this site of stories that were not indexed yesterday:
Yesterday, last night, it didn't:
Google's indexing issue where no new content is being indexed is still NOT resolved https://t.co/BwA6Xxr3NA pic.twitter.com/DPCDuHLZiP
– Barry Schwartz (@rustybrick) August 8, 2019
It also shows my stories from both Search Engine Land and Search Engine Roundtable in the web index:
And the Google Search Console URL inspection program indicates that this URL is being indexed:
Valentin, who saw this indexing early, also seems the same:
just tested a little more URL & # 39; s: the bug has now disappeared, even for 2 minute old URL & # 39; s 🎉 pic.twitter.com/gSEzfvkHZs
– Valentin Pletzer (@VorticonCmdr) August 9, 2019
Let's see how long it takes for this article to be indexed. I will post an update here if I see it indexed.
Google did not confirm that the indexing issues were resolved when I posted this story.
Forum discussion on twitter.
Update: Yes, this item is indexed within a few seconds / minutes:
Here is the web index:
Update 2: John Mueller from Google said he thinks we're good, but he's waiting for the final confirmation:
Glad to see :). We are still waiting for a number of definitive confirmations, but I think it looks good now. pic.twitter.com/Bd3rQPQOzk
– 🍌 John 🍌 (@JohnMu) August 9, 2019
Update 3: Yes, Google has confirmed on Twitter that it has been officially resolved:
This issue has now been resolved. Thank you for all your feedback en route. I wish you all a quiet weekend!
– Google Webmasters (@googlewmc) August 9, 2019
Update 4: More details will follow later from Google:
Part of our procedures now with these types of situations is sharing time frames and posting notes about the impact of Search Console. But we will do that after a full assessment has been completed. Rough timeframe is a few hours for our tweet; it was not site specific.
– Danny Sullivan (@dannysullivan) August 9, 2019