Search · Filters · Feeds for WooCommerce

Tired of slow WooCommerce search?

Slow search, filters that take seconds, an index that never finishes, a feed that runs out of memory. Searchmaker serves all of it from a local index instead of database queries, on ordinary hosting, for shops with 10,000 or more products.

30DAYMONEY-BACKGUARANTEE30-day money-back guaranteeFull refund for any reason. How it works.
  • License works offline, no license server
  • WordPress 6.5+ · WooCommerce 8+ · PHP 8.1+

Sound familiar?

Six things WooCommerce owners keep running into.

Each one has a plain cause. Each one has an answer below.

  • Live search lags behind your typing

    People write: “ajax search slow on a large catalog”

    Many live searches run through WordPress itself, then ask the database to match text.

    See the answer
  • Filters and category pages crawl

    People write: “slow performance with a lot of products and filters”

    Every click joins several database tables, and variations multiply the rows.

    See the answer
  • Search misses SKUs and variation SKUs

    People write: “no results when I search a variation SKU”

    Core search matches titles and text. Variations are separate posts it skips.

    See the answer
  • Zero results, typos, the wrong word

    People write: “the results do not match”

    Exact text matching: no typo tolerance and no synonyms.

    See the answer
  • Index builds hang or run out of memory

    People write: “hangs while building index”

    Indexing runs inside web requests or WP-Cron, and the host caps time and memory.

    See the answer
  • Feeds run out of memory, variants get disapproved

    People write: “feed exceeds memory limit”

    The feed is built from live database queries, and variations multiply the items.

    See the answer

Phrases are short wordings from public support threads and issue reports (WordPress.org, WooCommerce GitHub, plugin vendors’ own help pages). They show the problems exist, not how often they happen.

Slow live search

Answer from a local index, not through WordPress.

Searchmaker’s search endpoint does not load WordPress, your theme or your plugins. It reads a compact index file and returns the matching products.

One real store, 6,500 products

On a slow store we tested, the theme’s built-in live search (a WordPress admin-ajax request) took about 1.4 seconds per search, round trip, on average. The same queries through WordPress’s REST path took 0.45 to 0.55 seconds. Searchmaker’s engine answered in single-digit milliseconds.

Different layers: a browser round trip against engine time, so we do not turn them into a ratio. One store, our own test, no comparison with any plugin.

A typical WooCommerce search request

  1. Browsertypes a letter
  2. Web serverPHP-FPM
  3. WordPress bootstheme + plugins
  4. WP_Querymeta + term joins
  5. MySQLscans and sorts
  6. Render + replyHTML or REST JSON

The same request through Searchmaker

  1. Browsertypes a letter
  2. Web serverPHP-FPM
  3. query.phpno WordPress loaded
  4. BitmapsAND / OR in memory
  5. JSON replyids + cards
Illustrative: shows the work done per request, not timings. Measured numbers are on the benchmarks page.

Filters and category pages

A filter click is bit math, not a table join.

Searchmaker keeps every category, brand and “in stock” as a row of bits, one bit per product. Picking filters combines those rows, and the same result gives the live counts next to each option. No new database query per click.

  • OR within a filter group, AND across groups.
  • Filter pages are noindex with a canonical, so combinations do not pile up in Google.
  • Limits: global attributes only, the top 24 options per group by default, and variation-level filters are approximated from the parent product’s terms.

Category AND (Brand A OR Brand B) AND In stock

Engine level · synthetic catalog

Measured engine time on 100,000 products with 165,264 variations. No web server, no WordPress, no concurrency: this is not a page-load time. The grey bar is a naive full scan in PHP, for scale.

Category + in stock
0.49 ms
Category + brand + 2 facets + stock
0.39 ms
Multiselect (OR within, AND across groups)
0.42 ms
Price range + category + stock
0.47 ms
Search + filters + first 24 product cards
0.64 ms
Counts for five facet groups
4.42 ms
Naive full scan in PHP (baseline)
53.6 ms

Logarithmic scale · shorter is faster

PHP 8.3, 128 MB, shared-style host. A real-store category-page load time, before and after, is not measured yet. Method and limits.

SKUs, typos, synonyms

Find the part number. Forgive the typo. Know the word.

Variation SKUs lead to their parent product. Exact SKUs rank first, then words, prefixes, compound words and typos. Synonym packs cover words shoppers use that your titles do not.

Try it: break it on purpose.

A miniature of the plugin's matching, running in your browser on 36 demo products (the first six have SKUs). Flip synonyms off to see what a plain search would have shown.

try:
northfield-tools.example

Start typing, or pick an example.

Not measured yet: matching text from the middle of a code with no separator (8x40 inside M8x40-A2) and a zero-result rate on a real shop. Test your own part numbers within the 30-day guarantee.

Synonym packs: 6,653 pairs in 5 languages, open data (CC BY 4.0)

Only words that exist in your catalog are ever used. Packs not yet reviewed by native speakers are marked as generated. Open source

fi

Finnish model-reviewed

1,333 pairs · 4 packs

en

English generated

1,503 pairs · 4 packs

sv

Swedish generated

757 pairs · 4 packs

