Filament Sitemap Laravel Package

Product Decisions This Supports

• SEO hygiene as a checkbox, not a project. A Filament-native sitemap generator lets you ship "we have a sitemap" in an afternoon instead of a sprint, which is usually enough for early-stage crawlability needs.
• Build vs. buy on admin tooling. The build option here is small (a route + a query over published models); this package is worth buying only when you also want the settings UI and Filament integration to be someone else's maintenance burden.
• Roadmap sequencing for SEO surface area. If sitemap management is a precondition for content/SEO work (marketing pages, programmatic pages, multi-locale routes), adopting now unblocks that work; if SEO is a next-quarter theme, defer.
• Scope boundary for the admin panel. Deciding whether sitemap configuration belongs inside the Filament settings page (low-friction, discoverable) or in .env/config only (fewer moving parts). v1.0.1's "hide settings hint" toggle is a direct acknowledgement that this is a real product decision, not just a technical one.
• Dependency posture. The timestamped migrations option exists specifically to coexist with spatie/laravel-settings. If you already run that package, this release is what makes adoption tractable without hand-editing published migrations — a concrete build-vs-buy cost reduction.
• Not supported: sitemap strategy decisions (what to include, priority/changefreq policy, index segmentation, hreflang). Those remain yours regardless of the package.

When to Consider This Package

Adopt when most of these are true:

• You are on Filament (this is a Filament plugin, not a general Laravel sitemap library) and want sitemap handling surfaced in the admin panel rather than in code.
• You already use, or plan to use, spatie/laravel-settings — v1.0.1's timestamped migration publish option is aimed squarely at that combination.
• Your sitemap needs are single-file and straightforward: published models/routes, standard URL set, no sharding or complex index requirements.
• You want a configurable settings surface for non-engineers (or for your future self) and are willing to accept a young package to get it.
• You value speed over vendor maturity and are comfortable pinning a version and reading the source if something breaks.

Look elsewhere (or build in-house) when:

• You are not on Filament — this buys you little over spatie/laravel-sitemap directly.
• You need large-scale sitemap indexing, >50k URL segmentation, multi-locale hreflang generation, or per-section sitemaps with caching and invalidation. That is a design problem, not a plugin install.
• You require mature maintenance signals: this is a v1.0.x package from a single maintainer with a small contributor base (one new contributor in this release). If your org gates on adoption metrics, it will not clear the bar.
• Sitemap output is compliance- or revenue-critical and needs an SLA, security review, or long-term support commitment.
• You need auditable, tested behaviour across Laravel/Filament major-version upgrades and cannot absorb upgrade churn.

How to Pitch It (Stakeholders)

For executives: This is a low-cost, low-risk add-on that closes a standard SEO gap — a machine-readable sitemap that search engines can crawl — without a dedicated engineering project. It is a v1.0.1 release from a small independent maintainer, so treat it as a tactical convenience rather than strategic infrastructure: expect to own the fallback if it stalls. Cost of trying is hours; cost of being wrong is a config change.

For engineering: A Filament plugin wrapping sitemap generation with a settings UI. The v1.0.1 patch is small but meaningful for us: it adds a config toggle to hide the settings hint, and — more importantly — a timestamped migration publish option that avoids collision with spatie/laravel-settings migrations. That second item removes the main integration friction we would otherwise hit in our stack. Surface area is small and the code is readable, so forking is a realistic escape hatch. Recommended posture: pin the exact version, publish and review the migrations rather than trusting defaults, and confirm the Filament major version constraint matches ours before merging. Do not let sitemap content policy (which models, which locales, priorities) drift into the plugin's defaults — that stays an explicit product decision owned by us.