Merchlint
Available now
Next, in this order
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install
← All checks

WooCommerce product not showing on the shop page

It sold well, and then somebody hid it—visibility set to Hidden, or the status back to Draft. Almost never a decision, usually a bulk edit or an import.

Group
Money
Confidence
F — fact read directly from your store
Name on the plugin screen
Selling, but hidden
Included in
the free plugin
Updated
Code
A3

The symptom

A product that sold steadily all year is no longer anywhere in the store. Not out of stock—the stock is there. It is simply not in the catalog: either its catalog visibility is set to Hidden (or Search results only), or its status went back to Draft or Private.

If only the visibility changed, the URL still works, so anyone with the old link sees a normal product page. A draft or private product gives customers a 404 “page not found” error instead. Nobody else can find it at all, and nobody reports it, because a product that quietly disappears causes no error and no complaint.

Video, 1:13 — WooCommerce product not showing in the shop? Check these two fields

What it costs

This is the finding where the number is not an estimate. The product earned a known amount over the past twelve months; today it earns nothing, and the difference started on the day it was hidden.

It is also the finding people are most surprised by. Nobody remembers hiding it, because usually nobody decided to:

  • A bulk edit on a filtered product list where the filter matched more than expected.
  • An import with a status column that set everything in the file to draft. What to check after an import: WooCommerce CSV import.
  • A staging copy pushed to the live site with statuses from a half-finished editing session.
  • Someone hiding a product for one afternoon during a photo shoot, three months ago.

The tell is clustering. If forty products were hidden within the same minute, you are not looking at forty decisions.

How to check it yourself

In the admin. Above the product list there are Drafts and Private links. Each shows the products with that status, which customers cannot see in your store. A link appears only when there are such products. The list does not show catalog visibility and cannot be filtered by it. You can check it in the product itself (the Publish box, Catalog visibility) or in Quick Edit (the Visibility field), one product at a time. Search results only hides the product from the shop and category pages just like Hidden does; customers can find it only through the search box.

If both look right (the product is published and visible) and it still does not show:

  • It is out of stock, and the store hides such products. WooCommerce → Settings → Products → Inventory, Hide out of stock items from the catalog. With that box checked, a product at zero stock disappears from the store until it is restocked. A product that sold all year and cannot be bought today has its own check: A1.
  • The status is Scheduled. The publish date is in the future, and the product appears on that date, not before.
  • A page cache still serves the old shop page. After the change, clear the cache in your caching plugin or at your host.
  • Its parent does not exist or is not published. The admin never shows this field. On WooCommerce 11.1 and 11.2 a parent that does not exist hides the product from the store, the categories and search, and a simple product cannot be bought either; a parent that is an unpublished product hides it in every version. It has its own check: B11.

All at once, from the command line (for developers). Since WooCommerce 3.0, catalog visibility is not stored in postmeta but in the product_visibility taxonomy, with terms such as exclude-from-catalog and exclude-from-search. That trips up most hand-written queries:

wp db query "SELECT DISTINCT p.ID, p.post_title, p.post_status, p.post_modified, t.slug
  FROM wp_posts p
  LEFT JOIN wp_term_relationships tr ON tr.object_id = p.ID
  LEFT JOIN wp_term_taxonomy tt ON tt.term_taxonomy_id = tr.term_taxonomy_id
       AND tt.taxonomy = 'product_visibility'
  LEFT JOIN wp_terms t ON t.term_id = tt.term_id
  WHERE p.post_type = 'product'
    AND ( p.post_status IN ('draft','pending','private')
          OR t.slug = 'exclude-from-catalog' )
  ORDER BY p.post_modified DESC"

Read the post_modified column carefully: that is where the clustering shows. Products changed within the same minute were changed by one action.

To see which of them mattered, compare them with sales. WooCommerce keeps a lookup table for exactly this:

wp db query "SELECT product_id, SUM(product_net_revenue) AS revenue
  FROM wp_wc_order_product_lookup
  WHERE date_created > DATE_SUB(NOW(), INTERVAL 12 MONTH)
  GROUP BY product_id ORDER BY revenue DESC"

How to fix it

  1. Start from the revenue list, not the product list. Restoring the three products that earned real money is an afternoon’s work with a measurable result; going through all two hundred hidden products is a week with no result.
  2. Restore visibility, then check that the product is actually complete: price, stock, image. A product hidden mid-edit may have been hidden for a reason that was valid at the time.
  3. Find the action, not the products. If they cluster by post_modified, undo the cause: correct the import mapping, or note which filter the bulk edit used.
  4. For genuinely discontinued lines, hidden is the right state and keeping the product is correct—it preserves order history. Hide the finding so it stops coming back.

When it’s a false alarm

  • Products sold only through a direct link: a bundle reached from another product, an upsell, a private offer for one customer. Hidden is exactly right for those.
  • Seasonal lines put away deliberately until next year.
  • Discontinued products kept for order history, which is the correct thing to do rather than deleting them.

All three are decisions. This check exists to separate them from the ones that were not.

How Merchlint finds it

Merchlint starts from the products that earned money over the past twelve months, taken from WooCommerce’s own order lookup table, and reads each one’s status and product_visibility terms. It reports a product that is not published, or that is set to Hidden or Search results only. It reports only products with sales: a hidden product that never sold is not interesting, and reporting it would bury the ones that are. From version 0.3.5 the same goes for a product whose sales earned nothing in that period: sold only at a price of 0, such as a free gift added to orders, or with every sale refunded.

The finding shows the status, the catalog visibility, the reason (not published, or hidden from the catalog), and the revenue with the period it covers. It does not show when the product was changed; for that, use the post_modified column from the query above.

Confidence: F—fact from the database. A status and a taxonomy term are read; the revenue is summed from recorded orders.

Revenue is never added up across currencies. A store selling in more than one gets a figure for each, because adding them without an exchange rate would mean inventing a number.

Run this check on your store

Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com