Amazon Web Services: Clouded by Duplicate Content

Re:Amazon Web Services: Clouded by Duplicate Content by rlpb on Monday June 28, 2010 @11:13AM (#1468171)

If accessing your web server via .amazonaws.com does not make sense for you, why not just block (whether 403 or 404) all HTTP requests with a Host: *.amazonaws.com header, rather than messing around with rewrites and robots.txt?

[ Parent | on HN ]

Re:Amazon Web Services: Clouded by Duplicate Content by ddemchuk on Monday June 28, 2010 @11:15AM (#1468180)

Because once that content is indexed, you can receive a negative effect from Google by mass 403-ing a huge amount of content

[ Parent | on HN ]

Re:Amazon Web Services: Clouded by Duplicate Content by rlpb on Monday June 28, 2010 @11:51AM (#1468314)

301 then it if this applies to you. It's still the same solution.

[ Parent | on HN ]

Re:Amazon Web Services: Clouded by Duplicate Content by ddemchuk on Monday June 28, 2010 @06:59PM (#1469740)

No its not. Google has said that in situations like this, use a 301 redirect to properly tell them where the actual content is located. Using a 403 is an error page that will tell the spiders that that page doesn't exist anymore, and that can have a negative impact on your rankings

[ Parent | on HN ]