Weave Code
Algoliasearch Laravel Laravel Package
algolia/algoliasearch-laravel
Official Algolia integration for Laravel. Index Eloquent models, keep them synced automatically, and add fast, typo-tolerant search to your app, with Scout support, aggregators, and zero-downtime reindexing.
algoliasearch-laravel is the official Algolia integration for Laravel. It connects your Eloquent models to Algolia's hosted search engine, keeping indexes synchronized automatically as records are created, updated, or deleted. Beyond basic indexing, it offers aggregators for searching across multiple models, a full Laravel Scout driver, and a fluent API for querying and managing indexes directly.
- Automatic model syncing via the
Searchabletrait - Multi-model search with aggregators
- Artisan commands for import, clear, and reindex
- Native Laravel Scout driver support
- Configurable indexing, ranking, and search parameters
Frequently asked questions about Algoliasearch Laravel
- Is algolia/algoliasearch-laravel deprecated?
- Yes. The package is archived and its README explicitly recommends Laravel Scout instead. Its last release predates Laravel 5.4 and PHP 7.1, and Algolia's supported path today is Laravel Scout plus the current algolia/algoliasearch-client-php. Do not add it to new or maintained Laravel applications.
- Does algolia/algoliasearch-laravel support Laravel 10, 11, or 12?
- No. The package predates package auto-discovery and pins the old Algolia PHP SDK v1, whose PHP constraints are effectively 5.x and 7.0-era. It is incompatible with modern PHP 8.1+ applications and modern Illuminate contracts. Composer will usually refuse installation, and forcing it with --ignore-platform-reqs is not a supported or safe workaround.
- What should I use instead of algolia/algoliasearch-laravel?
- Use laravel/scout with its Algolia engine plus the current algolia/algoliasearch-client-php. If you genuinely need multi-model aggregators, advanced synonyms, or multi-index search, add algolia/scout-extended. This keeps Eloquent-to-Algolia syncing while inheriting Scout's queue-based indexing, searchable() control, and soft-delete handling.
- Why does Composer fail when I run composer require algolia/algoliasearch-laravel?
- The package depends on algolia/algoliasearch-client-php ^1.0 and declares platform requirements from the PHP 5.x/7.0 era. On PHP 8.1+ and Laravel 10/11/12 those constraints conflict with your installed framework and PHP version. Composer refusing the install is the correct behavior; the package is archived and has no supported upgrade path.
- How do I migrate from algolia/algoliasearch-laravel to Laravel Scout?
- Treat it as a swap, not an upgrade. Replace the package's model trait with Scout's Searchable trait, implement toSearchableArray() explicitly instead of relying on toArray(), and put Scout behind an internal SearchService so controllers never call the engine directly. Then write to a versioned index such as catalog_v2, run a full reindex from a queue worker, shadow-read against production, and flip the alias before dropping the old index. Finally remove the old service provider, facade alias, and Composer entry.
- Does algolia/algoliasearch-laravel support queued indexing and soft deletes?
- No. It is a thin wrapper that calls the Algolia PHP SDK v1 directly from a model trait, with no queue integration and no index-settings-as-code. Missed deletes and silent indexing drift were common failure modes for this generation of wrapper. Laravel Scout handles queued synchronization and soft-delete removal as first-party behavior.
- Is algolia/algoliasearch-laravel secure or maintained?
- It is archived with no security policy, no patch path, and no CVE response process. Any future vulnerability in the bundled Algolia SDK would become permanently yours to manage. Archived dependencies with zero dependents also tend to fail Snyk, Dependabot, and SBOM-based dependency-hygiene gates.
- Can I still use algolia/algoliasearch-laravel in an existing legacy Laravel app?
- It may run on an old Laravel 5.x and PHP 7.0-era stack, but it is unsupported and has no security response. If you keep it temporarily, isolate it behind an internal search interface and budget a migration to Laravel Scout. Plan the swap before you need to upgrade PHP or Laravel, because the package blocks both.
- Does Laravel Scout require Algolia, or can I use Meilisearch or Typesense?
- Scout is engine-agnostic and ships drivers for Algolia, Meilisearch, Typesense, and database full-text search. If Algolia is not already contracted, Meilisearch, Typesense, and PostgreSQL full-text search are drop-in Scout drivers. That makes Scout the safer abstraction even if you later change search vendors.
- How do I register the algolia/algoliasearch-laravel service provider and facade?
- The package predates Laravel package auto-discovery, so older tutorials tell you to add the provider and facade alias manually in config/app.php. That manual registration assumes container bindings and Illuminate contracts from old Laravel versions. In modern Laravel you should not register it at all; install Laravel Scout and configure the Algolia driver in config/scout.php instead.
Weaver
How can I help you explore Laravel packages today?