Weave Code
Statamic Sitemap Laravel Package
mitydigital/statamic-sitemap
A Statamic addon that generates XML sitemaps for your site, automatically including entries, taxonomies and custom URLs, with support for multiple sitemaps and a sitemap index for larger sites.
A simple XML sitemap generator for Statamic
Frequently asked questions about Statamic Sitemap
- How do I install mitydigital/statamic-sitemap in a Laravel application?
- Install it with Composer using composer require mitydigital/statamic-sitemap, then let Statamic addon discovery register it or add it to your addon configuration if your setup requires it. Publish the addon config, define the collections, taxonomies, and custom URLs you want included, and expose the sitemap route. Because it is a Statamic addon, the application must already use Statamic as its CMS layer.
- Does mitydigital/statamic-sitemap work in a plain Laravel app without Statamic?
- No. It is a Statamic addon rather than a standalone Laravel package, so it fits Laravel applications that use Statamic for content and routing. A non-Statamic Laravel app, a headless-only architecture without Statamic routing, or a static-site pipeline that already generates sitemaps is a poor fit.
- Which Statamic, Laravel, and PHP versions are supported by version 3.5.x?
- The evaluation does not list exact version constraints, so check the composer.json of mitydigital/statamic-sitemap and the addon documentation before upgrading. Pin to a tested Statamic major and verify the PHP and Laravel constraints for your application. Test 3.5.x in staging with your actual Statamic version, multi-site configuration, and cache settings before relying on it in production.
- Does the addon support multiple sitemaps and a sitemap index?
- Yes. The addon is described as supporting multiple sitemaps and a sitemap index for larger sites. That makes it suitable when a single sitemap would exceed practical limits or when you want to separate content types. Validate the generated index and child sitemap URLs in staging, especially if you use multi-site or localized content.
- Can I include Statamic entries, taxonomies, and custom URLs in the sitemap?
- Yes. The addon automatically includes entries and taxonomies and also supports custom URLs, which you define during configuration. Publish the config and explicitly list the collections and taxonomies that should appear so you do not expose unintended content. After generation, check URL counts and status codes to confirm that entries, taxonomy terms, and custom URLs are all present.
- How does it handle multi-site and localized URLs?
- The addon is built for Statamic sites and can be configured for multi-site setups, but the technical evaluation flags multi-site and localized URL correctness as a key risk to verify. Generate sitemaps in staging with your real site tree and compare URLs, canonicals, and status codes for each locale. Do not assume the 3.5.1 patch changes multi-site behavior; test it explicitly.
- How is sitemap caching handled, and what invalidates it when content changes?
- The provided overview does not specify caching behavior, so treat caching and invalidation as items to verify in your environment. For large or multi-site content sets, plan to cache the sitemap route and schedule or queue generation if the addon supports it. Confirm what invalidates the cached output when entries, taxonomies, or custom URLs change, and monitor for stale URLs after content updates.
- What changed in version 3.5.1, and does it require a migration?
- Version 3.5.1 is a patch-level bug fix that filters empty results, improving output hygiene. The evaluation expects no new integration surface or migration requirement from this release. Verify what the filtering removes, because silently excluding empty URL entries, sitemap sections, or index entries could mask a misconfiguration. Run a before-and-after diff of generated URLs rather than assuming the change is purely cosmetic.
- How should I test the sitemap before replacing my existing /sitemap.xml route?
- Install and configure the addon in non-production first, then generate the sitemap and validate the XML, URL counts, status codes, and canonical URLs. Run it in parallel with your existing sitemap and diff the URLs, including multi-site and localized content. Use production-like content volume and cache settings in staging, then switch the route with a rollback path and monitor crawl stats and Search Console data.
- What are the main production risks and alternatives to this addon?
- The main risks are compatibility with your Statamic, Laravel, and PHP versions; sitemap correctness on multi-site or localized content; generation performance on large content sets; stale caches; and generation errors returning 5xx on the sitemap route. The 3.5.1 empty-result filtering could also hide a misconfigured section, so add validation, URL-count monitoring, and alerting. Alternatives include an existing sitemap solution in your stack or a custom Statamic route or template, but compare generated URLs and performance before switching. If you need a non-Statamic Laravel package, this addon is not the right fit.
Weaver
How can I help you explore Laravel packages today?