Weave Code
Findable Laravel Package
elaniin/findable
Findable adds simple, reusable search to Laravel Eloquent models. Add the trait, define searchable fields, and query models with clean, request-friendly syntax—reducing boilerplate for list pages, admin tables, and API search endpoints.
An SEO add-on for Statamic.
Frequently asked questions about Findable
- Is elaniin/findable a Laravel package or a Statamic add-on?
- The repository describes elaniin/findable as an SEO add-on for Statamic, even though it is often catalogued as a Laravel/PHP package. Statamic runs on Laravel, so the Laravel dependency is transitive rather than the package's primary integration point. Its blurb also mentions an Eloquent search trait, which conflicts with the Statamic description; confirm the actual code path in the repository before relying on either claim.
- How do I install elaniin/findable in a Laravel application?
- For a Statamic 3 site, install it with composer require elaniin/findable and let Statamic's add-on manifest or Laravel auto-discovery register the service provider. Then publish any config or assets and attach the provided SEO fields to your collections and site defaults. On a plain Laravel app without Statamic, there is no meaningful integration surface, so this package is not the right dependency.
- Does elaniin/findable support Statamic 4 or Statamic 5?
- There is no evidence of Statamic 4.x or 5.x support; the last release was January 2022, which places it in the Statamic 3 era. A ^3.0 constraint would hard-block installation on current Statamic versions regardless of code quality. If you are on Statamic 4 or 5, plan to fork and port the add-on or use a maintained alternative.
- What Laravel and PHP versions does elaniin/findable require?
- The TPM assessment places it around Laravel 8 to 10 and PHP 8.0 to 8.1, but the exact matrix must be confirmed from the package's composer.json. Check the statamic/cms and laravel/framework constraints against your pinned versions in a scratch environment before estimating work. Do not assume compatibility from the Laravel requirement alone, because Statamic's own version constraint usually gates installation.
- How do I add search to Eloquent models with elaniin/findable?
- The package blurb describes adding a trait, defining searchable fields, and querying models with request-friendly syntax to cut boilerplate for list pages, admin tables, and API endpoints. However, the repository and technical assessment identify the package as a Statamic SEO add-on, not an Eloquent search library. Verify the trait and search API exist in the source code before designing around them. If they do not, a small custom scope or a dedicated Laravel search package is a safer choice.
- Where does elaniin/findable store SEO metadata?
- The assessment flags this as an open question: metadata may live in entry front-matter (YAML) or in a separate table. The storage model determines migration cost and whether your data survives if you later swap add-ons. Inventory existing field handles and data locations before mapping them into this package's blueprint fields. Preserve the old fields until the new output is verified in production HTML.
- Is elaniin/findable still maintained?
- Treat it as effectively unmaintained: the last release was 2022-01-27, it has around 13 stars, and it is a single-agency project with no visible release cadence. There is no evident test suite, CI, or security audit trail. If you adopt it, budget to fork and own the code rather than expecting upstream fixes.
- What are alternatives to elaniin/findable for Statamic SEO?
- Statamic ships SEO Pro, a first-party, commercially supported add-on that covers per-entry meta plus sitemap, robots, canonical, and redirect concerns. A custom fieldset with a few templates is another option when you only need per-entry meta tags and want no third-party dependency. Weigh the cost and feature gap against the maintenance risk of a low-adoption community add-on.
- Does elaniin/findable work with Statamic multisite and static caching?
- Multisite support and meta-field localization are not documented in the material reviewed, so verify both in a scratch install. Static caching compatibility is also unconfirmed, and SEO output that depends on request context can behave differently when pages are cached. Test the rendered HTML, canonical tags, and sitemap behavior with caching enabled before going live.
- How should I test elaniin/findable before using it in production?
- Start with a scratch Statamic 3 environment pinned to your target Laravel and PHP versions and confirm the package installs cleanly. Then attach the SEO fields to a test collection, re-save entries to backfill defaults, and inspect the rendered HTML rather than only the control panel. Check canonical tags, meta output, sitemap and robots behavior, static caching, and multisite if applicable. Keep the old fields in place until the new output is verified.
Weaver
How can I help you explore Laravel packages today?