How noindex Works on Wix Stores
On Wix, noindex is implemented through the platform's built-in SEO settings rather than direct server-level control. For each page type — products, collections, blog posts, dynamic pages — Wix injects a robots meta tag into the page's HTML head when you toggle the 'Hide from search engines' option in the SEO panel. The resulting tag reads <meta name='robots' content='noindex, nofollow'> and is rendered server-side, so crawlers see it reliably without JavaScript execution.
Wix does not give store operators direct access to the HTTP X-Robots-Tag header or a global robots.txt noindex directive at the page level. All noindex signals on Wix flow through that meta tag alone. This means the mechanism is standard and respected by Google, Bing, and other major crawlers — but the control surface is narrower than on self-hosted platforms like WooCommerce or Magento, where you can set headers at the server or CDN layer.
Where to Find and Set noindex in the Wix SEO Panel
For individual product pages, navigate to your Wix dashboard, open the Wix Stores product list, click a product, and select 'SEO' from the left sidebar. At the bottom of that panel sits the toggle labeled 'Hide this page from search engines.' Enabling it writes the noindex meta tag to that product's rendered HTML. The same toggle exists for collection pages under Wix Stores > Collections > select a collection > SEO.
For pages outside the Wix Stores context — thank-you pages, checkout steps, cart pages — go to the Editor or Dashboard page list, click the three-dot menu beside any page, and choose 'SEO Settings.' The same hide toggle appears there. Wix's checkout flow and cart are hosted on wixstores.com subdomains and are already excluded from indexing by Wix's platform-level robots.txt directives, so you do not need to manually noindex those URLs.
Dynamic pages built with Wix's CMS (formerly Wix Content Manager) expose noindex settings inside the collection schema editor. Under 'SEO & Sharing' for a dataset, you can set a default noindex state for all items in that collection, then override it per item. This is the correct path for stores that generate hundreds of filtered or faceted landing pages programmatically through Wix's repeater and dataset components.
Wix URL Patterns That Need noindex Attention
Wix Stores generates several URL patterns that create indexation problems if left unchecked. Tag pages follow the pattern /products?tag=keyword and are crawlable by default. These thin-content aggregate pages duplicate product titles without adding unique value and accumulate crawl budget. Wix does not provide a bulk noindex toggle for tag pages; each must be handled individually through the SEO panel on the tag's dynamic page template, or blocked in the Wix robots.txt editor under SEO Tools.
Sort and filter URLs — for example /products?sort=price_asc or /products?color=red — are Wix's other common duplicate-content source. Wix adds canonical tags pointing to the base collection URL by default, which is the correct signal, but canonical is a hint rather than a directive. For collections with heavy faceted navigation and high crawl budgets, adding a noindex to filter-result pages through Wix's URL redirect manager or dynamic page SEO settings prevents crawlers from spending budget on parameter variants.
Search result pages on Wix (/search?q=keyword) are indexed by default. Wix does not auto-noindex internal search results the way some platforms do. Store operators running Wix Site Search should manually apply noindex to the search results page template through the Editor's page SEO settings — treating every unique search-query URL as a noindex candidate prevents infinite crawlable URL space.
Limitations Specific to Wix and How to Work Around Them
Wix does not support bulk noindex operations through its native dashboard. If a store has 500 out-of-stock product variants that need noindex, toggling each manually is the only native path. The Wix API (specifically the Pages API and the SEO module) allows programmatic updates via Wix's Velo developer environment. Using Velo, a developer can write a script that iterates a product collection, checks stock status, and sets the SEO visibility field to hidden — effectively bulk-applying noindex without touching each page individually.
Wix does not expose a site-wide custom HTTP header interface, so X-Robots-Tag is unavailable. If a third-party app installed from the Wix App Market renders its own pages in an iframe or on a different subdomain, those pages exist outside Wix's SEO panel entirely. For apps like loyalty portals or external review platforms embedded via Wix, noindex must be configured within the app's own admin settings, not through Wix.
Google Search Console integration on Wix is managed through the Wix SEO Tools dashboard rather than manual HTML tag or DNS verification. This means operators can monitor which pages Google has indexed, and cross-reference that list against pages that carry a noindex tag set through Wix's panel — a useful audit step to confirm Wix is rendering the tag correctly for all intended pages.
Actionable noindex Audit for Wix Stores
Start by crawling the store with a tool like Screaming Frog or Sitebulb, instructing it to render JavaScript. Export all URLs and filter for those with a noindex meta tag. Cross-reference that list against the Wix sitemap (found at yourdomain.com/sitemap.xml) — any URL appearing in both the sitemap and the noindex list is a misconfiguration, because Wix should automatically exclude noindexed pages from its generated sitemap. If you find overlap, re-check the toggle state in the Wix SEO panel for that specific page or dynamic collection.
Next, audit tag pages, search result pages, and filter URLs by fetching them in Google Search Console's URL Inspection tool. Confirm each returns 'Page is not indexed' for pages where noindex is intended. For any page incorrectly indexed despite a noindex toggle, clear Wix's platform cache through the SEO Tools panel and request re-crawling. Wix's CDN caching can delay meta tag propagation by several hours after a setting change, so verification should happen at least 24 hours after toggling.