| 开发者 |
queryra
aisearch |
|---|---|
| 更新时间 | 2026年6月2日 11:46 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
_elementor_data, including
text widgets, headings, and product descriptions built with Elementorbook_genre, material, property_type, or any public
custom taxonomy is sent to the AI search index, keyed by slugqueryra_indexable_meta_contentqueryra/semantic-search as a discoverable
ability. AI agents, chatbots, and assistants running on WordPress 7.0 can call
Queryra natively for semantic product search.public => trueYes. AI Search includes a native B2BKing integration starting in version 1.4.1. The bulk order form's keyword search is replaced with semantic AI product search — B2B buyers can search "warm winter jackets bulk", "cotton shirts wholesale under bulk pricing", or "high-volume keyrings" and find relevant products by meaning, not just exact keywords. All B2BKing visibility rules (B2B groups, category restrictions, per-product permissions) are fully respected. AI Search works equally well for B2C and B2B WooCommerce stores.
Yes — this is one of AI Search's signature capabilities. Customer queries like "wireless headphones under $80, not Beats" automatically apply the price filter AND exclude the brand. Most semantic search plugins only match meaning by vector similarity; AI Search adds LLM-based intent parsing on top. It understands price ranges ("under $50", "between $100 and $200"), brand exclusions ("not Apple", "without Beats"), attribute requirements ("blue cotton breathable"), and use-case contexts ("for hiking", "gift for mom"). This makes AI Search closer to ChatGPT-style search than to traditional keyword or vector-only search plugins. Learn more →
Vector search alone matches concepts by mathematical similarity, but it ignores customer intent — it can find products related to "wireless headphones", but doesn't understand "under $80" or "not Beats" as filters. AI Search combines vector search with LLM-based intent extraction. It knows that "under $80" is a price filter, "not Beats" is a brand exclusion, and "for working out" is a use-case context. The result: AI Search returns products customers actually wanted, not just lexically related ones. Pure vector search plugins (Pinecone-based, ChromaDB-only) miss these intent signals — AI Search parses them automatically.
Yes. AI Search runs alongside existing search plugins during testing — switch between them via Settings → Queryra → Enable AI Search. There's no data migration needed; AI Search builds its own semantic index from your WooCommerce products and WordPress content directly. Most stores migrate in under 10 minutes: install, one-click product import, enable AI Search. If the results aren't right for you, switch back instantly. Many stores keep their old search plugin as fallback while testing.
Yes. AI Search uses your theme's existing search results template — no HTML or CSS changes needed. AI search results render through your theme's standard search.php / archive-product.php template, so they automatically match your store's design. For deeper customization, use developer filters documented at queryra.com/docs/queryra-developer-filters — including custom result ordering, indexable meta content, and search query rewriting. Most themes work out of the box; advanced themes can override individual template parts.
Yes. Queryra registers as a native WordPress 7.0 AI search connector. After activation on WordPress 7.0 or newer, Queryra appears in Settings → Connectors alongside the default AI providers (OpenAI, Anthropic, Google). You can manage your Queryra API key from the standard Connectors screen instead of (or in addition to) the Queryra settings page.
Yes. Queryra registers the queryra/semantic-search ability via the Abilities API. AI agents, chatbots, and other plugins running on WordPress 7.0 can discover and invoke Queryra's semantic search programmatically — natural-language search results are returned as a discoverable WordPress ability with input and output schemas.
Yes. Queryra fully supports WordPress 5.8 through 7.0+. The Connectors API and Abilities API integration activates automatically on WordPress 7.0 sites; on older versions, Queryra continues to work through its own settings page (Queryra → Settings) with no feature loss for end users.
OpenAI, Anthropic, and Google are LLM providers — they generate text and images from prompts. Queryra is a search engine connector. Where LLM connectors create new content, Queryra finds existing content in your site by semantic meaning. They complement each other: an LLM connector can write a product description, then Queryra makes it findable. You can use Queryra alongside LLM connectors in WordPress 7.0 Settings → Connectors.
Yes. Queryra indexes posts, pages, custom post types, and WooCommerce products. The plugin name mentions WooCommerce because that is the most common use case, but Queryra is a full WordPress AI search connector — well-suited for blogs, knowledge bases, documentation sites, news sites, and any WordPress content type.
AI Search is a semantic search plugin that replaces the default WooCommerce product search with AI-powered search. Instead of matching exact keywords, AI Search understands what customers mean — so "gift for mom who loves candles" finds candles, not zero results.
Default WooCommerce search matches exact words only. AI Search uses semantic search to understand customer intent. A query like "my skin looks tired" returns night creams and recovery oils — products that match the meaning, not the words.
Yes. AI Search indexes WooCommerce product titles, descriptions, SKUs, categories, tags, and attributes. It supports product variations, virtual products, and any WooCommerce-compatible theme.
Yes. Customers can search using natural language — "something warm for winter", "gift for dad who likes coffee", "wireless headphones not Beats under $80". AI Search extracts intent, price filters, and brand exclusions automatically.
Semantic search understands the meaning behind a query, not just keywords. AI Search converts your products into AI embeddings and matches them against the customer's query using vector similarity — this is how it finds relevant products even when no keywords match.
No. AI Search is powered by Queryra's backend — no OpenAI account, no API key management, no per-request costs. One free API key at queryra.com covers everything.
Yes. AI Search supports 50+ languages out of the box including Polish, German, French, Spanish, Dutch, Japanese, Czech, and more. No configuration needed — customers search in their native language and find products automatically.
No. AI Search processes queries via an optimized API. Products are indexed in the background. Search results typically return in under a second — competitive with keyword search for most stores.
Install and activate the plugin, follow the Setup Wizard, get a free API key at queryra.com/signup, and run a one-click product import. AI Search is ready in under 5 minutes. No coding required.
AI Search falls back automatically to WordPress default search so customers always see something. You can also use Search Analytics to identify zero-result queries and fix gaps in your product catalog.
Yes. Product variations are fully indexed including variation-specific SKUs, prices, and attributes. AI Search handles simple products, variable products, and virtual products.
Yes. AI Search includes Boost Controls — you can promote specific products or categories to appear higher in results. Useful for high-margin products or seasonal inventory.
Yes. AI Search automatically extracts content from Elementor (_elementor_data),
Breakdance, Beaver Builder, and Oxygen (both legacy shortcodes and JSON v2). No
configuration needed — page builder content is indexed the same way as standard
post content.
Yes. AI Search reads ACF (Free + Pro) text, textarea, WYSIWYG, repeater, and
group fields automatically. Meta Box text and group fields are also supported.
For Pods, JetEngine, and Bricks Builder, use the developer filter
queryra_indexable_meta_content to specify which fields to index.
Yes. Queryra sends all public custom taxonomies (e.g. book_genre, material,
property_type) to the AI search index in a taxonomies field, keyed by slug.
Categories, tags, and the WooCommerce brand taxonomy continue to work as before.
pre-init flags fresh installs in logs for easier diagnostics.rel="noreferrer" with rel="noopener" on admin links so AI search referrer attribution works server-side while keeping security best practices intact.wp_json_encode() for safe output escaping.auto_awesome (same icon library B2BKing already uses).queryra_validate_api_key for external API key validation. Returns true on success, WP_Error on failure.queryra_indexable_meta_content for Pods, JetEngine, and Bricks Builder integrationqueryra_indexable_taxonomies to control which custom taxonomies are sent to AI search