Filament Rankforge Lite Laravel Package

Product Decisions This Supports

• Build vs. buy for on-page SEO: This package replaces a bespoke SEO meta layer (schema, admin form, scoring, tag rendering) with a maintained dependency. The HasSeo trait, one rankforge_meta row per record, and automatic score sync on every save — including saves outside Filament — mean an in-house scoring job and observer chain can be deleted rather than maintained.
• Scope of the SEO roadmap: Content-side on-page SEO (titles, descriptions, canonicals, robots, Open Graph/X cards, hreflang) is now largely covered out of the box. That frees roadmap capacity for the things this package does not do — sitemaps, redirects, structured data, programmatic/internal linking — which are the natural next bets.
• Whether SEO is a first-class product surface or a checkbox: The live analysis panel (overall/SEO/readability scores, 22 checks across 6 languages, desktop/mobile SERP preview, Facebook/X/LinkedIn card previews) turns SEO from a hidden field set into an editor-facing workflow. This is a UX decision as much as a technical one — it determines whether content teams self-serve or keep filing tickets.
• Which personas get the feature: Filament-resident teams get the full experience (SeoFields, SeoScoreColumn with red/yellow/green sorting for content audits and prioritisation). Headless/API consumers get only the rendering primitives (<x-rankforge::tags>, @rankforge), so an admin-panel-only launch is a legitimate phased decision.
• Migration sequencing vs. incumbents: Explicit compatibility with ralphjsmit/laravel-seo on the same model (no trait boot collision) means adoption can be incremental and reversible — a real de-risking factor for the buy decision.
• Localisation/market reach: 6-language checks and hreflang output support multi-market launches without custom work.
• Upgrade posture: Matching namespace, table, migration names and config keys to RankForge implies a drop-in successor with no content migration — relevant if RankForge is already in production anywhere, and a reason to treat this as a rename/continuation rather than a greenfield adoption.

When to Consider This Package

Adopt when:

• You run Laravel + Filament and content editors are the primary SEO operators.
• You need a single meta record per model covering titles, descriptions, canonicals, robots, OG/X fields and hreflang — i.e. standard on-page SEO, not programmatic/edge SEO.
• You want scores surfaced in the admin (sortable, colour-coded) to drive editorial prioritisation or QA.
• You are replacing RankForge — the identical namespace/table/config contract makes this a no-content-migration upgrade.
• You already use ralphjsmit/laravel-seo and want to trial this alongside it rather than rip-and-replace.
• You render tags in Blade (<x-rankforge::tags>, @rankforge) rather than through a JS/meta-framework pipeline.

Look elsewhere when:

• You are not on Filament — most of the value (form section, analysis panel, score column) is Filament-bound; you would be buying the trait and Blade tags only, which is a thinner case.
• You need sitemaps, redirects, robots.txt management, structured data/JSON-LD, or programmatic SEO at scale — out of scope here, so plan a companion tool.
• You need multi-locale meta per record with per-market variants — the release describes one row per record with hreflang output, not per-locale meta storage. Validate before committing if that's a requirement.
• Your SEO workflow lives outside the CMS (e.g. a separate SEO team with its own tooling and score of record); duplicating a scoring model creates a second source of truth.
• You require published stability guarantees — v1.0.0 is the first release, so treat the API surface and scoring model as young.
• You need enterprise SEO analytics (rank tracking, backlinks, indexing status) — this is on-page authoring assistance, not a monitoring platform.

How to Pitch It (Stakeholders)

For executives: We can stop maintaining our own SEO plumbing. This Laravel/Filament package gives editors SEO fields, a live quality score with SERP and social-card previews, and red/yellow/green scores in the content list — the kind of feedback loop that reduces rework and low-quality publishes without adding headcount. It replaces in-house code rather than adding to it, and because it keeps the namespace, table and config of the tool it supersedes, there is no content migration and a clean rollback. The strategic win is capacity: on-page SEO moves from roadmap to dependency, letting us invest in sitemaps, redirects and structured data where we still have gaps.

For engineering: One trait, one meta row per model, scores recomputed on save via the model layer rather than only through Filament — so API and artisan writes stay consistent and we delete our observers. Rendering is a Blade component and a directive; the admin surface is a form section, a live analysis panel and a sortable score column. It coexists with ralphjsmit/laravel-seo on the same model without trait boot collisions, so we can pilot on a low-traffic model and compare before committing. Main caveats to size up front: v1.0.0 means the public API is still settling, Filament is effectively a hard dependency for the majority of the value, and we should confirm per-locale meta behaviour before scoping multi-market content.