Weave Code
Sitemap Bundle Laravel Package
skuola/sitemap-bundle
Symfony bundle for generating XML sitemaps from your application's routes and content. Configure sitemap sections, URLs, priorities, and change frequencies, then expose a search-engine-ready sitemap.
skuola/sitemap-bundle is a PHP package for adding XML sitemaps to Symfony applications. It provides a lightweight way to expose sitemap endpoints and build sitemap documents from application URLs, helping search engines discover and index site content.
- Generate standards-compliant XML sitemaps
- Define URLs manually or from application routes
- Support for sitemap indexes on larger sites
- Configurable through standard Symfony bundle settings
- Simple integration with existing routing and controllers
Frequently asked questions about Sitemap Bundle
- Can I install skuola/sitemap-bundle in a Laravel application?
- Not directly. skuola/sitemap-bundle is a Symfony 2 bundle built around Symfony's HttpKernel and DependencyInjection components, so it will not boot inside a Laravel application. Its Composer constraints target Symfony 2 and an older PHP floor, which conflicts with Laravel 10 and 11 requiring PHP 8.1+ and Symfony 6 or 7 components. Installing it would require --ignore-platform-reqs or a fork, and even then it would not function as a Laravel package.
- Is skuola/sitemap-bundle maintained or abandoned?
- The last release was 2016-09-06, and Symfony 2 reached end of life in 2018 and 2019, so there are no security patches or PHP 8 compatibility updates. The repository has roughly 4 stars and no dependents, which means little production evidence. Treat it as abandoned and do not build new work on it.
- Which Laravel and PHP versions does skuola/sitemap-bundle support?
- There is no official Laravel version support at all; it is a Symfony 2 bundle that pins symfony/symfony ~2.x and an older PHP version. Modern Laravel releases require PHP 8.1 or newer and Symfony 6 or 7 components, so the constraints conflict. You should assume it is incompatible with Laravel 8, 9, 10, 11, and any current PHP runtime.
- What are the best Laravel alternatives for sitemap generation?
- Use a maintained Laravel-native option such as spatie/laravel-sitemap, or write a small generator of your own. A typical Laravel shape is a SitemapServiceProvider registering a singleton generator, a config/sitemap.php for URL sources and output paths, an Artisan command like sitemap:generate scheduled in the console kernel or scheduler, and a thin controller or static route serving the XML. That gives you the same result without a Symfony translation layer.
- What does skuola/sitemap-bundle actually do, and how does it source URLs?
- It is a Symfony bundle that helps build and manage XML sitemaps: it defines a bundle class, a DI extension with a configuration tree, service definitions, and almost certainly a controller or route that emits sitemap.xml. URL sourcing is likely explicit registration, Doctrine entity scanning, or route introspection, but only the first two are portable concepts. Route introspection is Symfony-specific and would need to be reimplemented for Laravel routes.
- Does it handle sitemap index files and the 50,000 URL or 50 MB per-file limits?
- The technical evaluation could not confirm index support or enforcement of the 50,000 URL and 50 MB per-file limits; you would need to read the source to verify. A 2016-era bundle of this size often produces only single-file output. If you port the logic, design for sitemap indexes and file splitting from the start, because those limits are what break large sites.
- Is the license safe to reuse in a commercial closed-source Laravel app?
- The license is unverified in the evaluation, so check the LICENSE file in the repository before copying any code into a commercial or closed-source Laravel codebase. A missing or non-permissive license blocks the porting path entirely, even if you only reuse the design ideas. If the license is permissive, keep the attribution and treat the code as a reference to be reimplemented.
- How hard is it to port skuola/sitemap-bundle logic to Laravel?
- Integration effort is measured in hours of source reading, not Composer wiring. You would map the Symfony bundle, DI extension, services, and controller onto a Laravel service provider, config file, Artisan command, and route, rather than transliterating Symfony idioms. Because there is likely no test suite, you must re-derive and re-verify the sitemap output yourself.
- Does skuola/sitemap-bundle support lastmod, changefreq, priority, and image, video, or news extensions?
- That is not confirmed. The evaluation notes it is unknown whether lastmod, changefreq, priority, and image, video, or news extensions are supported; a bundle from 2016 may only cover the base sitemap schema. Read the source and check the generated XML before assuming search-engine features. If you need media extensions, a maintained Laravel package is the safer choice.
- Is skuola/sitemap-bundle tested and production-ready for a Laravel site?
- There is no evidence of a test suite, issue history, or downstream users to validate behavior, and the repository has about 4 stars with zero dependents. That makes production usage risky and hard to debug. If you use it at all, use it as a checklist of edge cases and verify every generated sitemap in your own tests.
Weaver
How can I help you explore Laravel packages today?