Weave Code
Sitemap Bundle Laravel Package
nucleos/sitemap-bundle
NucleosSitemapBundle is a Symfony bundle for generating XML sitemaps from routes, Doctrine entities, and custom providers. It supports sitemap indexes, URL sets, priorities, change frequencies, last-modified dates, and caching, making it easy to expose content to search engines.
This bundle provides some classes for an automatic sitemap.xml generation.
Frequently asked questions about Sitemap Bundle
- Is nucleos/sitemap-bundle compatible with Laravel?
- No. nucleos/sitemap-bundle is a Symfony bundle that depends on Symfony's bundle registration, dependency injection container, routing, and event system, none of which map to Laravel's service-provider model without significant adapter work. Installing it in a Laravel application does not give you a working sitemap generator. Treat it as a reference implementation only.
- Can I install nucleos/sitemap-bundle with Composer in a Laravel project?
- Composer installation may succeed because Laravel already pulls in several Symfony components, but runtime integration will fail or require heavy glue code. The bundle expects a Symfony kernel and container to boot. Version conflicts between the bundle's Symfony constraints and Laravel's own Symfony dependencies are also likely, so audit composer.json before any spike.
- What does nucleos/sitemap-bundle actually do?
- It generates standards-compliant XML sitemaps from a Symfony application, including sitemap indexes, URL sets, priorities, change frequencies, last-modified dates, and caching. Entries can come from routes, Doctrine entities, or custom provider services. Output is exposed through a controller or console command.
- Is nucleos/sitemap-bundle still maintained?
- No. Release 4.4.0, published on 2022-09-18, is a deprecation-only minor that points adopters to nucleos/seo-bundle, and the project has been archived. There is no active maintainer, no security patch path, and no further compatibility work expected. Adoption is very low, with 5 stars and 0 dependents.
- What should Laravel developers use instead of nucleos/sitemap-bundle?
- Use a Laravel-native sitemap generator such as spatie/laravel-sitemap, which integrates with Eloquent models, routing, and Laravel's cache. If your requirements are simple, a small internal generator that writes sitemap.xml from a route list or query is often enough. Either option avoids Symfony kernel coupling and keeps you on a maintained release path.
- Does nucleos/sitemap-bundle support sitemap indexes, priorities, and change frequencies?
- Yes. The bundle supports sitemap indexes, URL sets, priorities, change frequencies, last-modified dates, and caching. These features are implemented against Symfony's routing and service container, so they are useful as a reference but not portable to Laravel as-is.
- Can I extract the sitemap generation logic from nucleos/sitemap-bundle for Laravel?
- Possibly, but only after verifying in source that the XML generation classes are decoupled from Symfony and Doctrine. The bundle is MIT-licensed, so copying minimal logic into an internal package is legally fine, but you would own that code permanently since upstream fixes will never land. For most Laravel projects, writing a small generator or adopting a native package is cheaper than extraction.
- What PHP and Symfony versions does nucleos/sitemap-bundle require?
- The declared constraints are not confirmed in this evaluation and must be read from composer.json before any commitment. Compatibility with PHP 8.2, PHP 8.3, Symfony 6, and Symfony 7 is unknown, and the last release dates to 2022. Because the package is deprecated, nobody will widen those constraints for you.
- Is nucleos/seo-bundle a good replacement for Laravel projects?
- No. nucleos/seo-bundle is also a Symfony bundle, so the framework mismatch is unchanged. The deprecation notice reflects the maintainer consolidating an end-of-life portfolio, not a redirect to a Laravel-friendly option. Evaluate it as a brand-new dependency for Symfony targets only, checking activity, release cadence, and feature parity for sitemap generation.
- What are the risks of using a deprecated Symfony bundle in a Laravel app?
- You inherit an unmaintained dependency with no security patch path and unknown compatibility with current PHP and Symfony versions. Any adapter layer you write becomes yours to maintain forever, and future Laravel upgrades may break the Symfony components the bundle relies on. For a production Laravel application, that risk is hard to justify when maintained native alternatives exist.
Weaver
How can I help you explore Laravel packages today?