Definition
A 301 redirect is an HTTP response that tells browsers and search engines a page has moved permanently to a new URL, and sends visitors there automatically. Google treats a 301 as a signal that the new URL should be canonical and shows it in search results, which is why 301s are used for changed URLs and site migrations.
How a 301 redirect works
When a browser or crawler requests an old URL, the server does not return the page. It returns the status code 301 and a Location header with the new address, and the browser follows it. The HTTP standard defines 301 (Moved Permanently) as meaning the resource has a new permanent URI and that future references ought to use it[1]. The visitor barely notices: they type or click the old link and land on the new page.
Search engines read the same signal. For Google, a permanent redirect (301 or 308) is a signal that the redirect target should be the canonical URL, and Google shows the new target in search results. For a temporary redirect it keeps showing the source page[2]. That is why the 301 is the redirect for anything that has moved for good: a changed product handle, a deleted category, a whole store moved to a new platform. Google recommends a permanent server-side redirect whenever possible[2].
A 301 is sticky. The standard makes it cacheable by default[1], and Shopify warns that 301 redirects are cached by browsers and search engines, so a redirect you delete may keep working in visitors' browsers[3]. Use one only when you are sure the move will not be reverted.
Types of redirects: 301, 302, 307, 308
| Code | Meaning | Request method | How Google treats it |
|---|---|---|---|
| 301 Moved Permanently | Moved for good | Clients may change POST to GET, for historical reasons | Permanent: target becomes canonical |
| 308 Permanent Redirect | Moved for good | Method must not change | Permanent: target becomes canonical |
| 302 Found | Temporarily elsewhere | Clients may change POST to GET | Temporary: source stays in results |
| 307 Temporary Redirect | Temporarily elsewhere | Method must not change | Temporary: source stays in results |
The method rules come from the HTTP standard, which also notes that 308 is much younger, from June 2014, and might not be recognised everywhere[1]. The Google column is from Google's redirect documentation[2]. For a store, the difference between 301 and 308 rarely matters, because pages are opened with GET. The choice that does matter is permanent versus temporary.
Two client-side options exist. Google reads an instant meta refresh as permanent and a delayed one as temporary, and says to use JavaScript redirects only if you cannot do server-side or meta refresh redirects, because rendering can fail[2].
301 redirects on Shopify
You manage redirects in the Shopify admin under Content > Menus > URL redirects, one at a time or by importing a CSV file, and you can export them the same way[3]. When you change the URL handle of a page, Shopify pre-selects an option to create a redirect from the old address[4], and collections offer the same choice[5]. The rules worth knowing[3]:
- Limits: up to 100,000 URL redirects, or 20,000,000 on Shopify Plus.
- Only broken URLs redirect. If the old URL still loads a valid page, the redirect does not work. Delete or hide the old product first.
- Blocked paths: URLs that start with
/apps,/application,/cart,/carts,/orders,/servicesor/shop, and the fixed paths/products,/collectionsand/collections/all, cannot be redirected. - Query strings in the old URL might not work as expected.
- External targets are allowed with a full URL.
Example: redirect map for a migration to Shopify
Take a hypothetical WooCommerce store moving to Shopify with 1,200 products, 60 categories, 300 blog posts and 40 information pages. The URL patterns change on every type:
| Content | Old URL | New Shopify URL | Redirects |
|---|---|---|---|
| Products | /product/linen-shirt/ | /products/linen-shirt | 1,200 |
| Categories | /product-category/shirts/ | /collections/shirts | 60 |
| Blog posts | /2024/05/care-guide/ | /blogs/news/care-guide | 300 |
| Pages | /about-us/ | /pages/about-us | 40 |
| Total | 1,600 | ||
1,600 redirects is 1.6% of the 100,000 limit on a standard plan[3], so the limit is not the problem. The mapping is. Google calls mapping old URLs to new ones important in a site move[6], and the work is in the details: every old URL goes to its closest new equivalent, the CSV is imported before DNS switches, and a crawl of the old URL list confirms each one returns a single 301 to a live page. Googlebot follows up to 10 hops in a chain, but Google advises redirecting to the final destination directly, or keeping chains to 3 or fewer[6]. Keep the redirects for as long as possible, generally at least a year, and expect rankings to move for a few weeks or more while Google catches up[6].
Redirect maps are part of every Shopify migration we run, and we test them in a sandbox store before launch, as described in our guide to testing a Shopify Plus migration in a sandbox.
301 redirect vs canonical tag
| 301 redirect | Canonical tag | |
|---|---|---|
| Visitor can still open the old URL | No, they are sent to the new one | Yes |
| What it tells Google | This page has moved permanently | Prefer this other URL for the same content |
| Use it for | Changed handles, deleted pages, migrations, domain changes | Duplicates that must stay reachable, such as variants and filters |
| On Shopify | URL redirects in the admin | Output by the theme automatically |
FAQ
How long should I keep a 301 redirect?
As long as possible. Google's site move guide says to keep redirects generally at least one year[6]. On Shopify there is little reason ever to delete them, since even a large store stays well below the redirect limit.
Should I use a 301 or a 302 redirect?
Use a 301 when the move is permanent, so Google shows the new URL and treats it as canonical. Use a 302 only when the old URL will come back, because Google keeps showing the source page in results[2].
How many redirects can a Shopify store have?
Up to 100,000 URL redirects, or up to 20,000,000 on the Plus plan[3]. You can add them one by one or import them from a CSV file under Content > Menus > URL redirects.
Why is my Shopify redirect not working?
Usually because the old URL still loads a page. Shopify redirects only broken URLs, and cannot redirect paths that start with /apps, /cart or similar reserved prefixes[3]. Browser caching of an earlier 301 can also mislead your test, so check in a private window.
Should I redirect deleted products to the homepage?
No. Google may treat many old URLs redirected to one unrelated page, such as the homepage, as soft 404s[6]. Redirect to the closest collection or replacement product instead.
The bottom line
A 301 redirect is the server's way of saying a page has moved for good, and Google answers by showing the new URL instead of the old one. On Shopify you manage redirects in the admin, with generous limits and a few rules: only broken URLs redirect, and some paths are reserved. The real work is the mapping, especially in a migration: each old URL to its closest new page, in one hop, kept for at least a year.
Article sources
We use primary sources only: official documentation, product pages and laws. Each link was checked on the date shown.
- IETF / RFC Editor. RFC 9110: HTTP Semantics, section 15.4 (Redirection 3xx). Accessed 17th Nov 2026.
- Google Search Central. Redirects and Google Search. Accessed 17th Nov 2026.
- Shopify Help Center. URL redirects. Accessed 17th Nov 2026.
- Shopify Help Center. Creating and editing pages. Accessed 17th Nov 2026.
- Shopify Help Center. Collection settings. Accessed 17th Nov 2026.
- Google Search Central. Site moves and migrations. Accessed 17th Nov 2026.
Need this on your store?
See the serviceThe checklist we run before touching a client's code
Get it by email, plus a few short notes over the next two weeks: what we see most often on Shopify stores and what actually fixes it.