Yesterday, Google was not indexing new content from many sites - including this one, the New York Times, Wall Street Journal, Fox News and many others. Google confirmed the issue but has not yet confirmed the indexing issues were resolved yet. It does seem to me that the indexing issues are indeed recovering. (See below, Google has confirmed it is resolved now, 4 hours after this story went live.)
Specifically, I looked at a site command for both this site and NY Times and sorted the news by date and content previously not indexed from yesterday is and content from the NY Times is showing as recent as an hour ago or less.
Here is content from the NY Times showing (click to enlarge):
Here is from Fox News (sorry if I upset someone for listing only the NY Times):
Here is from this site from stories not indexed yesterday:
Yesterday, last night, it did not:
Google’s indexing issue with it not indexing new content 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 Google Search Console's URL Inspection tool shows this URL as being indexed:
Valentin who spotted these indexing early on also seems the same thing:
just tested some more URLs: the bug is gone now even for 2 minute old URLs 🎉 pic.twitter.com/gSEzfvkHZs
— Valentin Pletzer (@VorticonCmdr) August 9, 2019
Let's see how long it takes this article to get indexed, I'll post an update here when I see it indexed.
Google has not confirmed the indexing issues are resolved at the time I posted this story.
Forum discussion at Twitter.
Update: Yes, this article was indexed within seconds/minutes:
Here is the web index:
Update 2: Google's John Mueller said he thinks we are good, but he is waiting for final confirmation:
Glad to see :). We're still waiting for some final confirmations, but I think things are looking good now. pic.twitter.com/Bd3rQPQOzk
— 🍌 John 🍌 (@JohnMu) August 9, 2019
Update 3: Yes, Google has confirmed on Twitter that it is officially resolved:
This issue is now resolved. Thanks for all your feedback along the way. Wishing you all a calm weekend!
— Google Webmasters (@googlewmc) August 9, 2019
Update 4: More details to come later from Google:
Part of our procedures now with this type of situation is to share time frames and post notes about Search Console impact. But we'll do that after a full assessment is complete. Rough time frame is a few hours before our tweet; it wasn't site-specific.
— Danny Sullivan (@dannysullivan) August 9, 2019
