aftershock2020
Senior Member
- Oct 19, 2007
- 980
- 502
It was designed to be used in the matter of moving a domain content to a new licensed domain and yes, it isn't a true error per say, however, the issue that I see far too many people doing is using it as a gateway port rather than a formatted and proper redirect as you are mentioning in this case. That was my point of reference where there is infact and issue, as you've stated yourself, with the intent of tricking google.
Using it for proper redirect from an old, taken or outdated domain to another new one is nothing new. People tend to abuse the redirect calls and infact do get errors not for the redirect itself but caused by the misuse and misapplication of the redirect, causing loss of the connection to the proper intended landing link. In that being the case, google does by default list those errors if a bot is unable to follow a redirect at any given time.
I'm specifically referring to the errors that they cause more than being an error function itself. Good point to be cleared up, as I don't want to mislead anyone otherwise.
Using it for proper redirect from an old, taken or outdated domain to another new one is nothing new. People tend to abuse the redirect calls and infact do get errors not for the redirect itself but caused by the misuse and misapplication of the redirect, causing loss of the connection to the proper intended landing link. In that being the case, google does by default list those errors if a bot is unable to follow a redirect at any given time.
I'm specifically referring to the errors that they cause more than being an error function itself. Good point to be cleared up, as I don't want to mislead anyone otherwise.
Last edited:
