302 turn and URL hijacking

Another more common status code is a 404 error (404 error), a 404 error or a 404 status code refers to a web page that does not exist.

Another related to the 302 status code is the 301 redirect, which refers to the permanent transfer of the web page to another location. The difference between 301 and 302 is that 301 is a permanent redirect and 302 is a temporary redirect.

What is the relationship between 302 redirects and URL hijacking? This starts with how the search engine handles 302. By definition, when making a 302 redirect from URL A to URL B, the implicit meaning of the host server is that URL A may change its mind at any time, redisplay its content or go to other places. Most of the search engines in most cases, when receiving a 302 redirect, generally only need to crawl the destination URL, that is, the URL B.

In fact, if the search engine crawls the destination URL B 100% when it encounters the steering, there is no need to worry about the URL hijacking.

The problem is that sometimes search engines, especially Google, don’t always crawl the destination URL. why? For example, sometimes the A URL is short, but it does a 302 redirect to the B URL, and the B URL is a long messy URL, and may even contain parameters such as question marks. Naturally, the A website is more user-friendly, and the B website is both ugly and user-friendly. At this time, Google is likely to still display URL A.

Since the search engine ranking algorithm is just a program rather than a person, when encountering a 302 redirect, it is not as accurate as a person to determine which URL is more appropriate, which creates the possibility of URL hijacking. In other words, an unethical person makes a 302 redirect to your URL B on his own URL A. For some reason, Google search results still show URL A, but the content of the page used is The content on your URL B, this is called URL hijacking. The content you wrote so hard has been stolen by others.

The URL hijacking caused by the 302 redirect has been around for a while. But so far, there seems to be no better solution. In the ongoing Big Dad data centre transformation, the 302 redirect problem is also one of the goals to be solved. From some search results, the phenomenon of URL hijacking has improved, but it has not been completely resolved.

If you encounter your own website URL being hijacked, there is nothing you can do on your own, you can only report to Google.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button