Ecommerce Migration: Map 301 Redirects for Products, Categories and Guides

Moving an ecommerce store to another platform often changes the addresses of product pages, collections and editorial guides. Customers may still open saved links, while search engines and other sites continue requesting the previous URLs. A useful redirect map connects each old address to the new page that genuinely answers the same question or represents the same product. It is a content-matching exercise first and a technical HTTP configuration second.

Start by knowing what the former URLs contained, which products and categories survive, and how languages and variants are represented on the new platform. A clear old-to-new list lets you decide between permanent redirects and properly unavailable content. It also provides a practical basis for checking response codes, canonical URLs, internal navigation and XML sitemaps when the new storefront is made public.

Build an inventory of the former product, category and guide URLs

Create a thorough inventory of existing public URLs before changing the platform or path structure. Export current product and collection addresses from the old catalogue and include guides, advice pages and other content that people can reach independently. Record the page type, language, old product or content ID, title and its present status. These details matter when new platforms use different IDs or slugs. An old product code is often a more reliable link to its successor than a similar-looking URL word.

Combine the catalogue export with the old XML sitemap, Search Console information, navigation links and relevant server logs. Sitemaps record what the site previously presented for discovery; Search Console can expose URLs remembered by Google; logs show paths still being requested. These sources complement each other. The purpose is to identify addresses worth assigning decisions to, including older pages outside the current main menu.

Include links found in supporting content, product recommendations and previous campaign material where possible. A guide may have moved out of the category navigation but still be cited by another article. A discontinued product may retain useful external links. Without a record of the original content, it is easy to mistake those paths for irrelevant errors and forward them all to a generic destination. Maintaining context alongside the URL prevents that loss of meaning.

Give each inventory row a distinct old URL, the type of content, a language code, an existing product/content reference where available and a candidate new destination. Keep the decision pending until you have compared the actual new content. Distinguish a live former page from a pre-existing redirect and from a URL only mentioned in a feed. Not all three should become an identical technical rule. The mapping sheet becomes a reviewable record of what changed and why.

Google also advises considering images, videos and other assets that have their own discoverable URLs. These can be important when someone links directly to a document or photograph. Keep their mapping to appropriate new assets separate from the main product-and-guide mapping. An old image URL is not automatically best redirected to a product category page. The replacement should match the type of resource being requested.

Match content, search intent, language and product variant

The most useful destination is not always the URL whose slug looks most similar. An old product detail page (PDP) should normally reach the same product in the new catalogue. A product listing page (PLP) should reach a comparable collection, with the intended product assortment and browsing purpose. An advice article should arrive at an article that addresses its original topic. Compare content, shopper intent and language before accepting a redirect pair.

Product variants deserve their own check. A previous link may have been intended for a specific colour or size. If that variation still has its own address on the new platform, direct the mapping to the correct version. If the new model uses a canonical parent product page, confirm that the relevant available variation can actually be found and selected there. A blue shirt should not silently become a black one simply because the base model name is unchanged.

Language is also part of equivalence. A Dutch guide that previously answered a Dutch-speaking visitor should reach the corresponding Dutch version when that content exists. An English product page should not be routed to a random translated page merely because its category matches. Check whether the new market selection, assortment and language reflect the former page. A bulk redirect pattern can otherwise create mismatches that are invisible if only URL syntax is compared.

Several old addresses may legitimately converge on a single new page when their former content has genuinely been consolidated. Two overlapping guides about caring for the same material could be replaced by one comprehensive guide covering both questions. Redirecting both to that guide serves the reader. Sending every retired article to the homepage is very different: it often removes the original answer and can be interpreted as a soft 404.

If a product or article is permanently removed and no meaningful successor exists, allow a proper 404 or 410 response. Do not present an unrelated product as the replacement solely to keep a 301 in the sheet. A temporarily out-of-stock product is not automatically removed content and does not need a permanent redirect to another item. Keep its existing product page and explain the current availability through the storefront.

