URL mapping is the assignment of every relevant old address to its best new destination. The table is created before launch and then used as the basis for acceptance. It protects users, links, and search signals from ending up on 404 pages or unfitting catch-all destinations.
Which columns belong in the mapping table
- old URL and status code
- page type and organic importance
- clicks, impressions, or backlinks, where available
- decision: keep, replace, merge, or remove
- new target URL and planned status code
- responsibility, test status, and comment
Choosing the right target
An old page is redirected to the new page that is closest in content. If no sensible replacement exists, a 404 or 410 status can be more honest than a blanket redirect to the homepage. A mass redirect turns different questions into the same destination for users and makes error analysis harder.
Avoiding redirect chains
The old URL should point directly to the final destination: A → C instead of A → B → C. Existing rules are therefore merged with the new mapping table. After launch, internal links and sitemap point directly to the new URLs, not to redirects.
Technical acceptance
- old URLs return the expected permanent redirect
- new targets respond with 200 and are indexable
- canonicals point to the final URL
- no loops or chains
- parameters and language versions behave in a controlled way
Shopify can manage redirects individually or via CSV. For larger Shopify relaunches, the mapping table is technically reviewed before import.
Primary sources and documentation
As of: August 29, 2026. This article describes a professional decision framework and is not a guarantee of revenue, rankings, or results.