Based on 301, 302, 307, 308: Which redirect is the chosen one? by Google Search Central. Published November 6, 2026.
Redirect choice isn't a disaster
The video says that whichever redirect you pick, one version of the page stays in the search index. A less-than-ideal choice mainly affects which URL appears in search results. That's the video's claim, so treat it as reassurance rather than a reason to skip the details.
Use a 301 for permanent moves
The video says a 301 tells the search engine a page has moved for good, so the old page's ranking signals pass to the new URL and the new one is picked as the main (canonical) page. If you've renamed a product page or collection for good, a 301 is what the video suggests, and it advises against leaving a permanent move on a temporary redirect.
Keep 302 for temporary moves
According to the video, a 302 signals a temporary move, so the search engine keeps showing the old URL and largely ignores the new one, expecting you to come back. Both 301 and 302 help group duplicate pages, but only a 301 helps the new URL become the main one. A 302 fits something like a short-term swap, not a permanent change.
307 and 308 matter when form data must survive
The video describes 308 as the modern version of a 301 and 307 as the modern version of a 302. The difference is that they keep submitted form data intact through the redirect. Its example is a checkout form sent to a backup payment server during overload, where a 302 would drop the data and a 307 would pass it along. For search, the video says they're treated the same as the older types.
Prefer server-side redirects
The video's view, which it presents as opinion, is that server-side HTTP redirects are better than JavaScript redirects or meta refresh. The latter make the browser load and process the page before sending the visitor on, which can be slow, can hurt the experience, and may be missed by search engines.
Client-side redirects are a last resort
If a server-side redirect truly isn't possible, the video says a client-side redirect might work, but you shouldn't count on it always working. For a small merchant, that means checking what your platform allows before settling for this option.
A checklist for this week
- List any pages you've moved or renamed, and note whether each move is permanent or temporary.
- Check that permanent moves use a 301 (or a 308) rather than a temporary redirect.
- Reserve 302 or 307 redirects for changes you really do plan to undo.
- Look for any JavaScript or meta refresh redirects and note where a server-side redirect could replace them.
- If you run a custom checkout, ask your developer whether any redirects could drop submitted form data.
- Search for an old page's URL after a move and see which URL shows up in results.
What the video doesn't cover
The video gives no steps for setting up redirects on Shopify or any other platform or server. It doesn't cover redirect chains, bulk redirects during a site migration, or how long ranking signals take to transfer. The checkout example mostly applies to custom setups, since merchants on hosted checkouts usually don't control payment redirects. There's no data or measured results behind it, only statements from search company staff, and a brief mention of a CDN causing server problems comes without advice.
When to get help
If you're moving a lot of pages, changing your site structure, or running a custom checkout, it may be worth having a developer or agency set up and check the redirects. For a handful of renamed pages, you can often handle it yourself.
See how we help with Websites, or tell us what you're working on.
About this article
This summary was drafted with AI from the video above, checked by an automated reviewer against our notes on the video, and published by Parkdale Digital. It describes what the video recommends; it isn't affiliated with or endorsed by the video's creator. More articles.