Back to all posts
Blogs
How to Map Old URLs to New Pages During a Content Migration
A guide to mapping old URLs to new pages during a Shopify content migration.
4 minutes, 10 seconds
A content migration, moving pages, restructuring information architecture, consolidating sections, lives or dies on the quality of one artifact: the URL mapping table connecting every old page to where its content now lives. Get the mapping right and the migration is nearly invisible to search engines. Get it wrong and rankings scatter.
This guide is for merchants planning a content migration who want a systematic approach to building and applying the URL mapping that protects existing search visibility through the transition.
Quick Answer
Yes, a content migration's SEO risk comes down almost entirely to the quality of its URL mapping. Inventory every existing page, decide its new location in the migrated structure, and build a complete old-to-new mapping table before moving anything. Apply that mapping as bulk-uploaded 301 redirects through SC Easy Redirects at the exact moment the migration goes live, then use 404 tracking to catch whatever the table missed.
What This Involves
Mapping old URLs during a content migration means building a complete table connecting every existing page to its new location before the migration executes, applying that table as bulk redirects at the moment of launch, and monitoring for gaps afterward, treating the mapping as the migration's central deliverable rather than an afterthought.
Who Needs This
- Merchants restructuring their site's information architecture
- Stores consolidating or reorganizing content sections
- Brands migrating content between platforms or major site sections
- Teams planning any project that will move a significant number of pages
- Anyone treating a content migration as primarily a content task rather than also a URL task
Why It Matters for Your Business
- The mapping table is what actually protects search rankings through a migration
- An incomplete mapping scatters rankings across broken and orphaned pages
- Bulk upload makes applying even a large mapping table efficient
- The mapping should exist before content moves, not be reconstructed after
- 404 tracking is the safety net for whatever the table missed
- This is worth treating as seriously as the content work itself
How to Map Old URLs to New Pages During a Content Migration on Shopify
Step 1: Prepare Your Store
Start by inventorying every page the migration will touch.
- Export or list every existing URL involved in the migration
- Note current traffic and rankings for each as a priority signal
- Identify any pages being consolidated together, not just moved one-to-one
Step 2: Install and Configure SC Easy Redirects
Build the complete mapping table before touching anything in SC Easy Redirects.
- Assign each old URL its new destination in the migrated structure
- Handle consolidated pages by choosing the strongest destination
- Flag pages with no clear new equivalent for a deliberate decision
Step 3: Create Your Logic
Apply the mapping as the migration goes live.
- Bulk upload the complete mapping table at the moment of launch
- Use redirect patterns for any systematic structural changes
- Group the migration's redirects together for coordinated review
Step 4: Test
Verify the mapping worked as intended.
- Spot-check high-traffic pages resolve to their correct new destination
- Confirm consolidated pages land somewhere that makes sense
- Check that patterns caught systematic changes correctly
Step 5: Go Live
Monitor and complete the mapping as gaps surface.
- Watch 404 tracking closely through the weeks after migration
- Track rankings for key pages against their pre-migration baseline
- Add any missed URLs to the mapping table as they are discovered
Examples & Use Cases
B2B Supplier's Resource Center Migration
Industry: Industrial
Problem: Migrating a large resource library into a new information architecture risked orphaning dozens of well-ranked pages
Setup: Built a complete mapping table before touching any content, then bulk uploaded it through SC Easy Redirects at the exact moment of migration
Result: Rankings transferred cleanly to the new structure with only a handful of stragglers caught by 404 tracking
Home Goods Brand Consolidating Guides
Industry: Home goods
Problem: Several overlapping buying guides needed consolidating into fewer, stronger pages during a content migration
Setup: Mapped each old guide to whichever consolidated page best matched its content and traffic history
Result: The consolidated guides inherited the combined traffic instead of splitting it across orphaned old URLs
Read more case studies for our apps here.
Best Practices
- Treat the mapping table as the migration's central deliverable
- Inventory every page before deciding anything about the new structure
- Build the complete mapping before content actually moves
- Bulk upload the mapping at the exact moment of migration launch
- Use patterns for systematic structural changes
- Verify high-traffic and consolidated pages specifically after launch
- Watch 404 tracking closely for weeks to complete the mapping
Summary
A content migration's SEO outcome is decided almost entirely by the completeness of its URL mapping table, built before the move and applied at the exact moment of launch. The core steps are inventorying every existing page, mapping each to its new destination deliberately, and applying the complete table as bulk redirects while monitoring for gaps afterward.
If a content migration is on the horizon, SC Easy Redirects can carry the mapping that protects every page's search history.
Frequently asked questions (FAQs)
The completeness and accuracy of the URL mapping table connecting old pages to their new locations.
Choose the strongest destination among the pages being combined, typically whichever had the most traffic or backlinks.
At the exact moment the migration goes live, so no window exists where old URLs return 404s before their redirects exist.
Flag them for a deliberate decision, redirecting to the closest relevant page or allowing genuinely obsolete ones to be retired without a redirect.
Bulk upload handles large mapping tables in one operation, far faster than creating redirect entries individually.