About 301 Redirects
Some websites claim that a 301 redirect is a permanent redirect which passes between 90-99% of link juice. Well, since you found this website you can see now that this is not the true.
Other websites even claim that 301 redirects ensure search engines and browsers of all kinds give "full credit" and once again you can see that traffic to your website is dramatically missing.
While many claim that it is common practice to redirect one URL to another think for a moment... what if 2, 10, or 1,000 pages were created and all of them became a 301 to a single page. Then how much "link juice" would be passed? Are you understanding now why 301s can't work?
Think to yourself... search engine algorithms give a lot of weight to incoming links and the new page has no incoming links. This is why the new page drops in the search rankings.
So, can you see now why 301 redirects cannot work?
If a client has link-editing capabilities, it should update all references to the Request URL. The response is cacheable unless indicated otherwise. Unless the request method was HEAD, the entity should contain a small hypertext note with a hyperlink to the new URL(s). If the 301 status code is received in response to a request of any type other than GET or HEAD, the client must ask the user before redirecting.
The HTTP response status code 301 Moved Permanently is used for permanent URL redirection, meaning current links or records using the URL that the response is received for should be updated. The new URL should be provided in the Location field included with the response. The 301 redirect is considered a best practice for upgrading users from HTTP to HTTPS.