Magento Search That Forgives A Typo

Yes — free up to 100 search results, for as long as you like, no card required. Paid plans start at $5.99/mo and are priced by catalogue size only, never per search.

Because running a search engine and having good search are different problems. Magento 2.4 requires OpenSearch or Elasticsearch, so you are already paying to size, patch and monitor a cluster — and out of the box it still returns nothing for a misspelling. We measured it: on a stock 2.4.8 install with sample data, searching “jaket” returns “Your search returned no results”, while “jacket” returns the jackets. NitroSearch returns twenty-three for both, and there is no cluster of yours in the path.

One Composer command — `composer require nitrosearch/magento2-search` — then the usual `module:enable`, `setup:upgrade`, `setup:di:compile` and `cache:flush`. Distribution is Composer and GitHub rather than the Adobe Commerce Marketplace, so there is no reviewer queue between a release and your install. Then open Stores → Configuration → Services → NitroSearch and press Connect.

Magento Open Source only. Adobe Commerce and Commerce Cloud are out of scope — we have not tested against them and will not claim support we cannot stand behind.

Yes, and the same single module serves both. Luma and Hyvä name their search box identically, so one layout file covers both themes — we verified it on one install running Luma on the default store view and Hyvä on a second one, including add-to-cart from the results grid.

Ours won’t. Every search travels from the shopper’s browser straight to our cloud-hosted engine, so neither your PHP workers nor your search cluster are in the path. Sending your catalogue to us happens in small batches on your existing cron, and never during a checkout.

Through Magento’s own change tracking, not a “product was saved” event. That matters more on Magento than anywhere else: catalog price rules applying from cron, tier prices written by mass tooling, stock moving because of pending orders and `bin/magento import` all change what a shopper should see without anyone saving a product. A save-hook extension does not break on those — it quietly drifts, which is worse.

One store view per connection today. Magento’s scope hierarchy is real and we would rather index one store view correctly than several badly — the Connect screen makes you choose which, and states the limit on the page rather than after you install.

Not yet. The module’s own back-office screens are in English today. The storefront search panel is a separate thing and already speaks 22 languages on WooCommerce; those translations have not reached the Magento module yet.

Yes. On every paid plan you get searches, click-through rate, add-to-cart rate, latency, the zero-result list, and search-attributed revenue — an order traced back to the search that started it. We proved that one through a real guest checkout, with a discount running and an unrelated item in the same basket, before we published the module.

Nothing you have to think about, with one setting worth checking. Pages carrying our configuration are tagged, so when your storefront search key is renewed only those pages re-render — we never flush your whole cache. If you run Varnish, Magento sends cache purges only to the hosts listed in `http_cache_hosts`; `bin/magento nitrosearch:status` tells you whether yours is set, because the failure is otherwise silent.