Weave Code
Core Laravel Package
indexnowkit/core
IndexNowKit Core is a Laravel/PHP package that provides essential IndexNow integration, helping your app notify participating search engines about new or updated URLs. It offers a simple core client and API foundation for fast, reliable indexing notifications.
IndexNow client for PHP: notify Yandex, Bing, Naver, Seznam and Yep about changed URLs. Batching, debounce, throttle, retry policy, key file handling. Framework-agnostic (PSR-18/PSR-3/PSR-16); adapters for Doctrine, Symfony, Laravel, Yii2, a sitemap add-on.
Frequently asked questions about Core
- What is IndexNowKit Core and how does it fit into a Laravel app?
- IndexNowKit Core is a lightweight, framework-agnostic PHP library that submits new or updated URLs to search engines using the IndexNow protocol. In Laravel you would wrap its client in a service provider, config file and queued job rather than scattering calls through controllers. It handles key generation, payload formatting and submission to Bing, Yandex, Seznam and Naver.
- How do I install indexnowkit/core in a Laravel project?
- Install it with Composer using the package name indexnowkit/core. There is no official Laravel adapter in this repository, so you add your own service provider, configuration and PSR-18 HTTP client binding. Pin a reviewed version instead of using a floating constraint.
- Which PHP and Laravel versions does IndexNowKit Core support?
- The package is distributed via Composer and is framework-agnostic, so its PHP constraint is defined in its composer.json rather than tied to a Laravel release. Check that constraint against your application's PHP version and run it in CI before adopting it. Laravel version support depends on your own adapter and HTTP client compatibility, not on a vendor-provided Laravel package.
- Do I need a PSR-18 HTTP client to use IndexNowKit Core?
- Yes, the library is built on PSR-18 and PSR-17 HTTP interfaces, so you bring your own compatible client such as Guzzle or Symfony HttpClient. That design keeps it testable because you can inject a mock client in unit tests. Confirm your chosen client and its dependencies match your Laravel project.
- How are IndexNow keys generated and served?
- The package handles API key generation and validation, but you remain responsible for hosting the key file at the location the IndexNow protocol requires for your domain. Keep production and staging keys separate and never expose a production key in local or staging environments. Key rotation and key-file hosting should be covered in your internal runbook.
- Can I submit multiple URLs in a single IndexNow request?
- Yes, IndexNowKit Core supports one-call submission of a single URL or a batch of URLs. You should define your own batch size, split large sets if needed, and review how partial batch failures are reported. Verify the package's payload and batching limits against the current IndexNow protocol.
- Is it safe to use IndexNowKit Core in staging or local development?
- No, you should prevent staging and local environments from submitting production URLs or keys to search engines. Use an environment allowlist and a log-only or no-op driver outside production. This avoids polluting search engines and keeps test data out of IndexNow.
- How should I handle retries and failures when submitting IndexNow URLs from Laravel queues?
- IndexNow is a non-critical outbound SEO signal, so failures should be logged and observable without blocking the user request. Be careful that the package's retry or backoff behavior does not conflict with Laravel queue retries. Review debounce, idempotency and duplicate-submission semantics before enabling it on high-traffic publish events.
- Is IndexNowKit Core mature enough for production use?
- Treat it as a small utility rather than a strategic dependency because it shows low adoption signals, including zero stars and no dependents in the assessment. Pin a reviewed version, inspect the source and test coverage, and be prepared to fork or vendor it if upstream stalls. A conditional pilot behind an internal adapter is the safer path.
- What alternatives are there if I want to replace IndexNowKit Core later?
- You can replace it with a direct PSR-18 HTTP implementation, another IndexNow client, or your own small submission service. The key is to wrap it behind an internal IndexNowSubmitter interface so controllers, models and jobs never depend on the package directly. That keeps migration cheap and lets you keep a fallback driver.
Weaver
How can I help you explore Laravel packages today?