Connect facets to content fields

A facet works only when its source points to consistently stored values. Inspect several real items before entering a source key.

Map meaning before interface

Use this worksheet for each proposed filter:

Choose the source type

• Taxonomy uses a registered taxonomy key and preserves term identity and hierarchy.
• Meta uses a short custom-field key. Do not use TinyMCE or textarea fields as facet sources.
• Post field uses a supported native post value such as the title.
• Post type distinguishes objects by post type and uses the fixed post_type key.
• WooCommerce exposes supported product values such as attributes, price, rating, or stock-related data.
• Location provides coordinate data for Proximity and Map.

The exact source key is not the field’s visible label. Confirm the taxonomy slug, meta key, or supported WooCommerce key in the content model.

Normalize the content

Before indexing:

1. Merge duplicate taxonomy terms that mean the same thing.
2. Standardize numeric values without mixed units or decorative text.
3. Store dates as values the date facet can normalize.
4. Ensure coordinates contain valid latitude and longitude.
5. Fill the field on enough published items to make the filter useful.

An empty field is not the same as a zero value. Use Not empty when the intended question is whether the source contains a value.

Index and inspect

After saving the facet, run Reindex context. Add its Faceted Search Facet element temporarily and check the visible choices and counts.

If labels are right but result cards lack a custom field, add that field separately under Indexed metas. Facet indexing and result-card payloads serve different purposes.

See Facets and data sources for the complete supported combinations.