The WooCommerce search that understands your references
Test it first on your own site: search the same reference in three forms — M8x20, M8 x 20, M8-20. If the three result counts differ, this page is for you.
What native search can't do
A blog search, not a catalog one
WordPress searches through posts. On technical references — “H07V-U 2.5mm²”, “6205-2RS” — word matching fails. What its code does, field by field: why your platform's native search engine isn't enough.
Reference spellings
“M8x20”, “M8 x 20”, and “M8-20” return different results depending on how your catalog was entered. The test to run on five of your references: search by reference on a B2B catalog.
Ranking
Results come out by date or by title, not by relevance for a professional buyer.
The integration, concretely
WordPress's standard hook
Our extension intercepts the query via pre_get_posts and dictates the list and order of products. Rendering stays entirely your theme's.
Compatible with your extensions
Your filters, variations, and product-page plugins keep working: only which products come out, and in what order, changes.
Automatic fallback
If Heurix doesn't respond, native search takes back over — and retries a minute later, with no intervention needed.
3 to 4 days
Estimate, for a catalog already exported, settings included.
The extension is published on wordpress.org, live since September 28, 2026, version 0.2.0. It installs from your WordPress admin — Plugins, Add New, search for “Heurix Search” — or from its directory page. No feature is held back for a paid version: what you pay for is the service, not the plugin.
What your site needs
The versions
WordPress 5.9 to 7.1.2, WooCommerce 6.1 to 11.1.2, PHP 8.1. These are the versions that were actually run, one at a time, not versions announced: each lower bound is the version where the plugin stops working.
WooCommerce 6.0 and older
Search shows its first page and returns an empty second one. The plugin does not detect this: it does not read the WooCommerce version, only whether it is present. That is what sets the bound at 6.1.
The “woocommerce” folder
Since WordPress 6.5, activation is refused if WooCommerce lives in a folder with another name — even when WooCommerce is running and the plugin would work. WordPress resolves the dependency by folder name. Rename it, or install WooCommerce from wordpress.org.
A Heurix key
A server key (prefix hx_) and a catalog created. Nothing leaves your site before the key is entered: without it, the plugin opens no connection at all.
How those bounds were found, what was not measured, and the kit to redo the measurement: what the wordpress.org review asked for.