Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Maybe this is a temporary issue. I will check later in the night today and update/close this thread. [2013-02-27] For most of the world, this issue should now be resolved and non-repro, and the general consensus is that it was a Google glitch!

I searched for 'StackOverflow' on Google UK, both via the Omnibar and the Google UK homepage. The resultant URL:

Displayed results (larger image):

Error in Google results for Stack Overflow

Actual page on (larger image): screenshot

This has no resemblance to the content displayed by Google.

I have tested this using Chrome Incognito without logging into Google so there is no search bubbling and also no plugins on Chrome that are playing these tricks.

I am not tagging this as a as it seems unlikely that this is an issue within Stack Exchange control.

Searching for stackoverflow on the US or some other region specific site, this effect is not observed. But searching explicitly for stackoverflow doioig brings up a slightly different result:

Larger Image Other regions

share|improve this question
No repro. I am getting as the first result. – Oded Feb 27 '13 at 21:17
Repro, I'm seeing what Pratik is seeing – Pëkka Feb 27 '13 at 21:18
@Pekka웃 - I am on, as in the screenshot. Are you on .de? – Oded Feb 27 '13 at 21:18
@Oded yup, Maybe we are witnessing a natural miracle that occurs once a decade: a bug on Google. We will be telling our grandchildren about this :) – Pëkka Feb 27 '13 at 21:19
Norepro too, also here ( Also on – Daniel Fischer Feb 27 '13 at 21:19
Regardless - nothing we can do. This is a google issue, and seeing the disparate results, probably transient. – Oded Feb 27 '13 at 21:20
Repro, when going to my own Google ( – Martijn Pieters Feb 27 '13 at 21:21
@Oded yeah. It's a genuine bug though: it's showing my Google Plus friends' +1's for the real Stack Overflow on that result. (ah, and the quick links as seen on bPratik's screen shot) – Pëkka Feb 27 '13 at 21:23
@Pekka웃 - Glad it's not just me... although the exclusivity was appealing! – bPratik Feb 27 '13 at 21:23
Maybe, must maybe some developer put up a SO page on the site to knowingly steal the page rank, and later removed it. This is just the final phases that we may be seeing on it... – bPratik Feb 27 '13 at 21:25
@bPratik but why would Google show SO's quick links and stuff on it? That doesn't make sense. It must be a bug. – Pëkka Feb 27 '13 at 21:26
Repro on, too. – Hannele Feb 27 '13 at 21:35
I've reproduced it here. I'll report it internally tomorrow - thanks for bringing it up. – Jon Skeet Feb 27 '13 at 21:53
Still seeing this – Ben Brocka Mar 2 '13 at 17:37
@AlexandreJasmin: I'll keep an eye on it internally (I didn't report it in the end as I couldn't reproduce it the next day - but it has been reported) but I doubt that I'll be able to give any feedback here about what happened. I'll see though. – Jon Skeet Mar 3 '13 at 16:31
up vote 50 down vote accepted

So apparently this is pointing to an issue with google. If you use fiddler or wget and request you will see the following response:

Fiddler for doioig

Notice the meta refresh pointing at - it seems that a developer copied and pasted the answer from here without changing the example URL:

Apparently has pretty significant rank and authority with google - so much so that it is currently impacting what is displayed and linked for our domain. We will try to get the attention of people at google and see where this goes.

Credit goes to - there's a discussion going on about this right now.

EDIT: It appears that google has taken action and resolved this issue. At this point I am seeing our usual links for the search term "stackoverflow"

share|improve this answer
Googlebot should take the URL it's being redirect to as the canonical one (here says I'm at now) But it's the other way around. Kind of strange. – Alexandre Jasmin Mar 3 '13 at 0:21
You got someone at Google's attention: "I've reproduced it here. I'll report it internally tomorrow - thanks for bringing it up. – Jon Skeet Feb 27 at 21:53" =) – jadarnel27 Mar 3 '13 at 0:26
interesting. arguably the SO redirect is the correct one, but the practical experience for most users will be the DOI redirect. google's right to be confused. (also i'm not sure what to make of SO being ousted from google by a government programmer blindly copying code from SO. the mind boggles.) – Eevee Mar 3 '13 at 2:15
There's a reason that I like Chrome: view-source: – Alvin Wong Mar 3 '13 at 4:03
Chrome lets you view the source of a page?! Why didn't Microsoft or Mosaic or Netscape come up with this 20 years ago? It's literally the best thing ever! I'm so sick of these stupid bloated developer tools that sometimes don't even show me the original page source and instead some DOM-based markup or somesuch. – BoltClock's a Unicorn Mar 3 '13 at 6:55
@BoltClock'saUnicorn, umm... pretty much all browsers have had a view source option for as long as I've been using them. – Winston Ewert Mar 3 '13 at 7:04
I wonder if that developer still keeps his job.. – Shadow Wizard Mar 3 '13 at 8:22
@WinstonEwert It's sarcasm. – Burhan Ali Mar 3 '13 at 10:57
@WinstonEwert: sarcasm - see "whoosh!" – snemarch Mar 3 '13 at 12:15
Everybody here failed to see what @AlvinWong meant. If you opened a page that immediately redirects to another page, you won't have time to view the source code using any browser (of course you can do that, but it's not straightforward) . Go ahead, try it. But with Chrome you can simple write view-source:SOME_URL in the address bar and it will download and view the source directly without rendering/executing it. – Adnan Mar 27 '13 at 11:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .