Filament Seo Laravel Package

Product Decisions This Supports

• Shipping content-managed SEO without a custom build: this plugin surfaces SEO metadata fields (title, description, Open Graph image, etc.) directly inside Filament resource forms, backed by ralphjsmit/laravel-seo. It turns "let marketing own meta titles and descriptions" from a 1–2 sprint build into a configuration task.
• Filament upgrade planning: v3.0 is a major bump driven by Filament v5 support plus a newer laravel-seo constraint. This makes it a hard pairing decision — v3.0 is only adoptable once your admin panels are on Filament v5. It is effectively a gate on the Filament upgrade roadmap rather than an independent choice.
• Build vs. buy for admin-surface SEO: the honest alternative is ~200–400 lines of custom Filament fields plus your own persistence and validation. Buying wins if you only need standard meta/OG fields; building wins if you need editorial workflow (draft/publish of metadata, approvals), multi-locale SEO matrices, or structured-data generation beyond what the underlying laravel-seo package exposes.
• Use cases this most plausibly serves: brochure/marketing sites, CMS-backed blogs, and any product where non-engineers should edit page metadata without a deploy. It is weaker for headless/API-first products where SEO fields live in a CMS you already have.
• Roadmap sequencing signal: because the package tracks Filament majors closely, treat "our Filament version" as the primary input. If the team intends to stay on Filament v4 for two or more quarters, this release is not actionable now.

When to Consider This Package

Consider it when:

• You are on Filament v5 (mandatory for v3.0) and already using or willing to adopt ralphjsmit/laravel-seo as the storage layer.
• Your content editors need to manage meta title, meta description, and social/OG fields from the existing admin panel — no separate CMS.
• You want the feature in days, not sprints, and are comfortable with a small single-maintainer package for a low-blast-radius, admin-only surface.
• Your SEO requirements are conventional (title/description/OG image). Anything involving structured data, hreflang matrices, or redirects should be scoped separately.

Look elsewhere or build in-house when:

• You are on Filament v4 or earlier and have no near-term upgrade — v3.0 does not apply, and pinning v2.3.x means owning a stale dependency branch.
• The admin surface is business-critical and you need vendor support, SLAs, or an active multi-maintainer project; this is a small-org package (34ML) with a thin contributor base.
• You need SEO capabilities the underlying laravel-seo package doesn't model — you'll end up fighting the abstraction.
• You already run a dedicated CMS (Contentful, Sanity, Statamic) that owns metadata; duplicating it in Filament creates a second source of truth.

Adoption gate before committing: verify the exact laravel-seo version v3.0 pulls in against your existing install, and confirm the Filament v5 migration is actually scheduled. A major version here is a coupling upgrade, not a feature upgrade.

How to Pitch It (Stakeholders)

For executives: This is a small open-source add-on that lets our marketing team edit page SEO fields — titles, descriptions, social preview images — inside the admin tool we already have, instead of filing engineering tickets for text changes. It costs nothing to license and removes a recurring request from the backlog. The catch is timing: the new v3.0 only works with the newest version of our admin framework (Filament v5), so adopting it is bundled with that upgrade rather than standing alone. Risk is low — it touches only the admin panel, not the customer-facing site — but it is maintained by a single small team, so we should keep our usage conventional and be prepared to maintain a fork if it goes dormant.

For engineering: v3.0 is a maintenance release, not a feature release. Two changes: Filament v5 compatibility and a bump to the laravel-seo dependency. Both are breaking in the practical sense — the package now requires Filament v5 and a newer laravel-seo, so this must land in lockstep with the Filament upgrade and after auditing our laravel-seo version. It's a thin field-layer over an existing package, so the integration surface is small and vendoring/forking is cheap if needed. Recommend we sequence it into the Filament v5 workstream, pin the version, and avoid extending it with custom SEO logic that would make a future fork expensive.