Symfony Bundle Laravel Package

Product Decisions This Supports

• Feature investment: IndexNow submission is a direct lever for search-engine discovery latency. The package covers URL collection, batching, throttling, debounce, optional Messenger dispatch, sitemap integration, verification, and submission history. 0.15.0 adds a shared clock abstraction and a locale-expansion check, improving predictability and configuration safety.
• Roadmap: This is a consolidation release. Shared behavior is moving into indexnowkit/core, indexnowkit/console, and indexnowkit/history, and the same command classes are reused across framework adapters. That is good for long-term maintainability and cross-framework consistency, but it confirms the project is still pre-1.0 and subject to API churn. Plan upgrades as maintenance work, not as zero-cost drops.
• Build vs buy: Strong buy/use case. Implementing the IndexNow protocol, batching, throttling, debounce, multi-locale URL expansion, optional sitemap/verify/history integration, and configuration checks is undifferentiated work. The package already encodes these behaviors and is actively hardening them.
• Use cases: Content-heavy sites, ecommerce catalogs, multi-locale marketing sites, documentation portals, and any Laravel/PHP application publishing URLs frequently enough that search engine discovery time matters.
• Risk and compliance decisions: 0.15.0 fixes a fatal boot when optional packages are absent and masks submission-store credentials in profiler output. Both reduce operational and security risk. The new clock service also enables deterministic tests for debounce, throttle, and submission timing, which supports QA and auditability.
• Customization decision: If your team directly references, decorates, or subclasses the bundle’s command classes, this release forces migration. PM should either budget for that migration or constrain customization to documented extension points such as runners, service decoration, or custom commands registered under the same name.

When to Consider This Package

• You are building on Laravel/PHP or Symfony and want IndexNow submission without owning protocol and client logic.
• You publish URLs at volume and need batching, throttling, debounce, and optional queue/Messenger integration.
• You operate multi-locale routing and need locales: 'all' expansion with guardrails; 0.15.0 adds checks and warnings when framework.enabled_locales is empty.
• You want optional sitemap, verify, and history modules that degrade gracefully when not installed; 0.15.0 fixes a fatal boot path when those packages are missing.
• You can tolerate pre-1.0 semver churn and pin dependency versions (indexnowkit/core ^0.13, indexnowkit/console ^0.5, and indexnowkit/history ^0.4 when installed).
• Look elsewhere if you require a stable 1.0 API, formal SLA/support, non-PHP runtime, or a hosted IndexNow service rather than an in-app library. Also look elsewhere if you heavily subclass or decorate the bundle’s command classes and cannot absorb the migration in 0.15.0.

How to Pitch It (Stakeholders)

• Executive summary: This package automates IndexNow submissions so new and updated pages are discovered faster by search engines. 0.15.0 hardens the integration: optional modules no longer crash application boot, credentials are masked in profiler output, and multi-locale configuration mistakes now surface as warnings instead of silently producing incorrect URLs. It is a low-cost, open-source lever for SEO freshness.
• Engineering summary: 0.15.0 consolidates duplicated classes into indexnowkit/core, indexnowkit/console, and indexnowkit/history. Commands are now package classes registered under the same names, arguments, options, exit codes, and --json behavior. The main breaking changes are removal of the bundle’s Command\* classes, Check\LocalesCheck, Check\EntitySampler, Check\SampleOptions, and Check\VerifySampleCheck; a FlushListener constructor signature change; and a MessengerDispatcher constructor change. Migration is straightforward unless you directly reference those classes. Upgrade requires indexnowkit/core ^0.13, indexnowkit/console ^0.5, and indexnowkit/history ^0.4 when installed.
• Recommendation: Adopt for teams that publish frequently and can pin versions. Upgrade to 0.15.0 with a short migration pass. Do not adopt yet if you require 1.0 API stability or deep customization of internal command classes without accepting future upgrade work.