de

German generated

1,886 pairs · 4 packs

et

Estonian generated

1,174 pairs · 4 packs

da

Danish

planned

nb

Norwegian

planned

fr

French

planned

es

Spanish

planned

nl

Dutch

planned

pl

Polish

planned

it

Italian

planned

Index builds and memory

Builds in chunks, aside, and switched in only when valid.

  • Written in small chunks, so memory stays flat. No product arrays are held in PHP at query time.
  • The new version is built next to the live one, checksummed, then switched in atomically. A failed build never touches live search, and rollback is one click.
  • Runs from WP-CLI or as a queued background rebuild. Price and stock changes patch the index instead of rebuilding it.
  • If the index is missing or unhealthy, shoppers get normal WooCommerce results instead of a blank page.
measured

6.1s

Full index build

100,000 products, 165,264 variations.

measured

57MB

Peak memory during the build

PHP 8.3, 128 MB limit, shared-style host.

Synthetic catalog. Later runs of the current index format were slower and used more memory; those figures are on the benchmarks page. Not verified: a build from a real 100,000-product WooCommerce database, and a WP-Cron rebuild on a weak shared host. We do not promise it never fails.

Google Merchant feeds

One variable product in, one item per variation out.

The feed is a static XML file written from the index, one card at a time, so memory stays flat. Visitors and Google only ever download the file. Requests never trigger generation.

In WooCommerce

Trail Jacket1 variable product · SKU TJ-100Colour: Blue, Red · Size: M, L

In the Google Merchant file

  • Trail Jacket - Blue, Mg:id TJ-100-BLU-Mg:item_group_id TJ-100129.00 EUR · in_stock
  • Trail Jacket - Blue, Lg:id TJ-100-BLU-Lg:item_group_id TJ-100129.00 EUR · in_stock
  • Trail Jacket - Red, Mg:id TJ-100-RED-Mg:item_group_id TJ-100119.00 EUR · out_of_stock
  • Trail Jacket - Red, Lg:id TJ-100-RED-Lg:item_group_id TJ-100119.00 EUR · in_stock
Illustration with made-up data. Rules: own price, stock and image per variation; the link preselects the variation; limit of 500 variations per product; Google Merchant only.
measured

3.1s

Feed, parent-only, 100,000 items

about 32,000 items per second, 43 MB of XML, flat memory (engine writer reading the index, PHP 8.3 CLI)

measured

6.4s

Feed, one item per variation, 239,692 items

about 37,000 items per second, 129 MB of XML; 100,000 parents with 159,758 variations, flat memory

Engine writer reading the index, synthetic 100,000 products, Intel i9 Windows machine, PHP 8.3 CLI, memory_limit 128M. Not measured: a feed on a slow shared host. The index build still reads WooCommerce. Feeds refresh on a schedule or after a rebuild, so prices are those at generation time. Google Merchant only. Compared with CTX Feed

What slowness costs

What outside studies say about speed and search.

Three studies, each with who ran it, who paid, and what it cannot tell you.

Agencies 55 and Deloitte · 2020 (2019 data)

A tenth of a second on mobile

Across 37 brand sites, a 0.1 second improvement in four mobile speed measures went together with 8.4% higher conversion on retail sites.

Funded by
Commissioned by Google.
Caveat
Observational, mobile only, and each of the four speed measures improved on every page of the journey. It is about page loading, not search.

web.dev: Milliseconds make millions

Google (Jake Brutlag) · 2009

Slower search results, fewer searches

When Google added 100 to 400 milliseconds to its search results in a controlled test, people searched a little less (0.2% to 0.6% fewer searches per user), and some of the drop stayed after the delay was removed.

Funded by
Run by Google on its own search engine.
Caveat
Google web search in 2009, not a shop. It measures how many searches people made, not sales.

Google: Speed matters for web search (PDF)

Baymard Institute · 2024, updated 2026

Most shop search is only so-so

Baymard rated the search of 170+ e-commerce sites and apps and found 56% do not adequately support what shoppers try to search for. In a separate benchmark of 344 sites, 68% show a no-results page that is a dead end.

Funded by
Baymard sells research and audits.
Caveat
A user-experience quality score of leading sites, not lost sales, and not WooCommerce shops in particular. The two figures come from different benchmark rounds.

Baymard: search query types Baymard: no results page

These studies do not show that Searchmaker raises conversion or revenue. None of them tested our product, and page-speed results do not automatically carry over to search latency. All eight studies, methods and limits

Your theme, your hosting

Fits the way you build, with the limits stated.

Works with

  • Classic and block themes. Verified on a block theme, a classic theme and Salient with WPBakery.
  • Page builders through shortcodes and blocks.
  • WPML and Polylang: one index per language.
  • Variable products and variation SKUs.

Be aware

  • TranslatePress is not supported yet.
  • Elementor and WPBakery grids are not replaced. Use the catalog shortcode there.
  • Theme presets are unverified suggestions. Check the search box on your own site.
  • Early access: we answer every message personally.

Hosting needs

  • WordPress 6.5+, WooCommerce 8+, PHP 8.1+ with sodium.
  • No Redis, no daemon, no shell access, no extra database.
  • Security plugins must allow the runtime file, and caching plugins should skip it.