Record why each destination is appropriate. An editor can confirm the article's coverage, a product owner can confirm item and variant identity, and the site operator can confirm that the destination will be publicly reachable. This simple separation of responsibility helps prevent a technical mapping from being approved before its content has been checked. Google explicitly discourages mass redirects to unrelated destinations such as a new homepage.

Five fictional old-to-new mappings for products, PLPs and guides

Imagine a fictional shop moving from https://old.example to https://new.example. The five rows below cover two PDP URLs, a collection listing and two editorial guides. The Atlas jacket remains available, an old Series Z product has been permanently retired, the jackets collection moves to a new path, and two shorter guides are merged into a detailed care article.

Read the HTTP-status column as the decision for the old URL, not the status the final replacement should return. A permanent change uses a direct 301 or 308 to the relevant new URL. When the old content is permanently gone with no equivalent, 404 or 410 is appropriate. After following a redirect, a normal published destination should respond with 200, be reachable to crawlers and display the content identified by the mapping.

The two article redirects deliberately share one destination. This is appropriate because the new page covers both cleaning and general maintenance. It does not mean that all editorial pages can be consolidated. If one old guide concerned a different product or issue, its destination would need separate review. The table also shows that an obsolete PDP has no arbitrary ‘nearest’ substitute: its final status reflects the actual assortment decision.

Use direct 301 or 308 responses and verify the final page

Use a permanent server-side redirect for a permanently moved page, with 301 and 308 both recognised by Google. The old URL should point directly to its final destination rather than moving through one or more intermediate paths. If an old domain redirects to a temporary platform URL which then redirects to the new product URL, visitors experience needless extra requests. Update the first rule so that it reaches the final, intended address.

Test for chains and loops as well as individual response codes. A loop occurs when rules direct URLs back to one another. A chain can appear when an earlier destination is changed again without correcting its original incoming redirects. Google can follow some redirect chains but recommends direct final destinations. Read the complete path from old URL to final page; do not consider the first 301 alone a successful migration.

The intended new public product, category or guide page should ordinarily finish on an HTTP 200 response with the correct content. Verify that the destination shows the actual intended page and is publicly accessible when launched. A migrated page meant for publication also needs crawler access and appropriate indexability. A leftover noindex instruction from testing is not consistent with publishing an indexable replacement.

Be careful when a product variant used a URL fragment. Google does not index #blue and #black as separate pages: /product/atlas#blue is treated as the same basic URL as another fragment of that path. Distinguishable variant URLs require a suitable path segment or query parameter when the shop and its canonical policy support it. The redirect map should follow actual URL identities, not invent indexed fragment pages.

An out-of-stock item usually still has a valid product page. A temporary lack of inventory is not a permanent URL move to a competitor product or a different colour. Keep the original page where the product remains part of the catalogue and communicate its availability. For genuinely retired content with no useful successor, the deliberate 404 or 410 response is clearer than an unrelated 301. Permanent redirects represent a real location change or meaningful content consolidation.

A technical checklist for each moved URL is therefore simple: old response is permanent, intermediate hops do not exist, final response is 200, the displayed page matches the original intent, and robots/canonical signals fit its publication status. Failures can be corrected by changing the specific pair in the mapping rather than creating yet another forwarding layer.

Align new canonicals, hreflang, internal links and sitemaps

The map of old and new URLs is only one part of the change. New pages should clearly identify which address represents their preferred version. Indexable product, category and editorial pages generally use an appropriate self-referencing rel="canonical" to the published new URL. Product cards, breadcrumbs and navigational links should point directly to those new addresses. That removes unnecessary visits through legacy redirects and gives crawlers a consistent path.

Build the updated XML sitemap from the URLs that belong on the new public site. A replacement that returns 200, serves the intended content and is meant to be indexed can be included. An old address that now redirects should not remain the preferred URL in the new sitemap. Align the sitemap with the destinations named by your canonical tags and internal links. Consistency is particularly important when platforms generate different URLs for default filters or paginated collection views.

