Filament Seo Files Laravel Package

Product Decisions This Supports

• Feature scoping: Decide whether automated sitemap.xml and LLM-readable files (llms.txt / llms-full.txt) belong in the product now. v1.0.2 is a reliability release, not a new feature release; it improves confidence in existing capabilities rather than expanding scope.
• Multi-tenant readiness: The auth/tenant-context fixes reduce the risk of tenant-scoped or user-dependent data leaking into public SEO files. This supports roadmap decisions for multi-tenant SaaS and panel-based admin tools.
• Internationalisation roadmap: Locale-specific generation and BCP 47 handling (es-419, zh-Hant-TW) make the package more viable for localised products and regional rollouts.
• Operational model: Non-blocking cache locks prevent panel-triggered and scheduled runs from interleaving. This supports decisions about whether generation can be safely exposed to admins or must remain scheduler-only.
• Build vs buy: If the product needs Filament-integrated sitemap/LLM file generation with tenant-aware sources, scheduler commands, and localisation, adopting this package is likely cheaper than building and hardening the same plumbing. If the need is a broader SEO suite, this is a component, not a replacement.
• Launch readiness: v1.0.2 fixes stylesheet leakage into panel pages, timezone display, case-insensitive search, and source-registry reset issues. These are quality signals that reduce launch risk but should not be treated as headline product differentiators.

When to Consider This Package

• Consider it when the product is Laravel + Filament, needs generated public SEO/LLM files, and wants an admin page plus scheduled commands without custom plumbing.
• Strong fit when sources are Eloquent models, especially with multi-tenancy, localised content, or user/tenant-dependent global scopes that must not leak into public files.
• Consider it when non-technical admins need a “Generate” action but the engineering team still wants scheduler-safe, lock-protected generation.
• Consider it for LLM discoverability and sitemap hygiene as a narrow capability, not as a full SEO platform.
• Look elsewhere or complement it if the roadmap requires redirects, meta tags, schema markup, sitemap indexing/sharding at very large scale, search-engine submission workflows, analytics, or non-Filament/non-Laravel admin surfaces.
• Treat v1.0.2 as a stabilisation release: no breaking changes are called out, but upgrading requires php artisan filament:assets. Validate the asset pipeline and any custom panel theme overrides.

How to Pitch It (Stakeholders)

For executives: This package gives the product a low-cost, admin-manageable way to publish sitemap and LLM-readable files. The latest release is primarily about reliability and safety: it prevents tenant/user data leakage into public files, stops overlapping generation runs, improves localisation support, and scopes admin styling correctly. It is not a new feature launch, but it reduces operational and multi-tenant risk.

For engineering: v1.0.2 is a bug-fix release focused on correctness in Filament panel contexts. Key changes: plugin CSS is scoped with fi-seo-files-* classes and loaded only on plugin pages; generation runs outside admin auth/tenant context; commands use non-blocking cache locks; llms generation respects file locale; source registry resets per application boot; timezone and search fixes land. No breaking changes are noted, but run php artisan filament:assets after upgrade.