Filament Seo Laravel Package

Getting Started

digit7s/filament-seo v0.1.0 is a first public release, so treat the API as pre-1.0 and pin ^0.1. It gives you three things: a polymorphic SEO metadata table/model, Filament UI pieces (form fields, optional tabs, infolist section, status and score columns), and a Blade component that renders the stored metadata into a document <head>.

Minimal path:

composer require digit7s/filament-seo:^0.1
php artisan vendor:publish --tag=filament-seo-config
php artisan vendor:publish --tag=filament-seo-migrations
php artisan migrate

Check the version constraints before anything else — PHP 8.4+, Laravel 13, Filament 5. If your app is on an older Laravel/Filament pair, this will not install, so verify in CI before planning work around it.

Where to look first: the published config file (it controls the SEO model/table and likely image/disk behaviour) and the README's resource-integration example. Your first use case should be one Filament resource — a Page or Post — where you add the SEO form section to the resource schema, persist the polymorphic relation, then place <x-filament-seo::meta> once in that model's frontend layout <head>. Confirm the rendered tags with a quick curl or feature test before rolling it out to other resources.

Implementation Patterns

Resource form integration. Add the package's SEO fields to your resource form, ideally inside the optional tabbed layout so the main content tab stays clean. Pair it with the infolist section on the view page and the status column on the table, so editors can see at a glance which records have metadata and which don't.

Polymorphic reuse across models. Because storage is polymorphic, one SEO table serves pages, posts, products, etc. Use the same form section partial/schema method across resources rather than duplicating field definitions, and define one Blade layout that renders the meta component for whichever model the view receives.

Explicit head placement. Put the component once in your base layout inside <head>, passing the current record:

<head>
    ...
    <x-filament-seo::meta :model="$page" />
</head>

Every frontend layout that should emit tags needs this — there is no automatic injection.

Editorial workflow with the score column. Use the score column as a triage signal in the Filament table (sort or filter low scores) and the status column for publication readiness. Combine with a table filter on "missing description" style conditions if the package exposes them, otherwise sort by score ascending during content audits.

Image handling. Store Open Graph images on a public disk and save the resulting URL/path. The component validates public-disk image URLs and silently omits ones that don't resolve, which is the intended safety behaviour but also means a misconfigured disk produces no visible error on the page.

Testing. Add a feature test per frontend route asserting <title>, og:title, and canonical presence, plus one asserting the tags are absent when a record has no SEO row. This catches layout regressions where the component gets dropped from a template.

Gotchas and Tips

• Nothing renders until you place the component. There's no auto-injection, no middleware, no head hook. A missing tag on a live page usually means the layout wasn't updated, not that data is missing.
• Version floor is aggressive. PHP 8.4 + Laravel 13 + Filament 5 excludes most current production stacks. Check composer why-not if install fails; don't try to force it with --ignore-platform-reqs in a Filament app.
• Private disks and S3 URLs get dropped silently. The public-disk validation means storage/app/private, or S3 without a public URL configured, will simply omit og:image. Verify the disk's url config and that php artisan storage:link has run for the local disk.
• Escaping is intentional. Title/description output is escaped, so any HTML entities or markup you paste into the SEO fields will render literally. Keep the fields plain text.
• Canonical and robots are stored, not derived. The package won't compute a canonical from the current URL or infer noindex from publication status. If those fields are left blank, you get no tag — set them deliberately for paginated, filtered, or syndicated pages.
• Status/score columns are editorial aids, not SEO truth. Don't build reporting on the score; it won't reflect rankings, backlinks, or Core Web Vitals.
• No JSON-LD, sitemap, robots.txt, crawling, or ranking data. Pair with spatie/laravel-sitemap and hand-written schema markup if you need those. The robots field is the meta tag only.
• No translation of stored metadata. EN/MY/TH translations cover the Filament UI labels, not your content. For multilingual sites you need per-locale SEO records (the polymorphic relation makes this feasible) or separate locale-keyed fields, and you'll need to publish/override the lang files for any locale beyond the three shipped.
• After publishing config, run php artisan config:clear (and in production, re-cache). Stale cached config is the classic reason published settings appear to have no effect.
• Watch table performance on the score column. If the score or status is computed per row, eager-load the SEO relation in the resource's query to avoid N+1 queries on large tables.
• Extension points: publish the views to change tag order/attributes, override the translation files for custom locales, and extend the published migration/model if you need extra fields (e.g. og:type, locale). Re-publishing migrations after an upgrade can overwrite local edits — diff before running the publish command.
• Pre-1.0 stability: keep an eye on the changelog between 0.1.x releases; minor versions may adjust component attribute names or config keys.