IndexNow Submission for Magento 2

No. Google does not participate in IndexNow and has stated they maintain their own crawl schedule. For Google indexing, use a proper XML sitemap and Google Search Console. This module is specifically for the IndexNow ecosystem (Bing, Yandex, Seznam, Naver, Yep).

No, that's the point of IndexNow. One key, submitted to api.indexnow.org, fans out to every participating engine. Generate the key once at Bing IndexNow or Yandex IndexNow and paste it into Magento.

https://yourstore.com/panth_indexnow/key, IndexNow crawlers hit this URL to verify domain ownership before trusting submitted URLs.

The HTTP call times out after 15 seconds, the failure is logged to var/log/system.log, and the save that triggered it completes normally. No admin-facing error, no retry queue, the next save attempts a fresh submission.

No. The observer only enqueues URLs during save and fires the actual POST in register_shutdown_function, after Magento has already sent the response to the admin. The merchant's Save button returns at normal speed.

Yes. IndexNow operates at the backend event layer (catalog_product_save_after, etc.), it's theme-agnostic. Runs identically on Hyvä, Luma, or any Magento 2 theme.

IndexNow is per-URL, not per-sitemap, Bing already polls your sitemap separately. If you want to force a re-crawl of a specific URL (not triggered by a save), you'd need a custom CLI command; this module doesn't ship one in v1.0.

Yes. mage2kishan/module-core is a required dependency and is pulled in automatically by Composer. Core provides the admin tab layout and common utilities.

Yes. Every configuration setting respects Magento's standard scope hierarchy (default → website → store view). Set different keys per store view, per website, or one default key globally, whichever fits your setup.

Not submitted. IndexNow is designed for new or changed content. Deletions are detected by search engines through normal re-crawl when they hit a 404 on the next visit to the URL.