- How do I install ultrono/laravel-sitemap in a Laravel app?
- Install it with Composer using composer require ultrono/laravel-sitemap, then rely on Laravel package auto-discovery for the service provider and facade. Publish the package config if one is provided and review the defaults before generating your first sitemap. Because the public repository is listed as unknown, verify the actual composer.json constraints and package contents before committing to a version.
- Does ultrono/laravel-sitemap support Laravel 11, 12 and 13?
- The package description claims support for Laravel 11, 12 and 13. The Laravel 13 claim combined with the stated release date suggests forward-looking compatibility, so confirm the real constraints in composer.json rather than trusting the description alone. Pin an exact version and add the Laravel version you use to a CI matrix so future upgrades surface conflicts early.
- How do I add routes and Eloquent models to the sitemap?
- The expected pattern is a URL-collection interface that lets you register plain URLs, crawl application routes, or supply model records that expose a URL via a contract similar to HasUrl. Confirm the exact method names and contract in the package source before building against them. Sitemap generation is an application-boundary concern, so you should not need changes to your domain models beyond implementing that URL contract.
- How do I serve sitemap.xml from a Laravel route?
- The normal approach is a thin controller endpoint that returns the generated XML, or a route that serves the file written to a Laravel filesystem disk. You can point output at local storage or S3 and serve it through a route, queue job or CDN. Set the correct XML content type and confirm the behavior with the specific filesystem disk you use.
- Can I schedule sitemap generation with Laravel's scheduler?
- Yes, sitemap generation fits naturally as a scheduled console job in Laravel. Wire the command into your scheduler, write the output to a storage disk, and make sure the target directory is writable by the application. If you serve the file through a CDN, account for cache invalidation after each regeneration.
- Does it handle large sitemaps, index splitting and gzip?
- The technical evaluation flags these as open questions rather than confirmed features. The sitemap protocol limits a single file to 50,000 URLs and 50MB uncompressed, so verify whether the package automatically splits into a sitemap index and supports gzip. Also check whether generation streams output or holds everything in memory on large route sets, and spike this on a representative URL subset before adopting it.
- What license is ultrono/laravel-sitemap released under?
- The license is reported as NOASSERTION, meaning a license file exists but is not machine-recognizable or is custom or ambiguous. Do not assume MIT. Legal review is a hard gate before any production merge, and the license must be resolved and confirmed as OSI-approved where required.
- Is ultrono/laravel-sitemap a fork of spatie/laravel-sitemap?
- The feature set and framing strongly suggest a fork or reimplementation of spatie/laravel-sitemap, but this is not confirmed. Before migrating, check API parity for the generator, facade and HasUrl contract, and identify the concrete delta that justifies choosing this package over upstream. If upstream already supports your Laravel version, prefer upstream and adopt this only where it demonstrably covers a gap.
- How do I set priorities and change frequencies for URLs?
- The package blurb states that you can control priorities and change frequencies through a simple API. Sitemap priorities use values from 0.0 to 1.0 and change frequencies use the standard always, hourly, daily, weekly, monthly, yearly and never values. Verify the exact method names and whether defaults are applied to route-crawled or model-based URLs.
- Is ultrono/laravel-sitemap safe for production use?
- Treat it cautiously: the public repository, CI, tests and issue tracker cannot be verified, the license is NOASSERTION, and a small star count suggests an unproven bus factor. The integration itself is low effort, but legal and supply-chain gates should be closed before production. Pin an exact version, record it, and review recent commits and tests if the source becomes available.