Searchie vs Super Speedy Search
Want faster results? Try Super Speedy Search on your store.
Get Super Speedy Search →Comparing Searchie with Super Speedy Search? This page breaks down the key differences and similarities so you can find the best fit for your WordPress or WooCommerce store.
Overview of Searchie
Searchie is a search and content discovery platform focused on making video, audio, and written content fully searchable, primarily for membership site owners and content creators. It positions itself as a solution for finding moments within media content rather than as a traditional database-driven product search engine for e-commerce.
How Super Speedy Search differs from Searchie
All plugins from Super Speedy Plugins share a SQL-first architecture and an uncompromising focus on performance — and Super Speedy Search is no different. Here is what sets it apart:
Shoppers leave when search is slow, irrelevant or cannot find the words they use. Super Speedy Search replaces WordPress’s table-scanning search with a dedicated index, then lets you control what matches and what ranks first.
How to choose between Searchie and Super Speedy Search?
While Searchie serves a specific niche around media content discovery, stores with large product catalogues have different requirements. Super Speedy Search is built specifically for WooCommerce and WordPress, with a SQL-first architecture that queries your own database directly — no external service, no data sync, no latency introduced by a third-party API. Tested against one-million-product catalogues before every release, it handles the search demands of high-volume e-commerce stores. Try the free trial on your staging site to see the difference.
What do others say about Super Speedy Search?
Awesome support and a great product – I had trouble using the product and Dave went out of his way to help and to get it working for me. Highly recommended – great plugin for search. Thank you
Game changing plugin with fantastic and responsive support. Our operation is currently small in scope when compared to other sites powered by Super Speed Search, however, we now have the confidence that we can continue to grow our catalog without destroying Woo's performance.
I already use a couple of products from Dave so when I need a good search plugin for a busy ecom website I didn't need to look any further. I am not as techy as some of the people here, but I had that search up and running in minutes. It works really well, its fast and it does everything you would want (& more) from a search plugin. Excellent – thank you
Super Speedy Search Knowledge Base
View full Knowledge Base →- Analytics & Caching: Track Searches and Cache Hot Results
- Faster wp-admin meta search
- Multi-search: Prioritise Recent Content for Faster Searches
- Restricting a search box to one category
- Searching multiple post types in full-page search results: Single ranked list vs Mixed sections
- Smart Variation Search
- Taxonomy combination suggestions
- Taxonomy Search
- Adjusting Super Speedy Search Weights
- Ajax Search Panel – Super Speedy Search Settings
- Getting Maximum Speed from Super Speedy Search
- How to add the Super Speedy Search widget into your header
- Installing and configuring Super Speedy Search
- Main Super Speedy Search Settings
- MariaDB "DOUBLE value is out of range" after a rebuild
- Meta Search – Super Speedy Search Settings
Articles about Super Speedy Search
View all articles →- Bug fix sprint
- December Development Update
- Manual update for Super Speedy Search required
- More speed, more updates, and a bit of a roadmap for our plugins
- More beta updates available
- Beta downloads and historic plugin versions now in your account
- Upgrades to multiple Super Speedy Plugins plugins now in beta
- Dev Diary #7
- Dev Diary #2
- Update to Super Speedy Search released
What's new in Super Speedy Search?
5.57.1 (22nd July 2026)
- Fixed a complete rebuild not recording the schema version on the common path where the suggestions table already exists and a forced suggestions rebuild is off. That path returned early, before the finalising step that writes the recorded version and flushes the object cache, so a rebuild could report success yet leave the version stale — and the query layer, which trusts that version, kept assuming an older schema. An `all` rebuild now always finalises, whichever path it takes.
5.57.0 (21st July 2026)
- Added an MCP / AI-agent surface. Eleven abilities under the `sss` namespace let an AI assistant read and tune your search configuration through the WordPress Abilities API (WordPress 6.9+), over the standard REST endpoints with an Application Password. No extra plugin is needed on the site.
- Added `sss/test-query`, the ability the rest depend on: it runs a real front-end search and returns the ranked results together with the score breakdown for each one, so an assistant can see which column earned each result its position instead of guessing.
- Added read abilities: `describe-search-config` (the full weight, column, synonym and combination vocabulary as data, including a plain statement that there is no fuzzy typo matching), `get-index-status`, `get-weights`, `list-synonyms` and `get-combination-settings`.
- Added write abilities: `set-weights`, `upsert-synonyms`, `delete-synonym`, `set-combination-settings` and `rebuild-index`. Unknown weight keys are rejected with the list of valid ones rather than silently written.
- `rebuild-index` rebuilds a batch at a time against a cursor, so a large catalogue can be rebuilt over HTTP without hitting a timeout. It refuses to resume if the settings changed mid-rebuild.
- Added the `sss_manage_search` capability and a "Search Manager" role, so the account an AI agent uses needn't be a site administrator. Existing administrators get the capability automatically.
- Added a stdio MCP bridge (`tools/sss-abilities-mcp-bridge.mjs`) for connecting Claude Code, Claude Desktop or any other MCP client to a site.
- The Search Manager role is now created on plugin activation and under WP-CLI, so `wp user create <name> –role=sss_search_manager` works without first loading a wp-admin page.
- Fixed "WordPress database error Unknown column 'language'" on every keystroke for sites whose suggestions table predates 5.44. The suggestions query decided whether that column existed by reading the schema version hard-coded in the plugin file rather than the one recorded in the database, so the check was true in every release since 5.44 and the query always referenced the column. It now reads the recorded version, and an install still on the older schema simply serves suggestions unfiltered by language instead of erroring.
- Fixed a rebuild reporting success while leaving the suggestions table on an old schema. The table structure is now created and migrated by every rebuild scope, including when post-title suggestions are switched off — that is cheap DDL only, so rebuilds with suggestions disabled stay just as fast, and the expensive token build is still skipped.
- The recorded schema version is now written once, as the final step of a complete rebuild, instead of by the search stage. It used to advance on rebuilds that never touched the suggestions tables, so it could claim a structure the database did not have.
- Fixed the rebuild's option writes being invisible to a persistent object cache (Redis, Memcached) when run from the admin Rebuild button or the schedule. Those writes go straight to the database, so the cached values survived them; only the WP-CLI rebuild cleared the cache afterwards. All three paths now finish the same way.
- Fixed the `?showweights=1` debug breakdown not adding up to the total relevance score. The excerpt, taxonomy and meta-value contributions were being multiplied by their weight factor twice, and the base fulltext score was not shown at all. The displayed contributions now sum to the score they explain.
- Fixed a SQL error that broke search entirely when `?showweights=1` was on and every search term was consumed by a synonym group.
Want faster results? Try Super Speedy Search on your store.
Get Super Speedy Search →
Comments