Statamic Sitemap Laravel Package

Product Decisions This Supports

• Build vs. buy for SEO surface area: Sitemapamic is a drop-in sitemap generator for Statamic sites. The decision it most directly informs is whether to spend engineering cycles on a bespoke sitemap/SEO-plumbing feature or adopt a maintained addon and redirect that capacity to differentiated work.
• Scope of the SEO roadmap: Establishes sitemap generation, multi-site/multi-locale sitemap indexing, and robots/canonical hygiene as "solved and off the roadmap" — freeing the roadmap for content-modeling, editorial tooling, and performance work instead.
• Release 3.5.1 specifically (patch, low risk): "Filter empty results" is a correctness fix — it prevents empty/blank entries from being emitted into the sitemap output. For a PM this maps to search-quality and crawl-budget hygiene, not a feature. It is the kind of fix that reduces the chance of Search Console warnings and support tickets from content editors, and it carries essentially zero migration or regression exposure.
• Release cadence as a signal: A 3.5.x patch line indicates an actively maintained addon with a stable major version — useful evidence when justifying a dependency in an architecture or vendor review, and when deciding whether to pin to ^3.5 versus pinning an exact patch.
• Use cases it unlocks: Programmatic sitemap generation across large content sets, multi-site Statamic installs needing per-site sitemap indexes, and editorial workflows where content is unpublished/removed and the sitemap must stay accurate without manual intervention.

When to Consider This Package

Adopt when all of the following hold:

• The product is built on Statamic (this is a Statamic addon, not a generic Laravel sitemap package — it will not help a plain Laravel app).
• You need sitemap generation plus a sitemap index across multiple sites/locales, and you want it configured through Statamic's control panel and config rather than in application code.
• Your content is primarily managed by editors through the CMS, so sitemap correctness should follow content lifecycle events automatically.
• You are comfortable adding a third-party dependency to the SEO surface — mitigated here by a patch-level release indicating active maintenance and a stable 3.x API.

Look elsewhere or build in-house when:

• You are not on Statamic. For plain Laravel, spatie/laravel-sitemap or a small custom controller is the better fit.
• You need sitemap features the addon does not cover — e.g. complex per-URL priority/changefreq logic driven by business rules, sitemap generation as part of a headless/API-only architecture, or streaming sitemaps for very large URL counts where you need explicit control over chunking.
• Your policy is to minimize third-party dependencies on SEO-critical paths, or you require a formal support SLA — an open-source addon maintained by a single vendor does not provide one.
• You are on a Statamic version outside the addon's supported range; verify compatibility before committing.

Also note the 3.5.1 change is a bug fix, not a capability — if the current assessment was waiting on a specific feature, this release does not deliver it, and no re-evaluation of the build-vs-buy decision is triggered by this patch alone.

How to Pitch It (Stakeholders)

For executives (one paragraph): We evaluated Sitemapamic, a small addon that generates and maintains XML sitemaps and sitemap indexes for Statamic-based sites. It removes a recurring, low-differentiation engineering task — keeping sitemaps accurate as content is added, edited, and removed — and replaces it with a maintained dependency configured by our editors. The newest release, 3.5.1, is a small correctness fix that prevents empty entries from appearing in sitemap output; it is a maintenance patch with no migration work, no breaking changes, and no user-facing feature. Cost is negligible, risk is low, and it lets the team spend its time on work customers actually notice.

For engineering leads: Statamic-only addon, stable 3.x line, actively patched (3.5.1 filters empty results from sitemap output). No breaking changes and no migration required — a routine composer update within the existing constraint. It handles sitemap indexing across multi-site installs, which is the part we would otherwise have to build and maintain ourselves. Recommended action: adopt at ^3.5, pin the lockfile, and add a smoke test asserting sitemap endpoints return 200 with well-formed XML and no empty <url> entries — so the behaviour this patch fixes stays fixed for us. If we later move off Statamic or need bespoke per-URL priority logic, this is a small, easily excised dependency.