PREFLIGHT CHECK

WooCommerce catalog visibility CSV checker

Validate WooCommerce catalog visibility values as visible, catalog, search or hidden.

Check CSV

＋Choose a CSV fileTap/click to choose. Drag and drop also works on desktop.

🔒 Analysis runs in your browser; the file itself is not sent to BlueprintLab.

What this tool checks

visible / catalog / search / hidden
Blank-value review
Unsupported values

What it cannot determine

This unofficial checker covers only rules that can be verified in the browser. Live account settings, remote server state and later service-side validation remain authoritative.

How to use this tool

Validate WooCommerce catalog visibility values as visible, catalog, search or hidden.

Use Try sample to inspect the included sample.
Set ＋ Choose a CSV file Tap/click to choose. Drag and drop also works on desktop..
Use Check CSV to process the input.
Compare the result with your source data and return to the input to make corrections.

＋ Choose a CSV file Tap/click to choose. Drag and drop also works on desktop.: .csv,text/csv

Input and settings example

Type,SKU,Name,Visibility in catalog
simple,SKU001,Sample Product,visible

This column is about where a product appears, not whether it is published

`Visibility in catalog` controls placement in the catalog and search experience. Its supported values are `visible`, `catalog`, `search`, and `hidden`.

It is separate from the `Published` state. Using `hidden` because you mean “draft” mixes two different WooCommerce concepts.

The four values are combinations of discovery surfaces

`visible` means catalog and search, `catalog` means catalog only, `search` means search only, and `hidden` means neither surface.

The checker reports unsupported spellings as errors. If the column is absent, it now warns rather than declaring the whole CSV invalid.

Column absence and an explicit hidden value have different meanings

An update CSV might intentionally omit this optional column when catalog visibility is not part of the change. That is different from actively sending `hidden`.

When you see the missing-column warning, decide first whether this file is supposed to modify catalog visibility at all.

Review publication state separately

If the same import also changes product status, run the WooCommerce Published checker. Keeping visibility and publication as separate checks makes combinations such as a visible-but-draft product easier to understand.

Go one step deeper

Five checks before a bulk CSV import →