301 redirects: a dangerous one way street (2012)
The problem with 301 without cache headers is that some browsers cache this forever due to some interpretation what 'permanent' means.<p>You often can't use 302 because all your external links no longer work SEO magic for you with a 302. Google only transfers link juice with 301 [1].<p>If you make a mistake and misconfigure your server, you're toast.<p>If a disgruntled employee 301 redirects your domain, you're toast.<p>If a service provider misconfigures your domain, you're toast.<p>If a hacker (from a competitor) 301 redirects your domain, you're toast.<p>If you buy a domain that had a 301 on it, it's worthless.<p>If you buy a domain that had 301s on it that point to phishing sites, you're in trouble.<p>I always add cache headers to 301 redirects I use to at least prevent me from shooting myself with an arrow in my knee.<p>UPDATE:
[1] Google seems to have changed this recently. It also no longer considers http/https different pages as it did in the past with the same content <a href="https://www.searchenginejournal.com/google-confirms-no-loss-in-link-authority-on-https-implementation/147933/" rel="nofollow">https://www.searchenginejournal.com/google-confirms-no-loss-...</a>