Wrong status code on amp->non-amp redirect

[EOrlov]

After disabling AMP on CMS level old amp-ed URLs are redirected to standard URLs with 302, instead 301.

Desperately need a fix - this is a hugh SEO issue, rankings go lost.

[kennedyp]

Hey @EOrlov! Thanks for your post. 

I understand your web pages are now using a temporary redirect after disabling accelerated mobile pages. When was AMP disabled? Also, can you share an example of the current redirect and what you'd expect instead? I am happy to verify why we are seeing this behavior. 

Best, 
Kennedy

[EOrlov]

link

[kennedyp]

Thanks, @EOrlov! After disabling AMP, a 302 temporary redirect to the canonical non-AMP page is expected. Check out this Google documentation for more context. 😊

[EOrlov]

After disabling of AMP , we set up manual 301 redirects. But neverthenless they don't work properly and send 302.

Why manual redirects don't work? Does HS has a solution? This is an obvious bug.

In the cited Google documentation is stated both 301 and 302 are possible. But as it is known, 302 produces remaining the previous url in index, which is absolutely counterproductive in terms of SEO.

[kennedyp]

Thanks for that additional context @EOrlov. From what I understand, a 302 is expected from HubSpot when disabling AMP since the 301 or 302 are acceptable. Can you provide more details or documentation about why you specifically want a 301 instead of a 302? From my understanding, 301 vs 302 shouldn't affect your SEO rankings or crawling budget. The only crawling budget concern I see mentioned by Google is long redirect chains. Any additional context you have as to how that affects your SEO will help us out! 

To our experts @danmoyle & @Sam62 do either of you have insight here? Thanks!!

Best, 
Kennedy

[EOrlov]

There isn't a question, what status code is right or wrong. The issue is, that for amp pages manually defined redirects with certain status code dont work.