{"id":23668,"date":"2022-12-15T11:01:09","date_gmt":"2022-12-15T11:01:09","guid":{"rendered":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/15\/google-reveals-more-information-about-search-status-dashboard\/"},"modified":"2022-12-15T11:01:09","modified_gmt":"2022-12-15T11:01:09","slug":"google-reveals-more-information-about-search-status-dashboard","status":"publish","type":"post","link":"https:\/\/mailinvest.blog\/index.php\/2022\/12\/15\/google-reveals-more-information-about-search-status-dashboard\/","title":{"rendered":"Google Reveals More Information About Search Status Dashboard"},"content":{"rendered":"

<\/a>\n
<\/p>\n

\n

Google published a new episode of the Search Off the Record podcast that reveals the reasons behind the Search Status Dashboard, what kinds of incidents it will cover and why they don\u2019t plan on translating updates to other languages.<\/p>\n

Google Search Status Dashboard<\/h2>\n

Google recently announced a new Search Status Dashboard that communicates when there\u2019s an outage.<\/p>\n

Service status pages are common to services like web hosts because it\u2019s a convenient way to communicate for both the users and the service provider.<\/p>\n

Why Google is Publishing a Search Status Dashboard<\/h2>\n

Notices of outages at Google were previously done on an ad-hoc basis via Twitter, which according to the Googlers came with downsides that made it a less than ideal solution.<\/p>\n

The podcast noted that Google promised a dashboard back in 2019, after the major search outages of 2019<\/a> where it seemed like the entire index went belly up.<\/p>\n

Gay Illyes explained:<\/strong><\/p>\n

\n

\u201cWell, one of the reasons is that we promised it in 2019, so\u2026 we said that we would have a more structured and better communication channel for Search incidents.<\/p>\n

So that was one of the motivations for the dashboard.<\/p>\n

\u2026there was a perception that we are not doing enough.<\/p>\n

So we kind of both internally and externally, and then we kind of wanted to fix that because, you know, I was told that
we have to be nice.\u201d<\/p>\n<\/blockquote>\n

Posting on Twitter Has a Lot of Overhead<\/h2>\n

The podcast segued to discuss the difficulties of choosing which outages are big enough to merit a tweet and how multiple parties had to be consulted before writing a tweet.<\/p>\n

There were no templates for the tweets, which added an additional layer of complexity to the process of communicating an outage.<\/p>\n

Lizzi Sassman explained:<\/strong><\/p>\n

\n

\u201cWell, but the actual posting is not that long. It\u2019s actually coming up with the wording. Like, that seemed to trip everyone up.<\/p>\n

In previous times we\u2019ve talked about this, it\u2019s like, \u2018What should we say and how to say it and when to say it?\u2019<\/p>\n

Gary Illyes: Yeah, that\u2019s the other thing that on Twitter, we were not using templates.<\/p>\n

So basically, every time on the spot, we came up with something, and then, if someone was around, like John, or you or someone, as in John Mueller\u2013<\/p>\n

Then we would double check, basically a peer review, and then we would post if it looks good.<\/p>\n

Lizzi Sassman:<\/p>\n

I mean, but this, it wasn\u2019t just like a peer review thing. There were way more people involved for these big messages.\u201d<\/p>\n<\/blockquote>\n

The Dashboard May Eventually Show More<\/h2>\n

The current Search Status Dashboard only covers three kinds of outages to search:<\/p>\n

    \n
  1. Crawling<\/li>\n
  2. Indexing<\/li>\n
  3. Serving<\/li>\n<\/ol>\n

    Gary Illyes explained what the three outage types cover:<\/strong><\/p>\n

    \n

    \u201cSo we map the dashboard to the major search systems, which is crawling, indexing, serving. And the incidents would go into those buckets.<\/p>\n

      \n
    1. So, for example, if for whatever reason Googlebot cannot crawl the whole internet, that would end up in the crawling bucket.<\/li>\n
    2. If there is some canonicalization problem that\u2019s affecting lots of sites, then that would end up in the indexing bucket.<\/li>\n
    3. And then if Google.com is not accessible to lots of users, then that would end up in the serving bucket.<\/li>\n<\/ol>\n

      Those three outage types are for version 1 of the dashboard.\u201d<\/p>\n<\/blockquote>\n

      The podcast revealed that they\u2019re going to see how this version of the Search Status Dashboard works out and then later on they might add other types of outages to the dashboard.<\/p>\n

      \n

      \u201cJohn Mueller:
      And what if there\u2019s just one specific feature in Search that is kind of broken? I don\u2019t know, let\u2019s say the Featured Snippets are not showing anymore.<\/p>\n

      Is that something that we would show here?<\/p>\n

      Gary Illyes:<\/p>\n

      That was a good question. In this version, we are only focusing on major incidents affecting the systems that we mentioned, like crawling, indexing, serving.<\/p>\n

      In the next iteration, we are thinking about exposing Search features.<\/p>\n

      So, for example, Top Stories or Feature Snippets or whatever, if they would go down for whatever reason, then we might communicate something about those incidents.<\/p>\n

      But in the current iteration, I don\u2019t think that we would externalize those issues.<\/p>\n

      Lizzi Sassman:<\/p>\n

      Would that be if Top Stories just stops appearing altogether, like a serving issue?<\/p>\n

      Or like certain sites saying like, \u201cI\u2019m not appearing as a top story. Like there\u2019s a problem.\u201d<\/p>\n

      Gary Illyes:<\/p>\n

      I mean either, depending on how many sites are affected.<\/p>\n

      John Mueller: And like, I don\u2019t know, related services to Search, like maybe Discover or Google News\u2026<\/p>\n

      If those went down, would that also be listed here or is this really focused on web search?<\/p>\n

      Gary Illyes:<\/p>\n

      No, that would be yet another version.<\/p>\n

      We know that some services want to appear on the dashboard, but we have to think about how to present other, basically, services.<\/p>\n

      And I just didn\u2019t have either time or nerves to think about that just yet.<\/p>\n

      Plus, I think it would be valuable to just launch V1 and then see how it goes, whether we can learn something from it.<\/p>\n

      And then see if we can improve it by including other services.\u201d<\/p>\n<\/blockquote>\n

      No Plans for Translations<\/h2>\n

      The podcast noted that there are no plans for a translated version of the new status page.<\/p>\n

      According to the Googlers, translating the dashboard announcements is too complex for the CMS they use.<\/p>\n

      They feel that using a service like Google Translate should be adequate for users who don\u2019t read English.<\/p>\n

      John Mueller started off this part of the conversation:<\/strong><\/p>\n

      \n

      \u201cJohn Mueller:<\/p>\n

      Are there plans for translations or is that already happening?<\/p>\n

      Gary Illyes: No.<\/p>\n

      Like in the current setup, it\u2019s practically impossible to have translations, and they are not even thinking about it.<\/p>\n

      Mostly because they, as in the developers of the dashboard, because the dashboard is kind of like a CMS that we share with other Google products or Alphabet products.<\/p>\n

      And it is developed to be as simple as it needs to be to serve the dashboard, itself. And no complexity to it whatsoever.<\/p>\n

      And translations would be a major complexity because then you have to load the different translations from different rows in the database that are serving the content.<\/p>\n

      \u2026Basically, if you are using Google Translate, for example, or any other translation, online translation software, then that will give you enough clue about what\u2019s happening.<\/p>\n

      Lizzi Sassman: I think with this, it\u2019s also particularly time-sensitive.<\/p>\n

      So if there was a delay to translate the thing, then that language would be behind or not having the same timeline of events, which could be an issue.<\/p>\n

      And then people might think like, \u201cOh, is this not affecting Search in French or something because it\u2019s not been translated in French?<\/p>\n

      Or it didn\u2019t happen for like three days, does that mean anything?\u201d When like, no, it just means that the translation is behind.\u201d<\/p>\n<\/blockquote>\n

      Search Status Dashboard<\/h2>\n

      The Search Status Dashboard is a good way to receive alerts about outages at Google.<\/p>\n

      There\u2019s an RSS feed (located here<\/a>) for those who use them that makes receiving notifications easy.<\/p>\n

      The usefulness of the dashboard is to help diagnose if a change in ranking is due to something wrong with the site or if it\u2019s happening across Google search.<\/p>\n

      There are many ways to listen to the Search Off the Record Podcast that are listed here<\/a>.<\/p>\n

      It\u2019s also available on YouTube:<\/p>\n