IndexNow Submission for Magento 2

What you get

Key Features

Automatic URL Submission

• Product saves auto-submit the product URL to IndexNow the moment an admin clicks Save
• Category saves auto-submit the category listing URL
• CMS page saves auto-submit the rewritten canonical CMS URL (respects custom URL rewrites + configured suffix)
• Single request batching — multiple entity saves in one admin action fire one batched POST, not one per entity
• End-of-request flush via register_shutdown_function — observer stays out of the critical path, merchant's save button returns instantly

Per-Store API Keys

• Scope-aware — configure one key per website or store view
• Correct host in every payload — each store's submission uses its own host, key, and keyLocation
• Single default key works too — set it once at Default Config and every store inherits

Built-in Key Verification Endpoint

• /panth_indexnow/key — IndexNow's required verification URL, served as plain text from the admin-configured key
• Optional ?key=<value> query param — lets crawlers pre-validate with timing-safe comparison; mismatches return 404 so the endpoint can't be abused as an arbitrary text echo service
• Auto-404 when disabled — if the feature flag is off or the key is empty, the endpoint returns a clean 404
• Module-owned frontName — uses panth_indexnow as its route's frontName so the module never shares a route registration with other modules (no controller resolution races)

Safe Defaults

• Disabled by default — must be explicitly enabled in admin so a fresh install doesn't start submitting URLs until you're ready
• ACL-gated (Panth_IndexNow::config) — only roles with the permission can see / save the settings
• Per-store toggle — enable globally and disable on specific store views (or vice versa)

Defensive HTTP Client

• 15-second timeout — won't hang the admin request if IndexNow is slow
• Full error logging — HTTP status + response body logged to var/log/system.log for post-mortem
• Never re-throws — a failed submission never crashes the entity save that triggered it

Which Search Engines Does It Cover?

IndexNow has a defined list of participating search engines. Submission via api.indexnow.org is fanned out to all of them:

Note on Google: Google has its own crawl schedule and doesn't accept IndexNow submissions. To speed up Google indexing, pair this module with an XML sitemap (e.g. mage2kishan/module-xml-sitemap) and use Google Search Console. This module is for Bing / Yandex / Seznam / Naver / Yep — the search engines that actually honor IndexNow.

How It Works — Under the Hood

The module is deliberately small (three classes — an observer, a submitter, and a controller) and leans on Magento's native event system rather than inventing a scheduler:

 ┌────────────────────┐ save_after event ┌─────────────────────┐
 │ Admin saves a │ ─────────────────────▶ │ EntityChangeObserver│
 │ product / category │ │ │
 │ / CMS page │ │ - resolves URL │
 └────────────────────┘ │ - collects in batch │
 │ - registers flush │
 └──────────┬──────────┘
 │
 │ PHP shutdown
 ▼
 ┌─────────────────────┐
 │ Submitter │
 │ │
 │ POST api.indexnow. │
 │ org/IndexNow │
 │ │
 │ { │
 │ host, key, │
 │ keyLocation, │
 │ urlList[] │
 │ } │
 └──────────┬──────────┘
 │
 ▼
 Bing, Yandex, Seznam,
 Naver, Yep

Design decisions:

• End-of-request flush — the observer doesn't POST on every save; it accumulates URLs per-store in a static array and fires one batched request in register_shutdown_function. A merchant saving 5 product edits in one admin action gets 1 POST, not 5.
• Store-scoped batching — multi-store saves to different stores fire one POST per store (each with its own key + host), batched by store.
• No database writes — no queue table, no pending table. State lives only in the PHP request that triggered it. If PHP-FPM dies mid-request the batch is lost, but that's an acceptable trade-off for zero-infrastructure operation.
• Never blocks — the save button returns the moment the entity is written. The IndexNow POST happens after Magento has already sent the response.

What Triggers a Submission?

The Key Verification Endpoint

IndexNow requires the domain being submitted to serve the API key as a plain-text file at a declared URL. The module serves this automatically at:

https://yourstore.com/panth_indexnow/key

Accepted URL forms:

The key comparison is timing-safe via hash_equals — the endpoint resists timing-attack key discovery.

Multi-Store Support

The module is fully scope-aware:

• Default key — set once at Default Config, inherited by every store
• Per-website key — set at Website scope for brand-specific keys
• Per-store key — set at Store View scope for the most granular setup

Each submission uses the correct key + host + keyLocation for the store the entity belongs to. Saving a product assigned to Store A and a CMS page assigned to Store B in one admin action triggers two POSTs — one per store — each with that store's own key.

Hyva store → POST {host: hyva.test, key: hyva-key-..., keyLocation: https://hyva.test/panth_indexnow/key}
Luma store → POST {host: luma.test, key: luma-key-..., keyLocation: https://luma.test/panth_indexnow/key}

Troubleshooting

Compatibility

Installation

Composer Installation (Recommended)

composer require mage2kishan/module-index-now
bin/magento module:enable Panth_Core Panth_IndexNow
bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy -f
bin/magento cache:flush

Manual Installation via ZIP

1. Download the latest release ZIP from Packagist or the Adobe Commerce Marketplace
2. Extract the contents to app/code/Panth/IndexNow/ in your Magento installation
3. Ensure Panth_Core is installed (required dependency)
4. Run the same commands as above starting from bin/magento module:enable

Verify Installation

bin/magento module:status Panth_IndexNow
# Expected output: Module is enabled

Get an IndexNow API Key

1. Visit Bing IndexNow or Yandex IndexNow
2. Generate a UUID-style key (e.g. a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6) — or invent any 8+ character hex string; IndexNow generates new keys per-site
3. Paste the key into Magento admin → Stores → Configuration → Panth Extensions → IndexNow → API Key
4. Save and flush the cache — submissions begin on the next catalog / CMS save

Configuration

Navigate to Admin → Stores → Configuration → Panth Extensions → IndexNow to configure the module.

Both settings are scope-aware — configure one key globally or set different keys per store view if you manage multiple brand domains from one Magento install.

License

Panth IndexNow is licensed under a proprietary license — see LICENSE.txt. One license per Magento installation.