WP Plugin · Page Builder

Queryra + Breakdance

Works out of the box

Breakdance and Queryra work together with no configuration. Page titles, taxonomies, WooCommerce attributes, and Breakdance builder body content are all indexed automatically. The plugin reads Breakdance's _breakdance_data postmeta and extracts the visible text from headings, text blocks, buttons, and captions during sync — zero plugin conflicts, zero setup.

Tested with

Breakdance 2.7.1

Queryra plugin

v1.3+

Setup time

0 minutes

What works

  • Page title, excerpt, content — fully indexed and searchable.
  • Breakdance builder body content — headings, text blocks, button labels, captions, alt text authored in the Breakdance visual editor. The plugin reads _breakdance_data postmeta and recursively extracts visible text during sync.
  • Taxonomies — categories, tags, product tags, the brand taxonomies recognised by Queryra (product_brand, yith_product_brand, pwb-brand), and any public custom taxonomies you've registered.
  • WooCommerce product attributes — both global and custom per-product attributes, regardless of how the product page is built.
  • No plugin conflicts. Breakdance only hooks posts_where in two admin-only utility contexts (form submissions, design library) and doesn't modify frontend search. Queryra hooks pre_get_posts and posts_search. Zero overlap.

How it works (technical)

Breakdance and Queryra coexist without any shared hooks on the frontend search path. Empirically verified on a clean test environment (WordPress + Breakdance 2.7.1):

  • Breakdance stores user-authored content in _breakdance_data postmeta (typically hundreds to thousands of bytes per page). The post_content column contains only a small Gutenberg block launcher comment.
  • Queryra reads the _breakdance_data structure during sync and recursively extracts text values from every node — headings, paragraphs, buttons, captions, alt text. Result: search returns Breakdance pages by their actual content, not just by title.
  • The same mechanism handles content from Elementor, Oxygen, and Beaver Builder automatically (postmeta-storing builders). For custom or non-standard storage, see the queryra_indexable_meta_content developer filter (lets you append content from any source).

Troubleshooting

If AI 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 14, 2026 · Tested with Breakdance 2.7.1.