| 开发者 | muhammadnan |
|---|---|
| 更新时间 | 2026年7月29日 17:33 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
LIKE query against your posts table. It is slow on large sites, it ranks results by date rather than relevance, and it finds nothing at all if a visitor misspells a word.
SearchWright hands that job to Typesense, an open source search engine you either self-host or rent. Your content is indexed there; searches are answered from memory in a few milliseconds and tolerate typos.
What it does
No. Typesense is open source and runs on a small server perfectly well. Typesense Cloud is a convenience, not a requirement.
The search results page falls back to the ordinary WordPress query, so visitors still get results, just slower and less relevant ones. The instant dropdown reports that search is unavailable and does nothing else.
No. The browser talks to a REST endpoint on your own site, which talks to Typesense server-side. The key stays on the server.
The dropdown attaches to any input matching the CSS selector on the Search tab, which defaults to standard search fields. If your theme uses something unusual, put its selector in that box.
Products appear in results because they are a public post type. Sorting and filtering by price, stock, attributes or variations needs the separate WooCommerce add-on described on the WooCommerce tab.
Indexing runs in batches from the browser, so site size is limited by your Typesense server rather than by PHP timeouts. Sites with hundreds of thousands of posts are well within Typesense's range.
Each site in a network keeps its own settings and its own collection. Point them at different collection names on the Connection tab.