A redirect map is useful only if each old address leads to the best live answer for the same user need. A spreadsheet that says “all old product URLs → homepage” may remove 404 errors while leaving shoppers lost. Audit the map against real landing pages, including important products, categories, guides and campaign URLs.
Inventory the addresses people and crawlers use
Combine the current site crawl, XML sitemap, Search Console pages, analytics landing pages, advertising destinations and links in public materials. Add known historical URLs from previous migrations. Record the old URL, content type, important links or visits, proposed new URL, reason and owner. De-duplicate normalized variants but keep a note of query parameters that carry business meaning.
Google’s site-move guidance recommends preparing URL mappings before configuring redirects. That preparation is the part many teams rush. Map a discontinued product to the closest useful successor or category when that genuinely helps the customer; if no relevant destination exists, a clear gone or not-found response can be more honest than a misleading homepage redirect.
Test the map as a shopper
| Old page | Candidate destination | Audit question |
|---|---|---|
| Specific product, new URL | Same product at its new address | Are variant, stock and price context preserved? |
| Retired product with successor | Successor product or clear replacement page | Would the buyer understand the relationship? |
| Old category | Equivalent category | Does the new page contain the expected range? |
| Old buying guide | Updated guide answering the same question | Are the promised answers still present? |
Check a sample manually before applying rules at scale. Redirects should usually land in one hop, not chain through several legacy URLs. Test status codes, final URLs, canonical tags, internal links and mobile behaviour. Keep the original map as a change record and confirm that new navigation and sitemap links point directly to final destinations.
Illustrative failure: a product family rename
Fictional example, not a Megvi client case. A UAE retailer changes the address pattern for 800 products. Its first rule sends every old item to a general category. A customer following an old link for a particular lamp lands among 100 unrelated items. The revised map sends active products to their exact new URLs, retired lamps with a direct successor to the successor page, and products with no good match to a clear category or unavailable-product explanation after manual review. The team checks 30 high-value URLs and a random sample from each mapping rule.
After launch, monitor 404s, redirect loops and important landing pages. If an old URL still gets clicks, test the customer journey again. The ecommerce migration checklist covers catalogue and launch work around this audit. Megvi’s ecommerce website service can review the map before a store migration. Bring the old and new inventories plus the pages that drive enquiries or orders.
Google Search Central guidance reviewed 19 October 2026. The retailer example is hypothetical.
Ahmed Elneil
https://megvidigital.comAhmed Elneil is a certified digital marketer and entrepreneur with over 5 years of experience helping brands grow through Search Engine Optimization (SEO), paid advertising, and CRM automation.