Sitemap Bundle Laravel Package

Product Decisions This Supports

• Technical SEO roadmap: A sitemap generator with per-route changefreq and priority turns "improve organic discoverability" from a backlog epic into a small, shippable configuration task. It supports prioritization decisions about which content surfaces (marketing pages, listings, CMS entries) are worth indexing effort first.
• Build vs. buy for sitemap infrastructure: With route-level frequency/priority control available in-package, the default answer shifts toward "build in-app" rather than paying for a third-party SEO sitemap service or hand-maintaining XML files. This is a cost-reduction and vendor-consolidation decision, not just a feature decision.
• Content and IA decisions: Explicitly assigning priority per route forces the team to state, in code, what the product considers most important. That artifact is useful for content strategy debates ("is the pricing page or the blog index more important?") and keeps IA decisions reviewable in pull requests rather than in a marketing spreadsheet.
• Launch readiness checklists: Sitemap generation is a recurring gate for new site launches, locale rollouts, and marketplace/catalog expansions. Having it as a package dependency makes it a repeatable step rather than launch-specific engineering work.
• Roadmap sequencing for programmatic/SEO-driven pages: If the roadmap includes large-scale generated landing pages or directory-style content, this package is a prerequisite enabler and should be sequenced before those pages ship.

When to Consider This Package

Consider it when:

• The application is Laravel-based and routes are the source of truth for indexable URLs, so sitemap entries can be derived rather than duplicated.
• You need per-URL changefreq and priority control, which implies a heterogeneous site where a one-size-fits-all sitemap is inadequate.
• You want the sitemap to stay in sync with code automatically — new routes get covered without a separate manual publishing step.
• Your content set fits comfortably in a single sitemap (roughly under 50k URLs) or you are prepared to verify sitemap-index/splitting behavior yourself.

Look elsewhere or proceed cautiously when:

• Version maturity is the main risk. This is a 0.2.0 release, the second minor version of a pre-1.0 package. Expect breaking changes between minor versions, and treat the public API as unstable. If you cannot absorb upgrade churn, prefer a mature alternative or a thin in-house implementation.
• The release notes describe only the core generation capability. There is no signal here about sitemap indexing for large sites, lastmod handling, gzip output, image/video/news sitemap extensions, sitemap caching, multi-domain or multi-locale handling, or XML escaping and URL validation edge cases. Validate these against your requirements before adopting.
• You need an admin-editable sitemap (marketing wants to add URLs without a deploy) — this is a code-driven, route-based tool and will fight that workflow.
• You are not on Laravel, or you need sitemap generation decoupled from your routing layer.
• The site is small and static enough that a hand-written XML file or a one-off Artisan command is genuinely cheaper to own than a dependency.

Recommendation: worth a time-boxed spike, not a committed adoption. Prototype against a representative route set, confirm lastmod, caching, and large-site behavior, and pin the exact version in composer.json with a note that minor bumps may break.

How to Pitch It (Stakeholders)

For executives: This is a small, low-cost dependency that makes our pages easier for search engines to find and prioritize, using configuration we already have in code. It removes a manual step from every site launch and gives us route-level control over which content we ask search engines to crawl first. The cost is negligible; the risk is that the package is early-stage (version 0.2), so we should trial it on one property before standardizing. Upside is better organic discoverability and one less recurring manual task; decision needed is a short engineering spike, not a budget line.

For engineering: A Laravel package that generates the sitemap from our route definitions, with changefreq and priority set per route. It keeps the sitemap aligned with the actual route table, so it stops drifting the moment someone adds a page. It is pre-1.0, so the API is not stable — pin the version and expect to absorb breaking changes on minor releases. Before we commit, we need to confirm three things it does not appear to cover in this release: sitemap splitting or an index file past ~50k URLs, lastmod accuracy, and caching so we are not regenerating XML on every request. If those check out, this replaces roughly a day of bespoke work plus ongoing maintenance.