3 ms·
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.
by rlpb 16y ago
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?
- ddemchuk 16y agoBecause once that content is indexed, you can receive a negative effect from Google by mass 403-ing a huge amount of content
- rlpb 16y ago301 then it if this applies to you. It's still the same solution.
- ddemchuk 16y agoNo 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