Shopify 301 Redirects for Large Catalogs: How to Build the Map

Most merchants treat redirect mapping as the last item on the migration checklist. It gets drafted hastily during the final week, handed off to a developer who's already juggling cutover tasks, and validated with a handful of spot-checks on launch day. Then traffic drops. Rankings slip. The post-mortem reveals that hundreds of URLs were either missed, miscategorized, or pointing at each other in loops. At that point you're in recovery mode, not growth mode.

For stores migrating with 500 or more URLs, redirects are not a technical formality. They are a crawl budget and SEO equity problem. Getting them wrong means Googlebot spends its limited crawl allocation following dead ends and chains instead of indexing your new catalog. The rankings you built over years can erode in weeks. The good news is that the problem is entirely solvable if you treat the redirect map as a first-class deliverable rather than an afterthought.

This is the playbook we use on every catalog migration, and it sits alongside the broader migration framework we walk merchants through before any cutover work begins.

---

Start with a Clean Crawl Before You Touch Anything Else

The foundation of any redirect project is a complete, pre-migration URL inventory. You need to know exactly what exists before you can map where it should go.

Screaming Frog SEO Spider is the standard tool for this work. Run a full crawl of the origin store and export from the Internal tab. You will get every indexable URL the crawler discovered, along with status codes, titles, and canonical tags. For stores on platforms with parameter-heavy URLs, you will want to configure Screaming Frog's URL rewriting settings to strip query strings that represent sort order, pagination parameters, or tracking tokens, since those do not need individual redirects and will pollute your list if you leave them in.

Once the export is clean, filter it down to the URLs that actually matter. Product pages, collection pages, blog posts, and key landing pages. Faceted filter URLs like /collections/boots?color=black are a category Shopify explicitly cannot redirect, since the platform treats those paths as valid even when no products match. You document them, note the limitation, and move on rather than building false coverage into your map.

The output at this stage is a spreadsheet with one canonical source URL per row, its current status code, its page type, and a column left blank for the destination. This same crawl pass surfaces the indexation and canonical issues we cover in the Shopify technical SEO playbook, so it pays to fix the obvious ones before cutover instead of after.

We run pre-migration crawls and URL inventories as part of every migration audit. Talk to our SEO team before you start mapping.

---

Building the Redirect CSV for Shopify's Bulk Import

Shopify's native URL redirect import accepts a two-column CSV: Redirect from and Redirect to. The Redirect from column takes relative paths only, no domain. The Redirect to column accepts relative paths for internal destinations and full URLs for external ones. That is the entire format.

You access the import interface via Online Store > Navigation > View URL Redirects > Import in your Shopify admin. Shopify processes the file and confirms the count before creating anything, so you can review before committing.

One hard constraint worth knowing: Shopify will not allow you to create a redirect for a URL that currently loads a valid page with a 200 response. The source URL must be returning a 404 or another error status. This matters for staging workflows. If you are mapping redirects while the origin store is still live, the old URLs return 200s and Shopify will reject those rows at import time. The common workaround is to build and stage the CSV before cutover, then import it immediately after DNS switches and the origin store goes dark.

For stores with more than a few thousand redirects, the standard redirect limit on most Shopify plans is 100,000, which is sufficient for the vast majority of catalog migrations. Shopify Plus stores can handle up to 20,000,000.

---

The URL Patterns That Break Every Time

There are four URL pattern categories that create problems on almost every migration we handle. Knowing them in advance prevents the bulk of post-launch firefighting.

Pagination URLs. Paths like /collections/jackets?page=2 are soft targets. Googlebot may have crawled and indexed some of them. They do not map cleanly to single destination pages. The right approach is to redirect all paginated collection URLs to the root collection, accepting that a small amount of indexed equity will dissipate.

Filter and faceted URLs. As noted above, Shopify cannot redirect URLs that use collection tag filtering. A URL like /collections/shoes/running is considered valid by Shopify even with an empty result set. Document these as non-redirectable and update your XML sitemap accordingly.

Variant URLs. On many platforms, product variants generate their own URL with query parameters: /products/sneaker?variant=12345. Shopify handles variants differently, hanging them off the parent product URL via query parameter. The parent product URL maps to the new Shopify product handle; the variant parameter structure changes. Your redirect map needs to point the old product base URL to the new product handle and accept that variant-specific parameters will not carry over cleanly.

/collections/ vs. /products/ confusion. The migration from WooCommerce, Magento, or custom platforms often involves category URLs that were structured differently. A path like /category/mens/shoes needs to map explicitly to /collections/mens-shoes on Shopify, not to /products/ or to the homepage. Every category-to-collection mapping needs to be reviewed manually. Automating this with pattern matching alone introduces mistakes at scale.

