Blog / Technical SEO /
Technical SEO: redirect maps for catalogue changes
Products get retired. Variants get merged. Collection URLs get replaced.
Someone exports the old links and starts adding redirects. Before long there’s a spreadsheet full of arrows. It looks like progress. It isn’t a redirect plan yet.
Each old URL needs a decision: does it have a relevant destination, and how will you test the change? A good redirect map protects useful paths through the site. It doesn’t promise that rankings or traffic will stay exactly the same, and I’d be wary of anyone who says it will.
Collect the URLs before changing them
Build the source list from more than one place. Crawl the current site, export products and collections, review sitemaps, inspect Search Console landing pages and check analytics for pages people still visit. Include URLs found in internal links and important external references where those records are available.
No export is complete by itself. Old campaigns, discontinued products and unlinked support pages may be missing from a catalogue export. Preserve the source URL exactly, including protocol, hostname, case and path, then note the intended destination and why it fits.
Decide what each URL should do
For every old URL, choose among keeping it, redirecting it to a close replacement, consolidating useful content into a relevant page or returning a not-found status. Don’t send a retired product to the home page just because it’s easy. A redirect should help the visitor continue the task they started.
If several old pages are merged into one, make sure the destination covers the useful information from each. If a page has no relevant substitute and no continuing value, a proper 404 or 410 may be more honest. The map should record the decision, not just the destination.
Make direct, testable redirects
Use direct redirects from old to final URLs. Avoid chains, loops and redirecting to pages that are themselves scheduled for removal. Update internal links so the site does not rely on redirects for routine navigation. If a domain or platform is changing, keep the old host available to serve the redirects.
Check how the platform implements redirects and whether rules are case-sensitive or affected by query parameters. Shopify and other systems have their own constraints. Test a representative group of URLs in staging or a safe environment before applying a large batch. I wouldn’t push a big redirect import without testing a sample first. Keep a backup of the original mapping.
Prioritise the highest-value paths
Not every old URL deserves the same investigation time. Prioritise pages with relevant search visibility, visits, links, sales or support value. A low-traffic page may still be critical if it answers an important customer question. Record the reason for prioritisation so the team can revisit it later.
Keep the map manageable by grouping similar URL patterns while preserving page-level exceptions. A broad wildcard can save time and also capture paths that should not be redirected. Test the rule against URLs expected to match and URLs expected not to match.
Launch and validate
After the catalogue change, crawl old URLs and check the response and destination. Confirm that the final page returns the expected status, loads correctly and has a canonical pointing to itself when appropriate. Update sitemaps to include current URLs, not old redirecting URLs.
Monitor server errors, Search Console indexing and relevant landing pages after launch. Search engines need time to process changes, and temporary movement does not prove the map is wrong. Fix concrete issues such as a broken destination, missing product information or a redirect loop. Keep a change log with the launch date and the map version used.
Keep the map useful after release
A redirect map should stay with the site documentation. If the next person needs to change a product range, they should understand what happened to the old URLs and why. Add new exceptions as they arise, and remove rules only after confirming they are no longer needed.
Plan exceptions before a bulk update
Some URLs deserve individual treatment even when most products follow a simple rule. A high-demand item may have a direct successor; a bundle may split into separate products; a category may be renamed but still represent the same range. Write these cases into the map instead of expecting a pattern to catch every exception.
Run the proposed rules against a sample list before deployment. Include URLs that should redirect, URLs that should remain and URLs that should return an error. Check how the platform handles encoding, trailing slashes and query strings. A rule that works for one product can match too broadly when product names share a prefix.
Keep redirects as part of operations
When a product is retired, ask who updates the redirect map and when. A catalogue manager may know about the change before the SEO owner does. Add a step to the retirement process so the URL decision happens with the stock and content changes, not weeks later.
Keep the map versioned and store it with the release record. If a customer or search report later reveals a broken path, the team can see what the intended destination was. Review old rules during major catalogue cleanups, but do not delete them just to make the list shorter; confirm they are no longer needed.
Write acceptance checks into the map
A redirect row is easier to validate when it includes the expected status, destination and reason. Add a check for the final page: does it load, describe the intended product or category and offer a next step? If several rows share a rule, list sample URLs to test and exceptions that must remain unchanged.
After launch, track unresolved rows separately from completed ones. A spreadsheet with hundreds of green cells can still hide a small set of important failures. I’d rather see a short list of open problems than a sea of green. Assign an owner to each open exception and record the date it was checked. That turns the map into an operational document rather than a file that disappears after deployment.
Related reading
- Technical SEO: soft 404s on retired products
- A practical review of page templates before a site redesign
- Schema markup in 2024: what’s still worth adding
Before your next catalogue update, pick five old URLs, including your best-selling retired product, and follow each one to where it ends up. Would a shopper be happy landing there? If any of the five makes you wince, the map needs another pass.