內容簡介
StoreBolt 是一款專為 WooCommerce 設計的進階搜尋外掛，透過專用的 FULLTEXT 索引表，提供即時且準確的產品搜尋體驗，讓顧客能快速找到可購買的商品，提升購物效率。
【主要功能】
• 支援 SKU、變體、品牌等多種搜尋條件
• 即時顯示搜尋結果，並高亮顯示關鍵字
• 提供最近搜尋與熱門搜尋功能
• 可自訂搜尋結果的顯示方式
• 無需 JavaScript 即可運作，兼容性佳
外掛標籤
開發者團隊
② 後台搜尋「StoreBolt – Advanced Search for WooCommerce」→ 直接安裝（推薦）
原文外掛簡介
WooCommerce search runs through WordPress’s post search, which looks at titles and descriptions and has never heard of a SKU, a variation or a brand. This plugin replaces it with a dedicated, FULLTEXT-indexed table built for products, so a shopper gets a ranked dropdown of real purchasable items from the second character, instead of a page reload.
Everything below runs on your own server, on plain MySQL, and is free.
Search that knows what a product is
Variations are first-class. Each variation is its own indexed row with its own SKU, price, attributes and stock status, inheriting the parent’s title and taxonomies. A search for a variation’s SKU opens that variation, not its parent.
SKUs, categories, brands and tags are searched alongside titles and descriptions. There is a weight slider for each field, so you decide what “relevant” means in your catalogue.
Out-of-stock handling follows WooCommerce’s own setting: show, hide, or push to the bottom.
A dedicated index, never a live query. Searches never join posts and postmeta at request time, which is what keeps a large catalogue fast.
A dropdown shoppers recognise
Instant results as they type, with the searched words highlighted.
Recent searches: the shopper’s own, kept in their browser and never sent anywhere.
Trending searches: what your shoppers actually search for, plus terms you promote yourself.
Category and brand suggestions, linked to their archives.
Query completions: searches other shoppers ran and got results for.
Recent and trending laid out as a list or as pills, your choice under Suggestions. Pills fit more terms above the fold and show each recent search’s product picture.
An optional category dropdown in the search box, and a takeover of the WooCommerce search results page so the ranked results survive the page load.
Works without JavaScript: the box is a real product-search form first, enhanced second.
Placed and styled however you build pages
A block (StoreBolt Product Search) with the full colour / typography / border / layout surface WooCommerce’s own Product Search block has, a shortcode ([maswcas_search]), and a classic widget.
The dropdown itself is an editable template part built from blocks: re-order it, remove the price, or ship your own layout from a theme.
Theme search enhancement, on out of the box: the instant dropdown attaches to the search box your theme already renders, with no block placement at all. If your theme ships a live search of its own, turn one of the two off. Settings → Theme search has the switch, and names the theme when it recognises one.
Merchandising you control
Product boosts: choose products to promote for particular searches. A boosted product is shown at the top of the results for those terms, including terms its own title and description would never match: a campaign name, “gift”, or something you are about to start stocking.
Boosts apply the moment you save (no reindex), and they still obey your catalogue: a product that is hidden, unpublished, or out of stock on a store that hides those is not promoted.
A search dashboard, on every install
A daily rollup (not a log) of what shoppers searched for, what found nothing, and what was searched but never clicked, with one-click hand-offs into a synonym rule or your trending list. Nothing in that table identifies a shopper: no ID, no IP, no timestamp finer than the day.
Optional: StoreBolt hosted search
The plugin is complete on its own. If you want what MySQL structurally cannot do (typo tolerance, synonyms, faceting, and search served off your server), you can connect a paid StoreBolt subscription from the settings screen. Nothing is withheld from the free plugin to sell it, and if the hosted service is ever unreachable, search falls back to your local index automatically.
External services
Out of the box, this plugin makes no external requests. Everything below happens only after a merchant chooses to connect a StoreBolt account, and stops when they disconnect.
StoreBolt (api.storebolt.app) is the service that issues and validates your subscription.
When: when you connect (or paste a license key), and once a day afterwards to keep the subscription status and expiry current.
What is sent: your license key, your site URL, and an environment report covering the site name, WordPress / WooCommerce / PHP / plugin versions, locale, whether the site is multisite, the published product count, and which search engine is currently active. The environment report is filterable (maswcas_vendor_environment); returning an empty array from that filter sends none of it.
Why: to return your store’s search connection, to tell you which stores are on which plan, and so support can tell what a store is running when something breaks.
Your StoreBolt search gateway is the host named in the connection your account returns.
When: only while the hosted engine is the selected engine. “Keep the cache warm between shoppers” adds no destination: those requests go to your own store’s search endpoint, and reach the gateway only where a shopper’s search would have, which is when the answer is not already cached. What it changes is the timing, not the recipient.
What is sent: the shopper’s search terms, and your indexed catalogue documents (product and variation titles, descriptions, SKUs, prices, stock status, visibility, attributes, categories, brands and tags) as they change. Images, permalinks and the prices a shopper is shown are resolved locally and never leave your store. No shopper identity, cookie or IP is attached by the plugin.
Why: to answer searches with typo tolerance and synonyms, which the built-in MySQL engine cannot do.
StoreBolt analytics (api.storebolt.app) is the hosted half of the search dashboard.
When: on a schedule (about every six hours) while connected to a plan that includes it.
What is sent: your licence key, your site’s URL, its timezone and its store currency, together with your existing daily rollup rows. A row is the search term, the day, and the counters, which include the revenue attributed to that term where conversion measurement is on. These are the same rows the dashboard already shows you locally, and no shopper identity is stored in them to send.
Why: so your history survives past the local 90-day retention window and can be read across several of your stores. The licence key identifies the account; the site URL, timezone and currency are what let the dashboard tell your stores apart and report their figures correctly.
Service terms: Terms of Service and Privacy Policy.
Source code and build
Everything that runs on your storefront is shipped as readable source. assets/js/ (the search box, the dropdown blocks, the block-editor script, the theme-search loader and the analytics beacon) is hand-written, commented, and unminified, and so is every PHP file under src/ and templates/. Nothing there is compiled, and nothing is fetched from anywhere at runtime.
One screen is built. The wp-admin settings app is a React application. Its source is the admin-src/ directory of this plugin, and it is compiled to assets/build/index.js, assets/build/index.css and assets/build/index-rtl.css. Both the source and the build configuration ship inside this plugin, so the compiled files can be regenerated and checked against their source without leaving the package:
cd into the plugin directory (wp-content/plugins/storebolt-advanced-search-for-woocommerce).
Run npm install to install the build tools declared in package.json (Node.js 18 or newer).
Run npm run build, which rewrites assets/build/.
The build is @wordpress/scripts 27.9 (the official WordPress webpack and Babel configuration) with Tailwind CSS applied through PostCSS; postcss.config.js is the whole of the CSS configuration. npm start is the same build in watch mode. No build step is needed to install or run the plugin, because the compiled files are shipped.
Third-party libraries included in this plugin
Tailwind CSS 4.3.3 (MIT) is a CSS framework. It is not shipped as a library: it is compiled at build time into assets/build/index.css and assets/build/index-rtl.css, which carry its licence header. Source: https://github.com/tailwindlabs/tailwindcss
automattic/jetpack-autoloader 6.0.0 (GPL-2.0-or-later) is a PHP class autoloader, shipped as readable PHP in vendor/. It lets several plugins that share a library each load the newest copy of it rather than whichever loaded first. Installed with Composer from composer.json. Source: https://github.com/Automattic/jetpack-autoloader
The admin app uses React, wp.apiFetch, wp.element and wp.i18n from WordPress’s own bundled copies (declared in assets/build/index.asset.php); no copy of React, jQuery, Lodash, Moment or any HTTP library is bundled into this plugin.
