- How do I install 3x1io/filament-sitemap in a Laravel application?
- Install it with Composer (composer require 3x1io/filament-sitemap), then publish the config and migrations with vendor:publish, run php artisan migrate, and register the plugin in your Filament panel provider. The package targets Laravel apps already running Filament v3 on Laravel 10 or 11. Check the repository README for the exact plugin registration snippet for your panel.
- Does filament-sitemap work without Filament, or can I use it in a plain Laravel app?
- No. It is a Filament panel plugin with hard runtime dependencies on Filament and spatie/laravel-settings, so it only makes sense when your admin surface is already Filament. Pulling the entire Filament dependency tree into a non-Filament app just to produce a sitemap is not justifiable. For plain Laravel projects, use a standalone generator such as spatie/laravel-sitemap instead.
- How do I register my models and custom URLs in the sitemap?
- You register models or custom URLs from the Filament admin panel, where you also configure priorities and update frequencies per entry. Configuration is persisted through spatie/laravel-settings, so it survives deployments and is editable without touching code. The exact registration API and config keys are documented in the package README.
- Why did my migration fail with a spatie/laravel-settings collision?
- Version 1.0.0 shipped migrations that could clash with the timestamps used by spatie/laravel-settings, which was the most likely first-install failure. Version 1.0.1 adds a migration-publish option with an explicit timestamp to avoid that collision. Publish using the new option, or adjust ordering, and pin the exact patch version in composer.json rather than floating a caret constraint.
- Does filament-sitemap support a sitemap index with chunked child sitemaps?
- This is not answered by the release notes, and it is the single biggest scalability question for the package. A flat sitemap.xml is fine up to a few thousand URLs, but search engines cap a single file at 50,000 URLs or 50 MB, so larger sites need a sitemap index. Test with a realistic URL set before committing if your catalogue runs into the hundreds of thousands.
- Is sitemap generation synchronous on request, or can I schedule it?
- The generation model is not documented in the supplied release notes, so verify it against the source before relying on it. Only artisan-invoked or schedulable and queueable generation is production-viable for large sites, because building a sitemap inside a web request risks timeouts. If generation is synchronous on request, wrap it in a scheduled command for anything beyond a few thousand URLs.
- Does it support multiple Filament panels, multiple domains, or hreflang locales?
- Multi-panel, multi-domain, and multi-locale behaviour is not confirmed in the available materials, and the answers determine whether the package fits international or multi-tenant products. If you need one sitemap per panel, per domain, or hreflang alternates, confirm support before adopting. Otherwise plan a custom route or a different generator for those cases.
- Where is the generated sitemap XML stored and how is it served?
- The release notes do not specify whether the XML lands on the public disk, in storage behind a route, or is generated on the fly, and that choice affects caching, CDN behaviour, and file permissions. If you are replacing a hand-rolled Route::get for sitemap.xml, keep the same public path so previously indexed sitemap URLs do not start returning 404s. Confirm the emission path before switching over.
- Is 3x1io/filament-sitemap production ready, and what is the maintenance risk?
- It is at version 1.0.x with a single maintainer and its first external contribution landing in 1.0.1, so bus-factor risk is real even though the code itself is a thin, low-coupling layer. The migration-timestamp fix found and shipped quickly is a good sign, but its existence suggests thin test coverage on fresh installs. Pin the exact patch version, review the source, and keep a fallback sitemap route in mind.
- Will it work with Filament v4 or Laravel 12, and how do I check compatibility?
- The supported version matrix is not published in the release notes, so run composer why-not against the Filament and spatie/laravel-settings versions your app already pins before committing. Because 1.0.1 is explicitly coupled to spatie/laravel-settings migration behaviour, pin the exact patch version rather than a caret constraint. Re-verify compatibility on every bump during the trial period.