Large e-commerce sites should treat redirects as ongoing URL management, not a one-time upload of rules during a redesign. Start with a complete inventory of URLs and existing redirects, map each permanently moved page to its new counterpart, and use batch rules for URLs that follow consistent patterns. Support this work with testing, a phased rollout, and post-launch monitoring. Beyond checking that redirects work, confirm that destination pages correspond to the original pages, that there are no redirect chains, and that old links continue to function. The following is based on migration recommendations published by tenten.co in 2025 and should not be treated as current official rules from search platforms.
Build a complete URL inventory before setting priorities
Managing thousands of product pages should not rely solely on manual fixes, one page at a time. First, crawl the site, compile the old URLs that need to change, and list existing redirects separately so they are not overlooked during migration. Include all relevant URLs in the inventory, then prioritize checks on the following:
- High-traffic pages: refer to Google Analytics and Search Console data.
- Pages with important backlinks: confirm that old pages linked to from external sites still have appropriate destinations.
- Key conversion pages and image URLs: do not limit the inventory to product pages; include image URLs that may bring in traffic.
Map permanent moves precisely rather than sending everything to the homepage
For pages whose URLs are changing permanently, create a 301 mapping table linking each old URL to its corresponding new URL, rather than redirecting all old pages to the homepage. A 301 signals a permanent move, but it does not guarantee that rankings or traffic will remain unchanged.
For URLs with a consistent structure, use rules to handle redirects in batches—for example, mapping /product123 to /new-category/product123—provided that the structural change applies to the pages concerned. During testing, confirm that redirects work and that there are no redirect chains or loops. Update internal links at the same time.
Check administrative permissions when choosing an implementation method
Do not choose tools based solely on the number of rules. Before using a platform’s bulk import tool, confirm which features the platform and tool support. Setting up redirects at the server level requires the relevant administrative permissions. The source also suggests CDN-level redirects as an option for reducing origin server load, but explicitly warns that their effects on caching must be tested. Ease of deployment is not a reason to skip validation.
Roll out in phases and continue maintenance after launch
Before launch, validate redirects locally and run load tests in a staging environment. Then introduce redirects in phases while watching for changes in load times and conversion rates. After launch, continue tracking 404 errors, crawling and indexing issues, traffic, and rankings. Set up anomaly alerts so the team can investigate promptly.
If the domain is also changing, maintain the old domain and its DNS so redirects on the old URLs continue to work. Update product links on external sales platforms as well. Completing redirect deployment does not mean link maintenance is finished.
Redirect management for large e-commerce sites: perspectives from across the web
Where should an old URL redirect after a product is removed?
The source recommends prioritizing a category page for similar products rather than the homepage, so visitors arriving through old links can still find relevant products. This recommendation applies when a product has been removed but the site still has a relevant category to browse. Before setting up the redirect, confirm that the category page is genuinely relevant to the original product; do not use the same destination for every removed product.
How should seasonal campaign pages and multilingual pages be handled?
For seasonal campaign pages, consider temporary 302 redirects and remove them after the campaign ends. Keep historical data for reference the following year. When migrating multilingual pages, use region-specific redirects alongside hreflang settings. The two cases serve different purposes: seasonal redirects handle temporary changes, while multilingual migrations also require URLs to be mapped to the appropriate language and regional versions.
How can you check how product pages appear in search after redirects are in place?
After migration, check that the existing Schema structured data has been carried over fully and correctly to the new pages. Missing markup can affect whether rich snippets appear. You can also track link equity metrics for redirected pages to identify pages that need further investigation. These checks help uncover maintenance issues, but they cannot guarantee that rich snippets will appear or that rankings and traffic will remain unchanged.
References
- 網站搬家不崩潰:這樣做就對了! (指南+避雷)tenten.co · 2025-04-23T14:32:08.000Z — Discusses: Where should an old URL redirect after a product is removed?; How should seasonal campaign pages and multilingual pages be handled?
