Sin impuesto Con impuesto
RKR IndexNow Best: Notify search engines of every change and measure your products with Search Console

RKR IndexNow Best: Notify search engines of every change and measure your products with Search Console

Price: €108.78
First year:€108.78tax incl.
From the second year:€27.20/yeartax incl.
  • One year of technical support and lifetime updates; from the second year, support is extended for €27.20/year and includes taking on your general improvement ideas for the module.
  • Renews automatically; cancel whenever you want, with no minimum term.
One-time payment:€108.78tax incl.
  • One year of technical support and lifetime updates; after that, support ends (with the subscription it is extended for €27.20/year).
  • A single payment, with no automatic charges.
€89.90 + VAT = €108.78

Notifies Bing, Yandex, Seznam, Naver, and Yep as soon as a product, category, CMS page, brand, or supplier changes, or when a price changes or a product is out of stock, without interrupting the save process : a single request per save, with retries, exclusions, and manual catalog submission. Within each product page in the back office, you'll find clicks, impressions, CTR, average position, and the top 10 Search Console queries. A 12-tab panel with multi-store health, 7 charts, and 23 themes; optional Google Indexing API and Bing Webmaster channels. Rekire module, tested on PrestaShop 1.7.8 , 8.2, 9.0, and 9.2.

Compatible with PrestaShop 1.7.8 to 9.2, with PHP 7.1 to 8.3.

Share

Technical SEO and visibility

You change a price or list a product. And search engines take a while to find out.

Until a crawler visits your store again, the search results will still show yesterday's price or a product you no longer sell. RKR IndexNow Best It notifies search engines as soon as something changes, and shows you within each product listing how many clicks and what searches it receives from Google.

5 search engines
receive notice of each change: Bing, Yandex, Seznam, Naver and Yep, with a single submission to IndexNow
1 request
Because it's saved, it's sent to the end: saving a product doesn't wait for any search engine.
10 queries
Key metrics for each product, including clicks, impressions, CTR, and average position, can be found within its back-office record.

/ Your store notifies you automatically, without you even having to remember.

When you create, edit, deactivate, or delete a product, category, CMS page, brand, or supplier, the module detects it and notifies search engines with the exact address that has changed. There's no button to press and nothing to remember after each edit. Products and categories are enabled by default; CMS pages, brands, and suppliers are just a switch away.

Price changes
If a product's price changes, you'll be notified. The module compares the new price with the price in the database before saving, so it alerts you to a real change, not just any saved price.
Out of stock and back in stock
You'll be notified when a product is out of stock or back in stock, not with every unit sold. This notification is disabled by default: you can enable it in the Automation tab, just like the notifications for CMS pages, brands, and suppliers.
What is deleted does not remain in the index
Deactivation and deletion always include a notification. When deleting a product, category, or page, the address is saved before it disappears, and a notification is sent in all available languages so that search engines can remove it.
One address per language
In a multilingual store, notifications are sent for each active language, so hreflang variations are also tracked. If you prefer fewer notifications, you can limit them to the default language or the language of your session.

/ Saving is still just as fast

Notifications are not sent while saving. The module records the changes and sends them only once, at the end of the request, in a single transmission to all addresses. Imports and bulk actions don't wait for anyone.

Three ways to send
Instant (right after each save), queue only with manual submission, or queue plus cron job. The third option is recommended for large imports and catalogs: a single cron job serves all stores in the facility.
Re-attempts with a head
If a search engine doesn't respond or tells you to slow down, the module waits and tries again. The wait time doubles with each attempt, up to a maximum of six hours; by default, three attempts are allowed after 60 seconds. A permanent error (400, 403, 404, or 422) is not retried: it's marked as failed on the first attempt to avoid wasting requests.
If one search engine complains, the rest continue.
By default it is sent to api.indexnow.org, which distributes the notification. If you prefer to send it to each search engine separately, an address counts as delivered as soon as one accepts it, and another responding "too many requests" doesn't cancel the entire batch.

/ You decide what gets sent

Exclusions with counter per rule
Write one rule per line: text, wildcards * and ?, anchors ^ and $, or a regular expression prefixed with regex:. Each match is counted and attributed to its rule, and the panel shows you how many addresses were left out today. This way, a poorly written rule won't eat up the entire catalog without you noticing.
Products deactivated, out by default
Deactivated products, categories, and pages are not announced unless it is a deactivation or deletion, which is always announced.
Manual submission
Paste URLs, one per line (up to 1,000), for campaign landing pages, URLs migrated from another platform, or pages from another module. URLs that are not on your domain will be rejected locally, without wasting a request.
Complete catalog, in batches
To notify everyone at once (after a migration, for example), there's a "Send full catalog" button. It's done in batches, so a large store doesn't run into the server's maximum processing time.

