# Wrong status code on amp-\>non-amp redirect

**URL:** <https://community.hubspot.com/t/wrong-status-code-on-amp-non-amp-redirect/116160>\
**Category:** Content Strategy & SEO\
**Tags:** content-seo\
**Created:** [September 11, 2024, 12:41pm UTC](https://community.hubspot.com/t/wrong-status-code-on-amp-non-amp-redirect/116160 "2024-09-11T12:41:24Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![kennedyp](https://avatars.discourse-cdn.com/v4/letter/k/49beb7/32.png) [@kennedyp](https://community.hubspot.com/u/kennedyp)\
**Post date:** [October 1, 2024, 9:58pm UTC](https://community.hubspot.com/t/wrong-status-code-on-amp-non-amp-redirect/116160/6 "2024-10-01T21:58:03Z")

</div>

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](https://developers.google.com/search/docs/crawling-indexing/large-site-managing-crawl-budget) 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

---

_[View the full topic](https://community.hubspot.com/t/wrong-status-code-on-amp-non-amp-redirect/116160)._