Meilisearch is a real search engine, not a database plugin. It lives outside WordPress, indexes your content, and handles searches with typo tolerance and relevance tuning that WordPress can’t do natively. Use it when you’ve outgrown the default search, need speed at scale, or want control over ranking that you won’t get from a plugin.
What is Meilisearch, and why use it on WordPress?
Meilisearch is an open-source search engine built to handle typos, incomplete queries, and large datasets fast. On a WordPress site, it means your visitors find what they’re looking for even if they misspell it, and you rank results based on what actually matters to your business – not just database weight.
WordPress’s default search is a keyword match in the database. It’s fine for small sites. Meilisearch is for sites where search converts to action: directories, WooCommerce stores, content hubs with hundreds of posts, any place where visitors search multiple times and search quality drives revenue.
84EM has shipped Meilisearch on a high-performance directory site with passwordless listing management serving thousands of location-based listings. Search was the core feature there. Default WordPress search wouldn’t have worked at that scale. That same directory runs on headless WordPress with a Hugo frontend, with Meilisearch as the search layer.
The tradeoff: Meilisearch lives outside WordPress, which means you own the indexing logic, the server, and the integration. Rather than a plugin you install and forget, it’s a system you build and maintain.
How does Meilisearch integrate with WordPress?
Meilisearch integrates in three parts: the indexer, the API, and the frontend.
The indexer watches WordPress posts. When you publish or update, a hook fires (typically transition_post_status), and a custom indexer pushes the post data to Meilisearch. You decide what data to send – post content, custom fields, ACF meta, taxonomies, whatever matters for search. The indexer runs in WordPress, so you control it completely.
The API sits between your WordPress site and Meilisearch. It handles authentication and query transformation. A search request comes from the frontend, hits the API, gets sent to Meilisearch with the right filters and settings, and returns results back to WordPress. You can run the API on the same server as Meilisearch or separately.
The frontend is what your visitors use. That’s where search input goes. You can build it as a simple form, an autocomplete widget, or an instant-search interface. No first-party WordPress plugin exists for this; you build it or use a third-party plugin.
This is where the plugin vs custom-build decision comes in. Two plugins cover this today: Yuto, an autocomplete widget, and Scry Search, a fuller native-search replacement. Check each one’s maintenance status before relying on it (Yuto hasn’t been updated in 11 months as of this writing). A custom build gives you control over indexing, filtering, and the frontend interface regardless of what either plugin does. See the plugin vs custom build comparison for the full tradeoff.
Meilisearch vs the alternatives
The main alternatives are Algolia and WordPress search plugins like Relevanssi and SearchWP.
Algolia is managed, which means they run the server and you pay per request. It’s rock-solid and has a well-maintained WordPress plugin. The downside: you don’t own the data, pricing scales with traffic (good if you’re small; bad if you’re big), and you’re locked in.
SearchWP and Relevanssi are database-backed plugins. They run in WordPress, don’t require external infrastructure, and cost a flat license fee instead of a per-request bill. They’re better than default search but have a ceiling: they can’t compete with Meilisearch on speed, typo tolerance, or scale past a few thousand posts.
Meilisearch is open source and self-hosted. You own the data. Cost doesn’t scale with traffic. Typo tolerance and speed are native. The tradeoff: you manage the server and the integration.
Which is right for you? If you want managed simplicity and don’t mind per-request pricing, Algolia wins. If you have a small catalog and need to stay simple, a plugin is fine. If you want control, flat costs, and a real search engine, Meilisearch is it.
Head to Meilisearch vs Algolia for a full breakdown. Or see Meilisearch vs WordPress search plugins if you’re deciding between Meilisearch and a third-party plugin.
Meilisearch and WooCommerce
WooCommerce search is where search quality actually moves the needle. A visitor who can’t find what they want doesn’t buy.
Default WooCommerce search is product name and description. That’s thin. Meilisearch handles variations, custom taxonomy, ACF fields, and custom meta. You index what matters to your store: size options, color, brand, materials, whether it’s in stock.
The catch: there’s no first-party InstantSearch adapter for WooCommerce and Meilisearch together. You have to build it or adapt one. That’s why 84EM usually recommends a custom Meilisearch integration for WooCommerce over off-the-shelf connectors.
See Meilisearch and WooCommerce for what a correct build looks like and how it differs from plugin-based approaches.
Hosting and cost
Meilisearch lives on a server. That server can be managed (Meilisearch Cloud) or self-hosted (your VPS).
Meilisearch Cloud is a managed service like Algolia. You pay a monthly tier; they run the instance. It’s simpler but more expensive than self-hosting, especially at scale.
Self-hosting puts Meilisearch on your own VPS or server. Cost is flat: server rent, backups, updates. No per-request meter. But you own the operational burden: monitoring, security, updates, uptime. If you have high traffic, self-hosting is cheaper. If you’re small or want ops off your plate, Cloud might make sense.
See self-hosting Meilisearch for the full ops picture and Meilisearch pricing for the cost model compared to Algolia.
When Meilisearch is the right call for WordPress (and when it isn’t)
Use Meilisearch if:
You have hundreds of searchable items or more. Speed and typo tolerance matter to conversions. You want control over what gets indexed and how. You’re building something once and owning it long-term. Budget is a constraint; flat-cost self-hosting is cheaper than per-request pricing at scale.
Don’t use Meilisearch if:
You have a small site with simple content. Default search works fine. You want zero ops overhead and don’t mind paying for managed. You’re not comfortable running or paying someone to run infrastructure. Speed isn’t a conversion factor on your site.
Gray area:
You have a WordPress plugin that works but is getting slow or hitting limits. That’s often where Meilisearch makes sense. The plugin did its job at small scale; Meilisearch takes you to the next tier.
Getting it built
Meilisearch integration isn’t a one-afternoon project. It’s a system with indexer logic, an API, a frontend, and ongoing ops. Get it wrong and search is slow, missing results, or stale.
84EM builds custom Meilisearch integrations for WordPress sites where search is core to the product, handling the indexer, the integration, the frontend, and the ops side. See custom WordPress development to talk about your project.