/ The key to IndexNow, without touching files

IndexNow requires a key published as a text file in the root directory of your domain. The module generates it (32 characters), publishes it automatically, and includes it in every submission. The "Verify via HTTPS" button downloads it from the internet, just like a search engine would, so you know it works before you trust it.

A practical detail. The only file the module writes outside its folder is that key in the root directory. If your hosting provider has the root directory set to read-only, upload it yourself via FTP and click "Verify via HTTPS".

/ Search Console within each product's page

You connect your Google account once, and when you open any product in the back office, the "Search Console for this URL" block appears with clicks, impressions, CTR, average position, and... Top 10 questions From that address. Without leaving the file, without opening another tab to cross-reference data.

The property chooses itself.
After connecting, the module reads your Search Console properties and chooses the one that covers your store, whether it's a URL prefix or a domain.
Careful data
Page totals are calculated by Google, using your chosen analysis window (28 days by default). They are cached (6 hours by default) to avoid exceeding your Google quota, and you can click "Update Metrics" whenever you want.
Notify from the record itself
In the same section you have "Notify search engines now", to force the notification of that product without waiting for the next save.
Store overview
The dashboard statistics add up the clicks and impressions from the entire store.

/ Google and Bing, as a complement

IndexNow is used by Bing, Yandex, Seznam, Naver, and Yep. Google is not among the destinations. Therefore, the module offers two optional channels, disabled by default:

Google Indexing API
With a Google Cloud service account. It has a limit of 200 addresses per day, and the module lets you specify how much of that quota you want to spend and on which events (recommended: additions and deletions). It tracks usage each day.
Bing Webmaster
Using your Bing Webmaster Tools API key. The test button reads your site's actual daily quota without using up your email sending time, and sends in blocks of up to 500 addresses.
Signed Webhook
If you want to be notified in Slack, n8n, Make or your own system, each module decision can be sent to a public address with an HMAC-SHA256 signature in the X-Rkr-Signature header, so the recipient can verify that it comes from your store.

Honesty about Google. Google documents its Indexing API only for job postings and live streams. It works for products, but it falls outside of that documented use, so we don't sell it as a replacement for anything: it's a plugin you use at your discretion. What Google does for you with this module is provide you with its Search Console data.

/ A panel with everything in view

In Rekire MODULES → IndexNow and Search Console You have 12 tabs: Main Panel, IndexNow, Automation, Search Console, Google Indexing, Bing Indexing, Themes and Styles, Statistics, Queue, Logs, Data and Tools, and Guide.

Multi-store health
One traffic light per store with the following information: master switch, shipping mode, queue status, pending retries, and active channels.
7 charts
Submissions to IndexNow, queue vs. delivered, Search Console trends, alerts by content type, submissions by search engine, HTTP responses, and most searched queries, with ranges of 7, 30, and 90 days. No external libraries.
Queue and registration
Each address includes its status, the search engine it was sent to, and the HTTP response. Retry failed attempts, a selection, or all attempts, and export the queue to CSV.
JSON backup
Export and import Search Console settings, queue, logs, statistics, and cache to move them to another store. The copy does not include credentials or the IndexNow key.
Demonstration data
Install 89 days of sample statistics, queue, logs, and cache from Search Console to browse all the charts before you have your own data, and remove them whenever you want without touching the real data.
23 themes and an optional badge
The panel is dressed with 23 topics Customize it to your liking. If you wish, you can display a "Search Engine Notifications" badge to your visitors, showing the date of the last submission and with a customizable animation. It is disabled by default.

/ Multi-store, multi-language, and trial copies

The IndexNow key and cron token are for the entire installation; everything else (switches, exclusions, channels) is configured per store. The panel is available in Spanish and English. And if you copy your store to another domain for testing, the copy stop warning yourself Until you save the panel to the new domain: your test environment does not fill the search engine index with fake addresses.

/ Security

Each action in the panel requires employee profile permission for the module tab, is sent via POST, and includes a random session code in addition to the PrestaShop token. Credentials (Search Console, Google account, Bing key, and webhook secret) are stored encrypted with your store's key and are never sent back to the browser. The cron job has its own random token, and the webhook only reaches public addresses and does not follow redirects.

/ What you should know

IndexNow provides a notification; it's up to each search engine to decide whether and when to index a URL. The module doesn't promise rankings or timelines: it simply eliminates the wait for a crawler to visit and gives you the data to see what works.

You don't need an account for IndexNow. For Search Console, you need to create OAuth credentials in Google Cloud Console and copy the redirect address shown by the module into them; the Guide tab has the steps. Google Indexing and Bing Webmaster Tools also require their own account or password.

