- How do I install and configure andrey-helldar/sitemap in Laravel?
- Install it with Composer, then publish the package config and define the route or generator that maps your content to sitemap entries. The package is framework-native, so it registers a service provider and facade without adding another runtime. Before deploying, confirm the illuminate/* and php constraints in composer.json match your application.
- Which Laravel and PHP versions does andrey-helldar/sitemap support?
- Release v5.5.0 adds Laravel 9 support, while earlier 5.x releases target older Laravel versions. The practical envelope described for this package is Laravel 8/9 with PHP 7.3 to 8.1, but you should verify the exact illuminate/* and php constraints in composer.json for your runtime. Do not rely on the release title alone for compatibility.
- Does andrey-helldar/sitemap support multiple sitemap files and automatic sitemap indexes?
- Yes. The package supports multiple sitemap files and automatic index creation, which helps split large sites into crawlable sitemap sets. Confirm how your version handles the 50,000-URL and 50MB protocol limits, and validate the generated index and child sitemap URLs before production.
- How do I customize sitemap URLs with lastmod, changefreq, and priority?
- Build your sitemap by mapping content models to URL entries and setting lastmod, changefreq, and priority values in the generator. Keep the values accurate and consistent: changefreq and priority are hints, not guarantees, and lastmod should reflect real content changes. Review the package config and tag or view overrides if you need custom output.
- Can I cache generated sitemaps with andrey-helldar/sitemap?
- The package includes caching support as part of its configuration, so you can avoid regenerating the same sitemap on every request. Use a cache store shared by your application nodes and clear or warm the cache when content changes. For large sites, pair caching with scheduled generation rather than request-time generation.
- Can sitemap generation run in a queued job or scheduler instead of on every request?
- The sitemap builder is invoked through the package facade and routing helpers, so typical production setups generate it from a scheduled command rather than a user request. You can dispatch generation from a queued job if your generator and output paths are safe to run in a worker. For large sitemap sets, prefer scheduled or queued generation and serve the resulting files or cached responses.
- How do I migrate from laravelium/sitemap to andrey-helldar/sitemap?
- Treat the migration as a rename plus refactor, not a drop-in replacement. Remove the old package, update namespaces and facade aliases, republish and diff the config, and re-verify every tag or view override. The config diff is often the real work because config keys and namespaces differ from the ancestor.
- Does andrey-helldar/sitemap work with Laravel 10 or Laravel 11?
- The release context only confirms Laravel 9 support in v5.5.0; it does not confirm Laravel 10 or Laravel 11 compatibility. Check composer.json and the issue tracker before planning a major Laravel upgrade, and expect framework support to lag behind new Laravel releases. Pin the package version and test the generated sitemap after any upgrade.
- Is andrey-helldar/sitemap actively maintained and safe for production?
- The project has a single maintainer and a first-time contributor on the Laravel 9 compatibility change, with no formal support channel or release policy described. That creates schedule and bus-factor risk, especially for future Laravel upgrades. Pin versions, review changelogs, run your own validation, and consider alternatives such as spatie/laravel-sitemap, a custom Laravel command, or a managed sitemap service if maintenance risk is unacceptable.
- How should I test and validate sitemap XML generated by andrey-helldar/sitemap?
- Add a Laravel feature test that requests your sitemap route and asserts the XML response and expected URLs. Validate index references, URL counts, lastmod formats, and the 50,000-URL or 50MB limits where relevant, and re-run validation after content or config changes. Also verify that robots.txt points to the correct sitemap URL and that caching does not serve stale entries.