Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

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

Fiddler for doioig

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

http://stackoverflow.com/revisions/5411601/3https://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - 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"

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

Fiddler for doioig

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

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - 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"

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

Fiddler for doioig

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

https://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - 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"

added 158 characters in body
Source Link
Geoff Dalgas
  • 48.9k
  • 10
  • 136
  • 183

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

Fiddler for doioig

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

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - 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"

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

Fiddler for doioig

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

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - there's a discussion going on about this right now.

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

Fiddler for doioig

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

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - 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"

added 2 characters in body
Source Link
Geoff Dalgas
  • 48.9k
  • 10
  • 136
  • 183

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

Fiddler for doioig

Notice the meta refresh pointing at http://stackoverflow.com - it seems that a developer copycopied and pasted the answer from here without changing the example URL:

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - there's a discussion going on about this right now.

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

Fiddler for doioig

Notice the meta refresh pointing at http://stackoverflow.com - it seems that a developer copy and pasted the answer from here without changing the example URL:

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - there's a discussion going on about this right now.

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

Fiddler for doioig

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

http://stackoverflow.com/revisions/5411601/3

Apparently doioig.gov 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 http://news.ycombinator.com/item?id=5311151 - there's a discussion going on about this right now.

edited body
Source Link
Geoff Dalgas
  • 48.9k
  • 10
  • 136
  • 183
Loading
added 112 characters in body
Source Link
Geoff Dalgas
  • 48.9k
  • 10
  • 136
  • 183
Loading
Source Link
Geoff Dalgas
  • 48.9k
  • 10
  • 136
  • 183
Loading