We recommend scheduling the cron job on your hosting if you frequently import products or have a large catalog; the exact address, along with its token, is in the main panel.

Compatible with PrestaShop 1.7.8 version 9.2, with PHP 7.1 to 8.3, multi-store and multi-language

Developed and maintained by REQUIRE

  • Reference
    rkrindexnowbest

v1.7.0

Full review of the 1.6.3 , tested end to end (78 checks: saves, price changes, deactivations, deletions, stock, retries, queue, catalogue, Bing, Search Console, webhook, demo data, backup) on PrestaShop 1.7.8.11 , 8.2.8 , 9.0.0 and 9.2.0 , single shop and multistore.

Fixed

  • Credentials were never usable: the Search Console secret, the Bing API key, the Google service account and the webhook secret were stored with a one-way hash ( 1.7.8 / 8.x) or could not be saved at all (9.x), and saving the Google account left the panel unable to open. They are now encrypted with the shop key and read back; the unreadable values of older versions are cleared on upgrade so they can be typed again.
  • Every upgrade reset the configuration of single-shop stores (IndexNow key, cron token, exclusion rules, credentials). The key and the cron token are now installation-wide and an upgrade never overwrites a stored value.
  • In multistore the key and the cron token were invisible to every shop: nothing was sent and the cron answered 403.
  • Queue rows could be updated in the wrong place (the id of another table was read after an insert), leaving URLs pending forever.
  • Price changes and deactivations were never detected (the values were read after the save). They are now compared with the database before the save.
  • A save no longer waits for the search engines: hooks only queue, and the URLs of the request are sent once at the end, in a single bulk request, after the page has been answered. Imports and mass actions no longer time out.
  • Always the JSON form of the protocol with keyLocation : single URLs of shops installed in a subfolder were rejected (403).
  • A URL counts as delivered when one engine accepts it; one engine answering 429 no longer fails the whole batch. Only api.indexnow.org is selected by default (the engines share what they receive).
  • CMS pages were notified in the wrong language; manufacturer and supplier URLs used the domain of the current shop.
  • Deleted products, categories and pages are notified in every language (their URLs are captured before the deletion).
  • Two drains at the same time (two crons, the cron and a save) no longer send the same rows.
  • Retries waited hours instead of seconds when PHP and MySQL run in different time zones.
  • An exclusion rule added later no longer blocks the head of the queue.
  • Exclusion rules lost their line breaks when saved.
  • Demo data was sent to IndexNow by the cron and removing it deleted the real figures of the day; it never touches real rows any more.
  • Bing Webmaster: the API key was sent in a header and every request failed. The test now reads the real daily quota of the site without spending submissions.
  • Google Indexing API: the test no longer spends quota (ownership check), the signed assertion is only ever sent to Google and the property is optional.
  • Search Console: fixed redirect URI (shown in the panel to copy into Google Cloud), random single-use state, tokens per shop, the property of the shop is chosen automatically, page totals as Google computes them and the access is revoked when disconnecting.
  • The Search Console trend chart showed one spike instead of the daily figures (and every sync added 28 days of clicks to the current day): it now stores the daily clicks, impressions and position of the whole property.
  • Export/import did nothing from the panel; a backup no longer carries secrets nor the IndexNow key, and importing applies the same rules as the panel.
  • Front office: 500 error on every page with the badge on (PrestaShop 9); stray text printed under the badge; badge styles not loaded.
  • Product page block without its scripts on PrestaShop 8 / 9.
  • Texts with "&" or quotes showed HTML entities on PrestaShop 1.7.8 / 8.x.

Security

  • Every panel action checks the permission of the employee profile (view / edit / delete), accepts POST only and uses a random per-session nonce.
  • Webhook: no redirects, the vetted address is pinned for the request (no DNS rebinding), carrier-grade NAT and other internal ranges blocked.
  • Queue and log purges only touch the shop of the context.

Changed

  • Stock trigger: only when a product sells out or comes back in stock, not on every unit.
  • A copy of the shop moved to another domain (staging, local copy) stops notifying until the panel is saved there.
  • One cron line serves every shop of the installation; it drains the Google and Bing queues and refreshes Search Console when the panel says so.
  • The full catalog is queued in batches (no time limit on large shops).
  • Own menu trait, PrestaShop Addons rules (no Context:: , no hash_hmac , no nofilter , .htaccess , license), translations completed (501 strings in Spanish).

4 other products in the same category

RKR Mix & Match: custom boxes for PrestaShop
rkrmixmatchbox
€108.90
€90.00 + VAT = €108.90
Blog

Questions and answers

Nobody has asked anything about this product yet.

Loading...
Cookie consent
Back to top