Weave Code
Meilisearch Laravel Package
statamic-rad-pack/meilisearch
A Meilisearch search driver for Statamic that adds fast, typo-tolerant full-text search to your site. Automatically index entries, configure searchable fields, and query results through Statamic’s native search API—ideal for content-heavy sites needing instant, relevant results.
Meilisearch search driver for Statamic.
Frequently asked questions about Meilisearch
- How do I install the Meilisearch search driver for Statamic?
- Install it with Composer using the package name statamic-rad-pack/meilisearch, then publish the package config and register the driver in config/search.php. Point the configuration at your Meilisearch host and credentials, usually via environment variables. After that, build the search index using Statamic's CLI index command. No database migrations or content model changes are required.
- Which Laravel and Statamic versions does statamic-rad-pack/meilisearch support?
- The current v4 line targets modern Statamic releases, and v4.1.0 specifically added Laravel 13 compatibility. Because the package is a driver on top of Statamic's search abstraction, your real constraint is the combination of Statamic core, this package, and the Laravel version your host runs. Check the composer.json constraints and the release notes before upgrading, since a driver being Laravel 13-ready does not mean Statamic core or your other addons are.
- How does Meilisearch integrate with Statamic's search API?
- The package is a thin adapter: it plugs into Statamic's existing search driver contract rather than replacing your application code. You register the driver in config/search.php and your templates or PHP continue to query through Statamic's native search facade. That containment keeps the integration surface small, typically just a service provider, a config block, and the indexer.
- How do I index Statamic entries into Meilisearch?
- Indexing is driven through Statamic's CLI, so you build the index from your existing content after configuring the driver. Plan your rebuild cadence up front, since entry updates need to reach Meilisearch for results to stay fresh. A common approach is to stand up Meilisearch in a staging environment first, rebuild from a representative content sample, and benchmark recall and latency before promoting to production.
- Can I choose which fields are indexed and searchable in Meilisearch?
- Yes. The driver lets you configure searchable fields so only the content you care about is sent to and matched by Meilisearch. This is worth tuning early, because it directly affects relevance quality and index size. It also helps control what content is exposed through search results.
- Does this package work with multi-site Statamic installations?
- Multi-site support depends on how you configure index granularity, which is a decision you make rather than something the driver decides for you. You can scope indexes per site or per collection depending on how you want results separated. Decide this before launch, since changing index granularity later means a rebuild and possibly reworked queries.
- What happens if the Meilisearch server is unreachable?
- This is a question worth validating explicitly in your own environment rather than assuming. The behavior may be that search returns empty results, throws an exception, or degrades in some other way, and that determines whether an outage breaks search pages or just returns nothing. Test it in staging by stopping the Meilisearch container. If search is on a critical path, wrap calls and define a fallback before going live.
- Do I need to run my own Meilisearch server, and which version should I use?
- Yes, this package is only the driver; you still need a Meilisearch instance to talk to. It can be a container for evaluation and a managed or self-hosted service in production. Compatibility is three-way between Statamic, this package, and the Meilisearch server version, so confirm the minimum supported server version in the package docs and match it to what your platform team will operate.
- Is statamic-rad-pack/meilisearch actively maintained?
- It is a well-regarded community addon maintained by Duncan McClean under Rad Pack, with a steady release history; v4.1.0 is a small, additive compatibility release with no deprecations or config changes. The main caveat is bus factor: it is a single-maintainer package without a commercial support contract. That is usually acceptable for search, but you should not put it on a critical write path without a plan.
- How does this compare to Statamic's built-in search driver or Algolia?
- Statamic ships a built-in search driver that may be entirely adequate at your content volume, so benchmark relevance and latency against it before adding an external engine. This package is the cheapest part of adopting Meilisearch; the real cost is standing up and operating the Meilisearch instance plus owning index rebuilds and relevance tuning. Choose it when you need typo-tolerant, instant full-text search on content-heavy sites and are prepared to run that infrastructure.
Weaver
How can I help you explore Laravel packages today?