How Wix Handles 301 Redirects
Wix gives store operators a native redirect manager inside the dashboard under Settings → SEO → Redirects. Every redirect created there issues a 301 status code — a permanent redirect — which signals to search engines that a URL has moved and that link equity should transfer to the new destination. For Wix stores running on Wix eCommerce, this covers product pages, collection pages, blog posts, and static pages.
Unlike open-source platforms where redirects sit in a server config file or a plugin database, all Wix redirects are stored at the platform level. Wix's infrastructure handles the HTTP response before the page ever renders, so there is no performance penalty from JavaScript-based fallbacks. The redirect manager supports one-to-one URL mapping and accepts both relative paths (e.g., /old-product) and full URLs from the same domain.
Wix Redirect Manager: Conventions and Limits
When creating a redirect in Wix, the old URL field must be a path without the domain — enter /old-slug not https://yourstore.com/old-slug. The destination field accepts internal paths or full external URLs. Wix does not support wildcard redirects natively, meaning you cannot write a single rule like /products/* → /shop/* to catch an entire URL pattern. Each redirect must be entered individually.
The redirect manager has a documented limit of 2,000 redirect rules per site. For large catalogues with seasonal product turnover, this ceiling is a real constraint. Wix also does not support regex-based rules, so complex URL restructures — such as migrating from a parameterized URL structure to clean slugs — require manually creating one rule per retired URL. Bulk CSV import for redirects is available, which reduces the manual entry burden significantly for migrations involving hundreds of URLs.
Wix automatically creates redirects when a page slug is changed through the editor. If a product URL changes from /shop/blue-sneakers to /shop/blue-running-sneakers, Wix generates the redirect without any manual input. This auto-redirect behavior covers product pages and collection pages but does not extend to Wix Blog URLs when the blog post slug is edited — those require a manual entry in the redirect manager.
Ecommerce-Specific Redirect Scenarios on Wix
Discontinued products are the most common redirect trigger in Wix stores. When a product is deleted, Wix does not automatically create a redirect — the URL returns a 404. The correct practice is to create a redirect from the deleted product's path to the most relevant in-stock category or a comparable product before deletion. Check the old URL by navigating to the live product page before removing it from inventory.
Collection restructuring creates bulk redirect needs. If a Wix store reorganizes from broad collections (e.g., /shop/mens) to subcollections (e.g., /shop/mens-shirts, /shop/mens-pants), every old collection URL needs its own redirect rule pointing to the closest equivalent. Because Wix lacks wildcard rules, use the CSV bulk import: export the old URL list from Google Search Console's Coverage report, map destinations in a spreadsheet, then import the completed file into the redirect manager.
Wix stores that switch from a Wix subdomain (username.wixsite.com/store) to a custom domain inherit a different redirect challenge. Wix handles the subdomain-to-domain transition at the platform level when a domain is connected, but individual page paths still need to be verified in Search Console for the new property. Submit a new sitemap under the custom domain and monitor for 404 spikes in the first 30 days.
Workarounds for Wix Redirect Limitations
The 2,000-rule ceiling and the absence of wildcard support are the two limitations that cause the most friction for scaling stores. For stores approaching the limit, audit existing redirects annually and remove rules for URLs that no longer receive crawl traffic or have zero impressions in Search Console. A stale redirect from a URL with no inbound links and no search impressions wastes one of your 2,000 slots.
For wildcard-style redirect needs, the only workaround within Wix is a landing page acting as a redirect hub. Create a Wix page at a catch-all URL (e.g., /discontinued) and use Wix's built-in SEO settings on that page to explain the change, then link prominently to the relevant live collections. This is not a technical redirect but it stops link equity from dissolving entirely on high-traffic category paths that no longer map cleanly to new URLs.
Third-party Wix apps in the Wix App Market offer extended redirect functionality. Apps in the SEO category can manage redirect rules outside the native 2,000-rule cap and some provide regex and wildcard support. Evaluate any app's approach carefully — if the redirect is handled via client-side JavaScript rather than a server-level HTTP header, it will not pass link equity reliably and may not be treated as a true 301 by search engine crawlers.
Actionable Steps for Wix Store Redirect Management
Establish a redirect protocol before any URL change, not after. When a product is about to be deleted, copy its current slug, draft the redirect rule in a spreadsheet, and publish the redirect in the manager before the product is removed. This eliminates the window of time where the URL returns a 404 and any crawl that occurs in that window logs a soft 404 against the domain.
Audit the redirect manager quarterly using Google Search Console's Coverage report filtered to 'Not found (404)'. Cross-reference 404 URLs against your redirect manager export to find gaps. Prioritize redirects for URLs that still receive impressions or have external backlinks — check backlink data in Search Console's Links report or in any crawl tool that reports inbound links. Fix high-value 404s first and work down by traffic priority.