WP Plugin · Custom Fields

Queryra + ACF

Works (with notes)

ACF (Advanced Custom Fields) and Queryra work together with no configuration. Your standard product and post information is searchable automatically. Some advanced custom fields need a small extra setup — three simple options below, the easiest takes about 2 minutes and zero code.

Tested with

ACF 6.x (free & Pro)

Queryra plugin

v1.2+

Setup time

0 minutes

What works automatically

  • Standard post fields — title, content, and excerpt
  • For products: short description, price, stock, SKU, and featured image
  • All WooCommerce product attributes — both global (Products → Attributes) and custom per-product attributes
  • Standard categories and tags, plus brand from the major brand plugins (WooCommerce native, YITH, Perfect Brands)
  • Re-indexing happens automatically whenever you save a post or product in the WordPress editor — ACF doesn’t need a separate trigger
  • No configuration to make ACF and Queryra coexist — install both, you’re done

One ACF-specific note: if your theme renders ACF values into the post content (so they appear in the body of the post when published), those values are already searchable because Queryra reads the published post content directly.

What needs a small setup

Custom fields you create in ACF — text fields, dropdowns, selects, dates, numbers, repeaters, flexible content, groups, and most ACF Pro field types — aren't automatically searchable yet. The sync still runs whenever ACF saves; the field values themselves just aren't included in what Queryra learns.

This is the same situation for Meta Box, Pods, JetEngine, and any other plugin that stores custom field values the standard WordPress way. Native support is planned for v1.3. Until then, three simple options below.

Three workarounds for today

1

Use ACF's "Taxonomy" field type

Easiest option. Zero code. About 2 minutes.

Instead of choosing a text or select field when you set up your custom field in ACF, choose "Taxonomy". Point it at one of the searchable taxonomies — product tag works for most cases. Make sure the Save Terms option is enabled. Once you do, every value you fill in becomes a regular WordPress tag, which Queryra already reads. Best when your values are a finite list (like Cotton, Wool, Linen).

2

Use a WooCommerce product attribute

Best for product-specific facets. Zero code.

If your custom field is product-specific — Color, Size, Material, Pattern — define it under Products → Attributes in WooCommerce instead of as an ACF field. All WooCommerce attributes are searchable automatically. You also get attribute filtering and display on the product page from one place. The trade-off: this works for products only, not posts or pages.

3

Mirror to a tag with a save hook

For when you want the ACF editor experience but searchable values.

A small snippet of code copies the value of your ACF field to a product tag every time the field is saved. The ACF field stays a regular text or select for the editor; Queryra reads the mirrored tag. Requires a developer or comfort editing your theme's functions file. Email contact@queryra.com if you'd like the snippet.

What's coming in v1.3

  • Auto-detection of any custom taxonomy registered as public — no more fixed list of supported taxonomies
  • Opt-in custom fields whitelist — pick which ACF (and Meta Box, Pods, JetEngine) fields to include in search, per content type
  • The whitelist will auto-discover available custom fields from existing data. Direct integrations with plugin-specific APIs may follow based on user demand.

Troubleshooting

If search isn't showing results after setup, the most common causes are: incomplete import, sync frequency too low for testing, or a conflict with another search plugin (FiboSearch, Relevanssi, SearchWP).

Full troubleshooting guide — fix in 5 minutes

More questions? See the general FAQ or email contact@queryra.com.

Try Queryra freeWordPress plugin docs

Last updated: May 6, 2026 · Last tested with ACF 6.x (free & Pro) and Queryra plugin 1.2.x.