FindAstra — AI Semantic Search for WooCommerce
| 开发者 |
elyass
freemius |
|---|---|
| 更新时间 | 2026年6月11日 05:21 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
FindAstra replaces WooCommerce's default keyword search with AI search that understands what shoppers mean. A search for "comfortable hiking shoes" finds your "Trail Running Sneakers Cushioned" product even when none of those words appear in the title or description.
Every published product is converted into a vector embedding that captures its semantic meaning. At search time the shopper's query is embedded too, and FindAstra returns the closest matches by cosine similarity.
The search engine
This plugin runs the Local engine: embeddings are generated in the shopper's browser with transformers.js (
Xenova/bge-small-en-v1.5). No API keys, no signup, no monthly cost. The ~33 MB model is downloaded once and cached. There is no product limit — index your whole catalog.
Pro engines (optional)
FindAstra Pro — a separate, paid version available from findastra.com — adds two server-side engines, useful for very large catalogs where browser-side indexing becomes impractical:
- OpenAI —
text-embedding-3-small, server-side. Bring your own API key (~$2/year for an average store). - Hugging Face —
BAAI/bge-small-en-v1.5, orBAAI/bge-m3for multilingual catalogs (100+ languages). Bring your own token (free tier ~30k requests/month).
- Live autocomplete dropdown that auto-attaches to the theme's existing search bar.
- Semantic results page — WooCommerce's product archive template renders proper product cards with the semantic ranking.
- Fallback products when no match scores above the relevance gate, so shoppers never see an empty results page.
- One-click setup under WooCommerce → FindAstra.
- Encrypted credential storage — API keys never sit in plain text.
- Match-quality gating so weak queries gracefully trigger the fallback instead of returning low-relevance noise.
[findastra]shortcode + classic sidebar widget + Gutenberg block.findastra/v1/*REST namespace.- Filter hooks for source text, gating thresholds, fallback notice text, and the free/paid capability matrix.
安装:
- Upload the FindAstra plugin folder to
/wp-content/plugins/, or install it via the WordPress Plugins screen. - Activate the plugin.
- Go to WooCommerce → FindAstra.
- Pick an engine. Local works without any account or key.
- Click "Index now" to build the search index.
- Open your storefront and search. Autocomplete and the results page wire automatically.
屏幕截图:
常见问题:
Do I need an OpenAI key to use this?
No. The default engine is Local — it runs entirely in your shoppers' browsers via transformers.js. Zero keys, zero accounts, $0 forever. The Hugging Face and OpenAI tiers are optional upgrades for stores that want server-side quality.
Will this slow down my store?
No. AI scoring runs inside your existing database and adds about 20–30 milliseconds to a typical search. Indexing is asynchronous and chunked, so it never blocks admin. The Local tier offloads work to the shopper's browser entirely.
Does it work with WPML or Polylang?
Multilingual indexing is part of FindAstra Pro. With Pro, FindAstra detects each translated product's language at index time and writes one embedding row per (product_id, language) pair, and searches are scoped to the current request language.
What about large catalogs?
FindAstra automatically switches to a hybrid retrieval mode (FULLTEXT prefilter + cosine re-rank on the top candidates) for stores with more than 5,000 indexed products.
Where are my API keys stored?
Encrypted at rest using AES-256-CBC with a site-specific key derived from wp_salt('auth'). Keys are only decrypted at the moment of use.
Does the Local engine download anything?
Yes — once. The first time the Local engine runs, it downloads a roughly 33 MB AI model from the Hugging Face model hub (huggingface.co), which your browser then caches. Only the model files are fetched; no store, product, or shopper data is ever sent. After that, all embedding and search runs entirely in the browser. (The Hugging Face and OpenAI engines instead call their respective APIs using the keys you provide.)
更新日志:
0.11.7
- The in-browser Local engine now loads its runtime entirely from the plugin — no external CDN fallback of any kind.
- Internal naming and packaging cleanup.
- The free version is fully functional with no product limit — index your whole catalog with the Local engine.
- The OpenAI and Hugging Face server-side engines, WPML/Polylang multilingual indexing, and search analytics are part of FindAstra Pro.
- Documented the external services each engine can contact (the in-browser model download and the optional Pro APIs).
- Background indexing for the OpenAI and Hugging Face engines: click "Index now" and you can close the tab — indexing keeps running on the server and resumes if interrupted. Ideal for large catalogs. (The Local engine still indexes in your browser.)
- Faster indexing: larger embedding batches mean far fewer API calls, so big stores finish in a fraction of the time.
- Clearer Match-quality gates: the settings now show the real defaults for your selected engine and note that they are advanced — most stores never need to change them.
- Fixed: with the OpenAI engine selected, almost every search showed "No exact matches — here are some popular products" instead of real results. OpenAI's relevance threshold was tuned for a different model; it now uses correctly calibrated values. (Local and Hugging Face were not affected.)
- Search relevance is now self-calibrating across all three engines: results are shown when a product clearly stands out from the rest, so genuine matches surface even when a store's catalog scores differently from the built-in defaults. Gibberish still falls back to popular products, and your manual Match-quality gates still take precedence when set.
- WordPress.org Plugin Check pass: documented the intentional direct/uncached queries against the plugin's own custom tables, suppressed the no-nonce notice on the public product-search request (input is sanitized and the token is signature-validated), and annotated the third-party WPML filter hooks.
- Aligned the readme title with the plugin header name to clear the Plugin Check name-mismatch notice.
- WordPress.org compliance pass (Plugin Check clean): added translator comments, hardened output escaping on the analytics counters, and documented the intentional schema-change and asset-streaming database/file calls.
- FAQ: documented the Local engine's one-time on-device model download.
- Compatibility: tested up to WordPress 7.0.
- Refreshed plugin brand: new mark on the FindAstra admin hero, official compact icon on the WP sidebar menu entry.
- Plugin metadata cleanup ahead of WordPress.org submission: Plugin URI + Author URI now point at findastra.com.
- Freemius integration: free + Pro/Agency/Unlimited tiers, license activation, automatic updates.
- New
FindAstra_Licenseclass centralises the free/paid capability matrix. - Free version ships the Local engine; Pro adds the OpenAI and Hugging Face engines.
- Kill the WooCommerce single-result redirect on hijacked searches so the ranked product cards aren't replaced by a teleport to one item.
- Language-aware shop-page fallback.
- Shop search page falls back to popular products on no-match so shoppers never see a dead-end results page.
- Per-model default match-quality gates (fixes HF + bge-m3 "no results" on multilingual queries).
- Fix indexer infinite loop on Polylang/WPML sites with untagged products.
- WPML + Polylang multilingual support — per-language embedding rows.
- Theme matrix expanded (Astra, Kadence, Blocksy verified working).
- Hugging Face provider gains
BAAI/bge-m3(multilingual, 1024d) as a settings-driven alternative to bge-small.
- Rebrand from SearchSense to FindAstra.