301 Redirects for Replatforming: Keep Your Rankings
Share
A 301 redirect permanently forwards an old URL to its new address and passes along the ranking signals attached to it — which makes the redirect map the highest-stakes SEO deliverable in any replatforming project. Build it completely and launch it at cutover, and rankings typically settle back within a few weeks. Skip it, and years of link equity point at 404 pages by lunchtime.
Why do 301 redirects decide migration SEO?
Every platform shapes URLs differently, so a migration changes nearly every address on your site — products, categories, blog posts, often all of it. Search engines have equity attached to those old URLs: rankings, backlinks, years of crawl history. A 301 tells Google “this page moved permanently, transfer the signals,” and Google has confirmed that 3xx redirects pass PageRank.
Without that instruction, the old URL returns a 404, the equity has nowhere to go, and your pages start over as strangers. The practical side breaks too: bookmarks, email links, affiliate links, and every ad destination you forgot about, all at once.
The framing we use with clients: redirects are a launch blocker, not a post-launch task. The map ships before DNS does.
How do you build a redirect map?
Six steps, all in one spreadsheet:
- Crawl the live site with Screaming Frog or similar. Capture every indexable URL — products, categories, pages, blog.
- Add Search Console data. Export the performance report for the full 16 months; it catches URLs the crawl missed.
- Add backlink targets. Pull every URL with external links from Ahrefs or Semrush. These rows carry the most equity each.
- Merge, dedupe, and tier. Tier one: anything with revenue, rankings, or backlinks. Tier two: everything else indexable.
- Map one-to-one. Product to product, category to collection, post to post. Send discontinued products to their closest category — never mass-redirect to the homepage, which Google treats as a soft 404.
- Add an owner and a “tested” column. A map nobody verifies is a wish, not a plan.
If you’re mid-migration, this pairs naturally with the catalog spreadsheet from our product data preparation guide — the same export drives both.
What are Shopify’s redirect limitations?
Shopify’s URL Redirects tool is solid but opinionated. Know these constraints before you build:
| Limitation | What it means | Workaround |
|---|---|---|
| Fixed prefixes: /products/, /collections/, /pages/, /blogs/ | Your old URL structure can’t be recreated | Redirect into the new structure; don’t fight it |
| Redirects only fire when the old path 404s | A rule pointing from a URL that still resolves won’t run | Check the map for collisions with live Shopify paths |
| No native wildcard or regex rules | Patterns like /category/* need one entry per URL | Generate rows with spreadsheet formulas; import by CSV |
| Query strings aren’t matched | Old ?p=123-style URLs won’t map by parameter | Redirect the base path; handle rare critical cases in the theme |
None of these are dealbreakers. They just mean the map gets generated up front in a spreadsheet — formulas turning old paths into new ones — rather than written as server rules after the fact.
How do you test redirects at launch?
Import the map before cutover. Entries sit dormant until the domain points at Shopify, because a redirect only fires once the old path stops resolving.
Then, inside the first hour of launch:
- Run the full old-URL list through a crawler in list mode against the live domain.
- Confirm every row returns a 301 — not a 302 — and lands on the correct target in one hop. Chains of two or more redirects waste crawl budget and slow real visitors.
- Manually click your top 100 URLs by traffic and revenue. Crawlers verify status codes; humans notice the wrong destination.
- Test a few old URLs with UTM parameters appended, since your ads and emails carry them.
What should you monitor after launch?
Submit the new sitemap in Search Console on day one, then watch four things:
- The 404 report — daily for two weeks, weekly after. Every legitimate URL that surfaces goes into the map the same day.
- Indexed page count. Old URLs should fall out as new ones come in; the total should hold roughly steady by week six.
- Rank tracking on your top 50 keywords. Movement for two to six weeks is normal. In our experience, complete maps settle at or near prior positions — a slide that keeps going usually means missed redirects, not platform trouble.
- Landing-page revenue in analytics, old paths versus new, week over week.
Keep the redirects live indefinitely; they cost nothing on Shopify and backlinks age slowly. Platform-specific quirks — BigCommerce’s root-level URLs, WooCommerce’s trailing slashes — are covered in our BigCommerce SEO migration guide and WooCommerce checklist.
FAQ
Do 301 redirects lose PageRank? No — Google has confirmed 3xx redirects pass PageRank. The recovery period after a migration comes from recrawling and reindexing, not from a redirect penalty.
How many redirects can Shopify handle? There’s no practical ceiling for a typical store. Large catalogs routinely carry tens of thousands of entries imported by CSV — upload in batches and spot-check each one.
Should old URLs redirect with or without trailing slashes? Map URLs exactly as your crawl found them. If the old platform served both forms, include both rows — two spreadsheet lines now beats a mystery 404 later.
Protect the rankings you’ve already earned
A redirect map is a few days of careful work protecting years of accumulated equity. If you’d rather have it built, tested, and monitored by a team that does this every month, see our platform migrations service — or start with an SEO audit to learn exactly which URLs carry your traffic.