Stack Exchange Icons in Google Results

Added by drnick@userstyles, Created: Jun 24, 2013, Updated: Nov 10, 2016
  • With the style applied
  • Other Stack Exchange sites
  • With the style applied (Generated screenshot)
  • Without the style applied (Generated screenshot)

Description:

Shows Stack Exchange sites favicons next to various Stack Exchange site links in Google search results. I find sites such as Stack Overflow, Server Fault, etc quite helpful, and this is designed to make those results stand out in a quick scan of the results list.

Comments and suggestions welcome.

More info
Updates:

November 10, 2016: Programmers subdomain is still showing up in Google results so put it back. Added the Security site.

November 4, 2016: Programmers site now renamed to Software Engineering.

October 26, 2016: The Programmers exchange site apparently changed names behind the scenes to Software Engineering (lol). Updated that favicon URL. Also changed to domain regex to match more top-level domains (.ca, .co.uk, etc).

April 3, 2016: Stack Exchange favicons were moved to a "Sites" subdirectory. Also changed icons to use HTTPS since Google results are secure default now.

Dec 22, 2015: Stack Exchange favicons got updated to 32x32 versions. Adjusted style to resize these back down to near 16x16, but they are less consistent now and some are sized differently or are nudged left or right.

Jul 23, 2015: Google changed results from <li> to <div> elements (which is weird, since they're still in a parent <ol>...).

Aug 8, 2013: Added styles for a few other Stack Exchange sites besides Stack Overflow. For more comprehensive coverage a user script would work better, but I like the lower overhead of a user style.

Keywords: stack exchange stack overflow stackoverflow server fault favicon google

You should to add comment and rate the style.

Discussions

+ Create discussion

Installs:
Applies to:
.*www\.google(\.[a-z]{1,4}){1,2}\/search.*

Related styles:

WARNING: This webware is not functioning properly. Please enable javascript in your browser and try again.