Need engineering hands on a complex catalog migration? See our Shopify development services.

---

Redirect Chains: The Silent Crawl Budget Tax

Redirect chains form when a new redirect points to a URL that is itself a redirect. It happens naturally over time, especially when a migration is layered on top of an existing redirect set, or when post-launch content restructuring adds new redirects without auditing the existing ones.

Google's own crawl budget documentation explicitly warns against this: long redirect chains have a negative effect on crawling. Each hop in a chain consumes a separate crawl request. A chain of three redirects costs Googlebot three requests to reach one final URL. Across thousands of URLs, that waste compounds quickly and pushes high-priority pages to the back of the crawl queue.

The practical ceiling most SEO practitioners work with is two hops maximum, with one being the clear target. When a chain of three or more develops, Google may abandon the chain before reaching the final destination, which means the page neither gets crawled nor indexed.

To detect chains post-launch, run Screaming Frog in List Mode against your old URL set with Always Follow Redirects enabled under Config > Spider > Advanced. The All Redirects report will surface every chain in a single export. For each chain identified, update the original source URL's redirect to point directly at the final destination, removing the intermediate hops.

Internally, update all links in your theme, navigation, and sitemap to point to final URLs. Every internal link that points to a redirect rather than the destination burns a crawl request unnecessarily. We see the same pattern surface in post-launch audits — it's one of the recurring items in the issues we find on established Shopify stores.

---

Validating Coverage in Google Search Console After Launch

The redirect map is built and imported. The store is live. Now you need to verify that the coverage is actually working, and that Google is processing the changes correctly.

The first check is mechanical: use Screaming Frog in List Mode, upload your original URL list, and confirm every row returns a 301 with the correct destination. Anything returning a 404 is a gap in your map. Anything returning a 302 (temporary redirect) instead of a 301 means equity is not being passed and needs investigation.

In Google Search Console, the Coverage report is your primary post-launch instrument. In the weeks following migration you want to watch three things. First, that the volume of indexed pages on the new domain is rising toward parity with the pre-migration count. Second, that the Crawl Stats report shows Googlebot spending more time on 200-status pages and less on error responses. Third, that the Not found (404) count is not climbing, which would indicate that redirect coverage has gaps.

The URL Inspection tool lets you test individual URLs from the old site to confirm they are being redirected and that the canonical URL Google sees matches your intended destination. For high-traffic pages, this manual check is worth doing one by one in the first week post-launch.

It takes Google several weeks to fully process a large redirect set and update its index. Expect some ranking volatility in the first 30 to 45 days. That is normal. What is not normal is an extended decline across your entire catalog without recovery, which typically indicates either systematic redirect failures or redirect chains that are preventing Google from reaching the new content.

Planning a migration with 500+ URLs? Request a migration audit and we will scope the redirect work alongside the rest of the cutover plan.

---

What This Looks Like in Practice

On a recent migration we handled for a specialty DTC brand with over 1,000 product URLs and multiple nested collection structures, the redirect mapping phase took longer than the theme build. The origin platform had accumulated five years of URL changes, some of which had been redirected manually and some of which were simply abandoned. We crawled the live site, cross-referenced it against Google Search Console's indexed URL list, and built a master map that included not just the canonical product and collection URLs but also legacy paths that were still receiving backlink traffic from external sites.

At launch, we imported 1,847 redirects in a single CSV and validated every row against the live store within the first two hours post-cutover. Organic traffic was within 8 percent of pre-migration baseline within 21 days, which is well inside acceptable range for a migration of that size.

---

The redirect map is not the most glamorous part of a Shopify migration. It rarely makes it into pitch decks. But it is consistently where migrations that look successful on day one quietly fail over the following quarter. At Shugert, we have been executing Shopify migrations for established DTC brands since 2015, and redirect strategy is built into our process from the first discovery call, not added at the end. If you are planning a migration to Shopify — and you are part of the wave of established brands moving to the platform — and your catalog runs into the hundreds of SKUs or more, our Shopify development services are designed specifically for stores where the SEO risk is real and the cost of getting it wrong is measurable.

Related Shugert resources

• Migrating to Shopify in 2026: the complete guide — the broader framework this redirect playbook plugs into.
• The Shopify technical SEO playbook — indexation, canonical, and crawl-budget basics every migration depends on.
• Common Shopify issues we fix on established stores — the post-launch problems redirect chains tend to hide.
• Browse our Shopify development services and past migrations.

When you're ready to scope a 500+ URL migration, request a quote.

---

By Samuel Noriega — Founder & CEO of Shugert, a Shopify Select Partner since 2015. His team has executed 30+ platform migrations since 2016 for DTC brands across the US and Latin America. Connect on LinkedIn: linkedin.com/in/samuelnoriega.