302 redirects in Magento, trying to fix

[LASClients]

Hi all, I'm assigned a site in Magento. After the first craw, we found almost 15k 302 redirects.

A sample URL ends with this /stores/store/switch/?SID=qdq9mf1u6afgodo1vtvk0ucdpb&___from_store=default&___store=german&uenc=aHR0cHM6Ly9qdWljeWZsdXRlcy5jb20vP19fX3N0b3JlPWdlcm1hbg%2C%2C

And they are currently 302 redirecting to the homepage as well as other main pages and also product pages it seems.

Some of these point to account pages where customers log in. Probably best for me to de-index those so no issues there.

But I'm worried about the 302 redirects to public pages.

The extension we have installed is SEO Suite Ultimate by MageWorx.

Does anyone here have experience here specifically and how did you fix it?

Thanks,

JC

[LASClients]

It turned out to be a language extension. We took it out and fixed everything except for a couple of links. I'm opening a new question for those. Thanks for all your help!

[terryseos]

Look at the template, as this is the likely culprit making links to these 302 redirects. If they are not required, simply remove any references to the link on your template?

If they are necessary links as you say, customer login etc - add a nofollow tag and de-index the page.

Ensure you have self-referencing canonical tags on the pages with lots of parameters.

You could also remove the a tag to something less SEO friendly to reduce your potential crawl budget ensuring that your non-vital (product/category) pages exhume more importance.

If you have so many links/pages, they will get lost within all the nonsense.

[tir17]

@lasclients Hello, you should debug the redirections in this case. Here's what you can do in Magento 2:

If you face an unexpected 301 or 302 redirect in Magento 2 and you don't know why it happens or what code causes it, you can easily find this out by temporarily editing the following files:

/vendor/magento/framework/HTTP/PhpEnvironment/Response.php
/var/www/html/m2_35ee/vendor/magento/framework/Controller/Result/Redirect.php

Open Response.php and add the following line to the beginning of the setRedirect function:

var_dump($url); \Magento\Framework\Debug::backtrace(false, true, false); exit();

Example:

public function setRedirect($url, $code = 302)
{
    var_dump($url); \Magento\Framework\Debug::backtrace(false, true, false); exit();
    $this->setHeader('Location', $url, true)
        ->setHttpResponseCode($code);

    return $this;
}

Now you open the second Redirect.php file and add this:

var_dump($this->url); \Magento\Framework\Debug::backtrace(false, true, false); exit();

After each line containing:

$this->url =

Example:

public function setRefererUrl()
{
     $this->url = $this->redirect->getRefererUrl();
     var_dump($this->url); \Magento\Framework\Debug::backtrace(false, true, false); exit(); 
     return $this;
}

public function setRefererOrBaseUrl()
{
     $this->url = $this->redirect->getRedirectUrl();
     var_dump($this->url); \Magento\Framework\Debug::backtrace(false, true, false); exit(); 
     return $this;
}

public function setUrl($url)
{
     $this->url = $url;
     var_dump($this->url); \Magento\Framework\Debug::backtrace(false, true, false); exit(); 
     return $this;
}

public function setPath($path, array $params = [])
{
     $this->url = $this->urlBuilder->getUrl($path, $this->redirect->updatePathParams($params));
     var_dump($this->url); \Magento\Framework\Debug::backtrace(false, true, false); exit(); 
     return $this;
}

Save the corresponding changes and open a page that causes an unexpected redirect. You should see a debug backtrace with the information about the code line causing the redirect.

If you don't see it, it means that the redirect is not caused by Magento code, but the webserver settings, or the third-party module code that uses not-recommended Magento programming practices.

Hope this helps!