- Can I use jgniecki/sitemap-bundle in a Laravel application?
- No. jgniecki/sitemap-bundle is a Symfony bundle built around a DI extension, compiler passes, and bundle service configuration, so Laravel cannot load it as-is. There is no Laravel ServiceProvider, facade, or config-publishing shim in the package. You would have to write and maintain an integration layer yourself. For a Laravel app, a Laravel-native sitemap package is the lower-risk choice.
- How do I install and register jgniecki/sitemap-bundle?
- Install it with Composer using composer require jgniecki/sitemap-bundle. In a Symfony app, register the bundle in bundles.php, import its routing where needed, and configure your sitemap definitions. Then run the package's Symfony console command to generate the XML. The package is not installed or registered through Laravel's provider system.
- Does jgniecki/sitemap-bundle support Laravel 11 or Laravel 12?
- No. The package is a Symfony bundle with no declared Laravel support, and v1.1.0 does not add a Laravel ServiceProvider or facade. Laravel's package discovery will not bootstrap it. If you need Laravel 11 or 12 support, use a Laravel-native package rather than forcing this bundle into Laravel.
- How does jgniecki/sitemap-bundle discover URLs for the sitemap?
- URL discovery is route-introspection based, and v1.1.0 adds host filtering so routes can be scoped by host. That answers part of how URLs are collected, but the package documentation still leaves explicit or tagged providers and database-driven sources open. It does not advertise a generic content crawler. You should verify provider behavior against your own route setup.
- Does jgniecki/sitemap-bundle support sitemap indexes for large sites?
- Yes. The package generates XML sitemaps and sitemap indexes for larger sites. v1.1.0 adds host-specific sitemap groups and host-level sitemap paths, which can support per-host index structures. However, the docs do not clearly describe sitemap index sharding limits or gzip support, so test large-site output carefully. This is a Symfony feature, not a Laravel one.
- How do I configure priority, changefreq, and lastmod values?
- You define sitemap URLs through configuration or route-aware providers, and the package lets you set priority, changefreq, and lastmod values in that configuration. v1.1.0 adds host groups and host-level paths, which increases the configuration surface area. The maintainer also added warnings for the default group, suggesting the default path can be a misconfiguration trap. Validate generated XML after config changes.
- Can I generate separate sitemaps for multiple hosts or domains?
- Yes, as of v1.1.0. The release adds host-specific sitemap groups, host-level sitemap paths, and route filtering by host. That makes it a better fit for multi-tenant or multi-locale Symfony estates than earlier versions. It still does not state hreflang, news, image, or video sitemap support. Host detection behind a proxy or CDN needs careful validation to avoid cross-host canonical leaks.
- What Laravel package should I use instead of jgniecki/sitemap-bundle?
- For Laravel, spatie/laravel-sitemap is the correct comparison because it is Laravel-native and has its own host and domain concepts. jgniecki/sitemap-bundle is Symfony-oriented, so using it in Laravel means forking or wrapping Symfony bundle behavior. With v1.1.0 adding host grouping, the glue-versus-build math moves further against the bundle in Laravel. Choose the Laravel-native package unless you have a specific Symfony integration requirement.
- Is jgniecki/sitemap-bundle production-ready and actively maintained?
- Treat it as elevated risk. The package has zero stars, zero dependents, no issue history, and no third-party review, so there is no community validation. It is maintained by a single person, which is a bus factor of one. The positive signal is release cadence: an initial release on 2025-09-04 and an active v1.1.0 with three merged PRs. In a Symfony host that cadence is encouraging; in Laravel the integration burden remains high.
- Does jgniecki/sitemap-bundle support gzip, hreflang, or image/video sitemaps?
- Gzip support is not stated in the release notes or overview. The package does generate XML sitemaps and sitemap indexes, and v1.1.0 adds host-aware grouping and paths. Hreflang, news, image, and video sitemap support are not mentioned, so do not assume they exist. Check the repository and composer.json for current constraints before relying on advanced sitemap formats.