{"id":53492,"date":"2020-05-08T10:56:21","date_gmt":"2020-05-08T08:56:21","guid":{"rendered":"https:\/\/www.humanlevel.com\/diccionario-marketing-digital\/redireccion-302"},"modified":"2020-09-16T13:53:00","modified_gmt":"2020-09-16T11:53:00","slug":"302-redirection","status":"publish","type":"dicmarketing","link":"https:\/\/www.humanlevel.com\/en\/digital-marketing-dictionary\/302-redirection","title":{"rendered":"302 redirection"},"content":{"rendered":"

What is a 302 redirection?<\/h2>\n

A 302 redirection indicates that the content of a page has been temporarily moved to another URL and redirects requests from the original URL to the redirect destination<\/strong>.<\/p>\n

In SEO, the 302 temporary redirection is used in very specific scenarios, in which it is necessary to redirect access from one content to another only temporarily, without involving a complete migration. This temporality is the main difference between a 302 redirection and a 301 redirection<\/a>, recommended for definitive migrations.<\/p>\n

\"How
How a 302 redirection works from the perspective of users and a search engine.<\/figcaption><\/figure>\n

As we can see in the graph, for users there is no difference between a permanent 301 redirection and a temporary 302 redirection. In both cases they perceive that the initially requested URL (abc) “jumps” to another one (xyz) where they finally access the content.<\/p>\n

Search engine robots are also redirected from the original URL (abc) to the redirect target URL (xyz). However, the 302 temporality code will tell them that the URL under which they should index that content is the source (i.e., abc), not the destination (xyz). This is the main difference between a 301 and a 302 redirection. In the case of a 301 redirection, search engines will interpret that the content has migrated permanently to the destination address and will use this URL for indexing (in this case, xyz).<\/p>\n

For practical purposes, a user does not notice the difference between a 302 and a 301 redirection<\/strong>. A search engine, on the other hand, interprets a 302 redirection literally<\/strong>: the transfer is temporary, and therefore, it is understood that the original URL is the one that must be kept indexed and positioned, because in the short or medium term it will be used again, and any authority and link juice<\/em> it has previously achieved is not transferred to the URL receiving the redirect.<\/strong>The original URL is expected to be reestablished in the near future.<\/p>\n

The current controversy with the use of 302 redirections is that they are often not used correctly, which ends up confusing search engines<\/a>. We have known many cases in which the correct redirect would be 301, since the content has been moved to another route for good. And yet a 302 response code has been used instead, thus preventing the proper transmission of popularity and relevance to the new page, and the old URL from being successfully replaced by the new one in the search results.<\/p>\n

Attention<\/strong>: we must be very careful with 302 redirections because only one URL can point to another with this type of redirect. If we redirect from multiple URLs with 302 redirections to another URL, we would be telling Google to index the content of the redirect destination URL with the multiple source URLs<\/strong> which would ultimately lead to a duplicate content situation.<\/p>\n

When does it make sense to use a 302 redirection?<\/h2>\n

Using 302 redirections is recommended only in very specific cases, because a temporary transfer of content is not very common. Normally the redirection is made effective in a definitive way with its corresponding content migration, since it supposes a considerable alteration for the page, and it is something that you want to mitigate as much as possible, so as not to dizzy neither the users nor the search engines, with the consequent impact on the visibility and popularity.<\/p>\n

We can think of the following possible<\/strong> scenarios:<\/p>\n