Default WordPress search relies on non-indexed LIKE '%term%' database queries that scan entire tables row by row. On large WooCommerce stores or heavy content sites, this causes massive database load and slow response times. Super Speedy Search replaces standard queries with a dedicated local index built on MySQL or MariaDB FULLTEXT search engine technology. Designed specifically for sites with tens or hundreds of thousands of products, SKUs, and variations, it accelerates front-end AJAX dropdowns and back-end wp-admin searches while keeping all data hosted locally.
Key Features & Database Architecture
- MySQL FULLTEXT Indexing: Queries run against optimized FULLTEXT indexes in BOOLEAN mode instead of performing full table scans.
- Local Storage Model: Operates entirely within the WordPress database, avoiding monthly SaaS subscriptions and per-query API limits.
- Short-Token Routing: Queries containing 1- or 2-character tokens (e.g., “M.2” or “Wi-Fi 6”) bypass MySQL FULLTEXT minimum length limits via specialized
LIKEfallback conditions. - 3-Way Punctuation Normalization: Stores boundary-preserving, space-separated, and joined SKU variations to match queries like “T-Shirt”, “tshirt”, or “ABC-123”.
- Bounded Candidate Scoring: Restricts relevance calculations to top FULLTEXT candidate sets (default 5,000 items), preserving server resources during broad queries.
- Recent Items Prioritization: Optionally limits initial search passes to recent post windows before scanning the legacy index.
- WooCommerce HPOS Compatibility: Fully indexes High-Performance Order Storage, including customer meta, line items, and variation SKUs.
Engine Limitations & Trade-offs
- No Automatic Typo Correction: Lacks fuzzy matching or Levenshtein distance calculations; search relies on prefix matching and manually configured synonym tables.
- Local Index Maintenance: The database index must be generated locally and updated via wp-admin controls or WP-CLI.
- Database Version Dependencies: Requires MySQL 8.0+ or MariaDB 10.2.2+ for BOOLEAN mode FULLTEXT support.
- Multilingual Tooling: Supports Polylang, but WPML compatibility remains unverified.
Configuration & Staging Rebuilds
Relevance is controlled via per-post-type weight settings, allowing developers to score product titles higher than body content or taxonomy terms. Index rebuilds execute through temporary staging tables, guaranteeing zero search downtime for front-end shoppers while the replacement database tables compile. Operations can be triggered via admin settings or automating wp sss rebuild routines.
Frequently Asked Questions
Does it require WooCommerce to function?
No. While heavily optimized for WooCommerce product variations and orders, the plugin indexes standard WordPress post types, pages, and custom post types.
Will search stop working during index rebuilds?
No. The indexing process builds new data inside staging tables, keeping the live index operational until swapped.
How are short terms handled if MySQL FULLTEXT ignores them?
Sub-threshold tokens are split out and evaluated using dedicated word-boundary LIKE checks alongside main FULLTEXT terms.
