News for hackers. Stuff that matters.
Re:If blacking out your website, return status code 503 to a... by SquareWheel on Monday January 16, 2012 @10:30PM (#3473637)
I see it's already hit the front page, but here is another page of advice directly from a Googler: https://plus.google.com/u/0/115984868678744352358/posts/Gas8...
Re:If blacking out your website, return status code 503 to a... by amirmc on Tuesday January 17, 2012 @03:55AM (#3474258)
The author (pierrefar) also commented in the HN thread of that post about JavaScript suggestions he'd come across.

http://news.ycombinator.com/item?id=3470396

Re:If blacking out your website, return status code 503 to a... by SquareWheel on Tuesday January 17, 2012 @08:24PM (#3477387)
SeoMoz now has a more technical rundown on how to do a 503 status code: http://www.seomoz.org/blog/how-to-handle-downtime-during-sit...
Re:If blacking out your website, return status code 503 to a... by jameslevy on Tuesday January 17, 2012 @01:31AM (#3473998)
If other 50x error codes can result in an SEO, why bother to even use them? is it frowned upon to use 503s where an actual server error response would usually be returned?
Re:If blacking out your website, return status code 503 to a... by jbri on Tuesday January 17, 2012 @01:46AM (#3474030)
I can't see anything in the linked article suggesting that other 50x responses will result in poorer search engine performance - I would expect that any of the transient-fault 50x responses would have the exact same search engine impact. The important part is not returning 200 OK and having googlebot index your blackout page.

It just so happens that 503 is the semantically correct response for this situation, while other 50x responses are not.

Re:If blacking out your website, return status code 503 to a... by rue on Tuesday January 17, 2012 @05:04AM (#3474385)
I'd really rather everyone use the correct status codes (503 indeed being the correct one here) than try figure out what their SEO impact may or may not be. I'm quite sure Google understands HTTP.
Re:If blacking out your website, return status code 503 to a... by suneilp on Tuesday January 17, 2012 @12:35AM (#3473891)
This is good advice.

Even better advice would be to serve different content for regular users. This is easily done through User Agent sniffing. You can do it at the app level or web server such as Apache's Rewrite rules.

Is this cloaking? It might be. However, for only a day, there shouldn't be any harm in it.

Re:If blacking out your website, return status code 503 to a... by SquareWheel on Tuesday January 17, 2012 @02:09AM (#3474081)
I'd be cautious of that method. Google is not a fan of cloaking, and you might wind up with a penalty for much longer than the blackout.
Re:If blacking out your website, return status code 503 to a... by ck2 on Tuesday January 17, 2012 @05:01AM (#3474378)
Or just use a CSS black curtain.
Re:If blacking out your website, return status code 503 to a... by cdent on Tuesday January 17, 2012 @08:01AM (#3474706)
I tweeted this earlier: https://twitter.com/#!/anticdent/status/159221189393383424

'Saying "If blacking out your website, return status code 503 to avoid an SEO hit" == "Bring the caviar when you come to the protest camp"'

If you're not willing to demonstrate damage to your situation in your protest, then it doesn't really count as a protest much, does it?

Re:If blacking out your website, return status code 503 to a... by non123 on Tuesday January 17, 2012 @08:27AM (#3474782)
That's stupid. It's not about taking damage, it's about raising awareness.
Re:If blacking out your website, return status code 503 to a... by cdent on Thursday January 19, 2012 @11:04AM (#3485018)
Re:If blacking out your website, return status code 503 to a... by randallsquared on Tuesday January 17, 2012 @08:12AM (#3474739)
For a startup's site, avoiding a search engine ranking drop is more like "Bring a sleeping bag" than "Bring the caviar", it seems to me.