Native redirect tool vs bulk CSV vs apps, wildcard patterns, chains and loops to avoid, and the 8-point post-launch verification check. Preserves rankings; ships in an afternoon.
Shopify ships a native URL Redirects tool that handles up to 100,000 redirects per store with bulk CSV import. For migrations under 1,000 URLs the CSV approach is fastest. Above 1,000 or whenever you need wildcard patterns, a redirect app (Redirect Toolkit, SEO King) saves hours. The three recurring failure modes are chains (A→B→C→D, dilutes link equity), loops (A→B→A, breaks crawlability), and irrelevant-destination redirects (old product to homepage, which Google treats as soft 404). Verify with curl -I, Screaming Frog in list mode, and Google Search Console's coverage report for 14 days post-launch.
Shopify Admin → Online Store → Navigation → URL Redirects → Add redirect. Enter old path (/collections/old-name) and new path (/collections/new-name). Saves as a 301. Useful for one-offs when a marketing team renames a collection or a product handle changes. Not practical for 500+ migrations; manual entry gets error-prone past 20 or 30.
Same admin screen; Import button top right. Upload a two-column CSV (redirect_from, redirect_to). Shopify validates and ingests in under a minute for a few thousand rows. Right approach for migrations of 100 to 1,000 URLs. Gotcha: paths are relative (/collections/old), not absolute URLs. Include trailing slashes if your theme uses them consistently; inconsistency here is a frequent cause of silent 404s.
Apps add wildcard pattern support (e.g., /blog/old-cat/* → /blog/new-cat/*) and bulk-edit tooling that Shopify's native tool lacks. Critical for migrations with pattern-based URL structure changes; one wildcard rule can replace 500 individual redirects. Enterprise stores sometimes skip apps and use Cloudflare Workers at the edge for fully programmatic redirect logic. On Shopify Plus, the Oxygen layer also supports custom redirect logic.
Four classes of redirect failure account for roughly 80 percent of post-migration SEO incidents we see. Each one is preventable with a pre-launch audit.
Chains. URL A redirects to B, B to C, C to D. Google follows chains up to about 5 hops but discounts link equity at each stop. Keep redirects to a single hop; if a page has already moved once, update the old redirect to point directly to the current destination rather than stacking.
Loops. A redirects to B, B redirects back to A. Both URLs become un-crawlable and Google drops them. Usually caused by appending trailing slashes inconsistently or by conflicting redirect rules. Every bulk CSV should be scanned for circular patterns before upload.
Irrelevant destinations. Redirecting every removed product URL to the homepage. Google treats this as a "soft 404" because the destination has no topical relevance to the source. The ranking dissolves. Redirect to the closest live equivalent (parent collection, category page, or similar product) instead.
Handle drift. Shopify product and collection URLs use auto-generated handles based on the title. Editing a product title can regenerate the handle and silently break backlinks and internal links. Lock handles during migration; make title edits after adding the redirect rule.
Three methods. First, the built-in URL Redirects tool in Shopify Admin under Online Store then Navigation. This works for one-at-a-time redirects and has a 100,000 redirect ceiling per store. Second, bulk import via CSV (Online Store, Navigation, URL Redirects, Import) which accepts a two-column sheet of from-URL to to-URL. Third, redirect apps like Redirect Toolkit or SEO King that add pattern matching, wildcards, and monitoring on top of the native engine. For migrations under 1,000 URLs the bulk CSV is the right tool. Above that, an app with wildcard support saves hours.
A 301 is a permanent redirect that tells search engines the URL has moved forever; link equity and ranking signals transfer to the destination. A 302 is a temporary redirect that tells search engines the original URL will return; link equity stays with the original. For migrations, URL restructures, and most SEO work, you want 301s exclusively. Shopify's built-in URL Redirects issue 301s by default. Only use 302s for genuinely temporary situations like an A/B test destination or a maintenance page.
The native URL Redirects tool does not support wildcards; every redirect is one specific from-URL to one specific to-URL. For wildcard patterns like /blog/old-category/anything to /blog/new-category/anything you need a redirect app (Redirect Toolkit, SEO King, Redirectly) or an edge function via Cloudflare Workers in front of the store. Enterprise Plus stores sometimes solve this with Oxygen custom logic. Wildcard rules are cleaner and easier to maintain than thousands of explicit pairs; above 500 changed URLs the wildcard approach is usually worth the app subscription.
Four recurring issues. One, redirect chains where URL A redirects to B which redirects to C which redirects to D; Google follows chains but discounts link equity at each hop. Two, redirect loops where A redirects to B and B redirects back to A, which makes both URLs un-crawlable. Three, redirecting to irrelevant pages (old product to homepage) which Google treats as soft 404 and the ranking evaporates. Four, forgetting that Shopify's product URLs use handles; changing a product title that auto-regenerates the handle silently breaks every backlink and internal link without a redirect.
Eight-point verification. One, curl -I on each redirect and confirm 301 response and correct Location header. Two, Screaming Frog or similar crawler in list mode fed a CSV of old URLs; confirm all resolve to the expected destination. Three, Google Search Console coverage report watching for spike in Not Found. Four, fetch-and-render in GSC for a few sample destinations. Five, spot-check in a fresh browser (not cached). Six, verify XML sitemap only includes live URLs (not redirecting URLs). Seven, check redirect chain depth; never more than 1 hop. Eight, 14-day watch of 404 logs for URLs that missed the map.