谷歌的索引錯誤解釋是一個微弱的死後

谷歌的索引錯誤解釋是一個微弱的死後

TWSEO觀點:

Yesterday Google Google experienced, which ultimately impacted our sites and our clients sites. They just repeated that there were issues and what they did to communicate about the issues and that no one likes that there are issues. Yea, I get it.

But if you read post mortem from other companies, such as numerous AWS examples, AWS gets into what went wrong, how the issue happened and what they are going to do to prevent it from happening again. Just see the Google to do the same – although I think AWS has similar security concerns that Google may have? But at least tell us why Google had indexing issues.

Indexing new content maybe had a bottleneck issue? Losing content from Google‘s index may have been to someone deleting something and then that replicating through the data centers? I mean, AWS specifically goes through what went wrong, why it escalated to a bigger issue and what they will do to prevent it from happening again. Of course, AWS has paying customers with SLAs, so there is a difference.

But I don’t see anything new that we did not know from this Google said they would

Kudos to

Here’s us sharing what happened last week in Search, what we’ve learned from it and what we’re doing about it now 🙂

This post was long in production to cover the April issue in depth, to help give some insight. It wasn’t written on Friday. That’s why there was no time to get into that. Plus, the real focus is more about how we’ve learned to react in such cases with improving communication.

— Danny Sullivan (@dannysullivan) Twitter.

“>

Close Menu