For multilingual stores, update the hreflang relationships to the actual new language-specific equivalents. A Dutch product page should reference the correct English version where it exists, not the former English URL that now redirects. Confirm that the language and market context of each pair remains relevant. A missing translation cannot be fixed simply by assigning a random page in another language as an equivalent.

Check site navigation, category templates, related-product blocks, older advice articles and footer links for old addresses. Migration rules will still serve visitors who arrive from bookmarks or external websites, but your own storefront should link to the final new paths. Where practical, important external references can also be updated. That reduces extra redirects while retaining a clear route for links outside your direct control.

Google's ecommerce URL structure guide explains why consistent paths, variant parameters and self-referencing canonicals help search engines understand a store. A good URL plan distinguishes a product family, a selectable variant and a paginated category without turning every transient state into a new indexable URL. Align those choices with the real platform behaviour before finalising redirects.

Use Change of Address only for the appropriate domain move

Google Search Console's Change of Address tool is for moves between different domains or subdomains, such as changing the entire shop domain. It is not part of every category or product URL restructuring. If a platform change only alters paths on the same domain, the relevant work is still the URL mapping, redirects, canonical signals and crawl checks, not an artificial domain-move request.

The tool is also not required solely for HTTP-to-HTTPS changes or switching between www and non-www on the same domain. Moving the hosting infrastructure while every public URL remains unchanged is not a URL move at all. Identify which type of migration you are actually carrying out before deciding whether a Change of Address submission is relevant.

Google recommends retaining permanent redirects as long as possible, generally for at least one year. This allows its systems and sites linking to the old pages time to discover and process the new addresses. Redirects may remain valuable beyond that minimum for customers following older bookmarks or links. Keep current internal navigation pointing straight to the new URLs even while old links continue working.

The official Google guidance on site moves with URL changes describes inventory, mapping, permanent redirects, sitemap updates and checks after launch. It also distinguishes URL moves from hosting changes with stable addresses. A clearly classified migration helps teams spend effort on the actual changed links rather than creating redirect rules where no URL has moved.

Review the planned move and the published destination URLs

Before launch, review a representative set of mapping decisions: an existing product with a variant, a collection, a consolidated guide and a retired item. Confirm that the intended new pages are ready and answer the original questions. After launch, follow the actual HTTP responses from the old addresses to the final pages. Compare what happens with the planned status and content; a mismatched destination calls for correction of that pair rather than another intermediate redirect.

Check the new page's 200 response, language, indexability, canonical and relevant internal links. Make sure its new address appears in the appropriate sitemap. Where an individual new product page has a separate indexing issue, the related guide Product Page Not Indexed in Google Search Console covers that distinct URL-level question.

Kiljano's 301 Redirect Map — 20 URLs reviews up to 20 supplied old-to-new URL pairs within one website or migration, checking the supplied destinations, gaps, duplicates and obvious chains. It delivers an editable UTF-8 CSV and a concise PDF of findings in a ZIP file.

The Webshop Launch Readiness — 30 Checks reviews thirty publicly accessible readiness points, including navigation, product pages, reachable checkout steps, languages and service information pages. The observations and priorities are provided in a PDF, with an optional TXT checklist packaged in ZIP. These reports offer a concrete basis for deciding which links or visible pages need attention.

Frequently asked questions about ecommerce 301 redirects

Should all old product URLs point to the homepage?

No. Match the same product or a real equivalent. For permanently removed content without a successor, use 404 or 410.

Can two old guides redirect to one new guide?

Yes, when that real consolidated page covers both original topics and serves the readers' intent.

What makes a 301 mapping work?

A direct permanent redirect to the final URL, with no chain or loop, followed by a 200 page containing the correct content.

Does temporary out-of-stock status require a redirect?

No. A product page can continue to show its current availability without permanently moving to another item.

Does #blue give a separately indexed product URL?

No. Google does not index fragment variants independently; use real paths or relevant query parameters where needed.

When do I use Change of Address?

For a domain or subdomain move, not merely new paths, HTTP to HTTPS, www switching or unchanged URLs on another host.

How long should permanent redirects stay?

Google recommends generally at least a year, and longer while previous links remain relevant.