| 开发者 | binsaifullah |
|---|---|
| 更新时间 | 2026年6月1日 17:32 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
"Show me red running shoes under $80" → Queryn automatically filters by color attribute, category, and max price. "Organic coffee beans above $20" → Queryn finds the right category and sets a minimum price filter. "Hello World" → Queryn finds your blog post titled Hello World alongside any matching products — normal search is never broken.Search Scope — Products, Posts, and Pages Together Queryn is smart about when to restrict results to products and when to search broadly:
WP_Query:
product_cat taxonomyproduct_tag taxonomypa_* attribute taxonomies (color, size, material, etc.)No. Queryn is designed to work alongside standard WordPress search without disrupting it. For keyword-only searches, results are returned across all post types you select in the Search Scope settings (posts, pages, and products by default). Only when a query contains product-specific filters (price, category, attributes, etc.) does Queryn restrict results to WooCommerce products. If no AI provider is configured or a call fails, WordPress falls back to its default search behaviour automatically.
This was a known issue in version 1.0.0, fixed in 1.1.0. Earlier versions always restricted search results to WooCommerce products. After updating, keyword-only searches will include posts, pages, and any other post types you enable in Settings → Queryn → General → Search Scope.
Yes. You need an active API key from at least one of the supported AI providers — OpenAI, Google AI Studio (for Gemini), or Anthropic. All three offer free tiers or trial credits to get started.
Queryn only makes an API call on search pages, and only when a shopper performs a search. Responses are cached for one hour per unique query using WordPress transients, so repeated searches hit your database rather than the AI API.
Yes. Queryn hooks into pre_get_posts and modifies WP_Query before any theme renders the results. It is fully compatible with all standard WooCommerce-aware themes including Storefront, Astra, GeneratePress, Flatsome, and block-based themes.
Only your store's taxonomy structure (category names, tag names, attribute names and values, and public custom field keys) alongside the shopper's search query. No customer accounts, email addresses, order data, or personally identifiable information is ever sent.
Only one provider handles search queries at a time. However, you can pre-configure API keys for all three providers and switch the active one instantly from Settings → Queryn → General.
Yes. In Settings → Queryn → General → Apply AI Search On, switch from "All search pages" to "WooCommerce pages only". When this option is active, the AI is only called when a search originates from a WooCommerce page (shop, product category, product tag). Searches from blog pages, static pages, or other non-WooCommerce areas skip the AI entirely and use standard WordPress search — so you are only charged for queries that are actually product-relevant.
Yes. In Settings → Queryn → General, the Search Scope section lists all public post types registered on your site. Check the ones you want included in keyword-only searches. WooCommerce products are always included. Filter-based searches (price, category, etc.) always return products only, regardless of this setting.
This was a bug in 1.0.0, fixed in 1.1.0. The AI now correctly maps "price is X" / "costs X" / "priced at X" to an exact price filter, and the underlying query uses a direct equality comparison rather than a range. Update to 1.1.0 and the search will work correctly.
Queryn reads taxonomy names in whatever language they are stored in your database. If you use WPML or Polylang and your category/tag names are translated, the AI will receive the translated names for the current language context.
Queryn\ namespace.