Shared publicly  - 
I'm not sure about where this thing comes from. Have a look.
Enrico Altavilla's profile photoPedro Dias's profile photoFlorian Kiersch's profile photo
That's not a Search Debug, it looks like some performance measurement on the page and stuff that loads with it... I worked with Search Debug at Google and I tell you, it looks way more interesting than that...
+Pedro Dias : many many years ago, a temporary glitch showed some debug information for each result in the SERP. This incident was reported on more than one SEO forum, at the time. I don't know if the exposed data was provided by what you call Search Debug, but I remember that when I saw it I thought that it was very similar to a typical list of ranking scores.
+Enrico Altavilla Yes, it would show that kind of information and much more. A Search Debug page turns a normal 10 results page to the same size as a 100 results page when it loads all the info. It will include anything, from query rewrites, to algos impacting that search, to experiments running, to the individual scores and boosts and demotions attributed to each result, etc, etc... I would only show it in a room after I trigger an EMP :P
+Pedro Dias : since a long time has passed, I don't remember well what the data looked like (nor I can find the old thread at but I do remember that it wasn't labeled in a very explicit way.

Each row was composed by a short label and a value, usually numerical. The meaning of the labels was of course comprehensible to the googlers, but not enough explicit to be understood by an external reader.

There were maybe ten or twenty of such rows for each search result. Since you have described a very rich output, it seems to me that what I saw either wasn't what you are referring to or  it was a very early version of the Search Debug.
The screenshot shows go/gws-vm-resource-monitor, so I would assume, this "debug information plugin" is only a small part of a full toolset.
Add a comment...