Point Searchmaker at your theme’s search input with one CSS selector. Shoppers get instant results with thumbnails, price, SKU, category and brand suggestions and an optional details panel. No template edits.

your-shop.example
Instant search dropdown with thumbnails, prices and a details panel

Pricing

One license per site, whatever the catalog size.

Annual licenses, offline keys, 30-day money-back guarantee. Prices exclude VAT.

Each yearly license is valid for 1 year. Keys work offline (no license server, no phone-home) and are tied to the domains you list. 30-day money-back guarantee. Sold to businesses only; prices exclude VAT. Prices exclude VAT.

Secure payment by Stripe

  • Credit and debit cards
  • Apple Pay
  • Google Pay

Card details go to Stripe and never touch our server. Apple Pay and Google Pay appear where your device supports them.

Powered by Stripe

Questions

Straight answers.

Something missing? Ask us. We would rather answer than guess. Weighing us against SearchWP or FiboSearch? Compare them fact by fact.

Can shoppers search by SKU, including variation SKUs and part of a SKU?

Yes, with limits. A query that is exactly a SKU or model number is matched first. Variation SKUs are searchable and lead to the parent product. A SKU is also indexed in its parts, split at hyphens and underscores, so a search for m18 finds m18-imuri, and the first letters of a word work as a prefix. What we have not measured: matching text from the middle of a code that has no separator, such as 8x40 inside M8x40-A2, on a real catalog. Check your own part numbers in the first 30 days; the money-back guarantee covers it.

Does the index build run out of memory or time out on a big catalog?

The builder works in chunks and writes a new index version next to the live one. It is checked, then switched in with one atomic step, so a failed build never touches the live index and you can roll back. It also runs from WP-CLI and as a queued background rebuild. Measured: a synthetic catalog of 100,000 products with 165,264 variations built in about 6.1 s with a peak of about 57 MB (PHP 8.3, 128 MB, shared-style host). Not verified: a build from a real 100,000-product MariaDB WooCommerce database, and a rebuild driven by WP-Cron on a weak shared host. We do not promise it never fails on a small hosting plan.

What about typos, synonyms and searches with zero results?

Search ranks in tiers: exact SKU or model, exact words, prefixes, then typo-tolerant matching. Open synonym packs cover Finnish, English, Swedish, German and Estonian, and learning can add rules from searches that found nothing (anonymous, capped, off with one switch). The packs are generated data that native speakers have not fully reviewed yet, and we have not measured a zero-result rate on a real shop, so we do not quote one.

Do filters create thousands of duplicate URLs for Google?

They are built not to. Filter controls are form elements, not links, so crawlers do not wander through combinations. Filtered URLs are noindex,follow and carry a canonical to the unfiltered archive (through WordPress core, Yoast SEO, Rank Math and All in One SEO), pages beyond the last one return a real 404, and you can optionally block filter URLs in robots.txt. We have not measured crawl statistics on a large shop.

How does the Google feed handle variable products?

By default every published variation becomes its own item with a g:item_group_id shared across the product, its own price, stock and image, and a link that preselects the variation. The file is static and requests never generate it. It is written on a schedule (manual, hourly, twice daily or daily) and after each rebuild, so prices are those at generation time, not real time. Limits: Google Merchant only, up to 500 variations per product, and colour, size, material and pattern attributes.

Will it work with my theme?

Instant search attaches to your existing search box through a CSS selector, so it works with classic and block themes without template changes. We verified it on a block theme, a classic theme and Salient with WPBakery. Diagnostics includes a compatibility check and suggested selectors for popular themes (treated as suggestions until verified on your site). Fast Grid replaces the main shop and category query; page-builder grids with their own queries are not replaced, but the [searchmaker_catalog] shortcode covers them.

What if the index is missing or broken?

The front end falls back to normal WooCommerce behaviour. Searchmaker is designed to fail soft: if the endpoint is unavailable or the index is unhealthy, shoppers still get results from WooCommerce while you rebuild.

Does it handle multiple languages?

It builds one index per language and is built for WPML and Polylang. Synonym packs are available for Finnish, English, Swedish, German and Estonian, and more languages are on the way (they are open data). TranslatePress-style setups are not supported yet.

What happens when a yearly license ends?

Yearly licenses are subscriptions that renew until you cancel, and each renewal produces a new key. If a term ends without renewal there is a 30-day grace period in which the modules keep working with a warning in the admin; after that the licensed modules switch off and WooCommerce takes over. Nothing is deleted.

What are the requirements?

WordPress 6.5 or newer, WooCommerce 8.0 or newer and PHP 8.1 or newer with the sodium extension (included in standard PHP builds) for offline license verification. No Redis, no daemon, no shell access, no extra database.

OEM and platforms

Building your own product? License the engine.

The index behind Searchmaker is a plain PHP library with a standalone runtime. Put search, filters and feeds inside your plugin, platform or hosting offer, under your brand.

Stop waiting on the database.

Install, build the index once, and try it on your own catalog. If it does not fit, the 30-day money-back guarantee covers it.