What can we help you with?

From 1.7.6 to 9.x. It installs like any other module, by uploading the zip from the back office: no console, no composer, no touching your theme's files.

Whichever one your shop already runs. It does not force you to change version in order to install it.

Yes, and in two ways. If your theme already has a search box, the module hooks into it and shows the results underneath. If you prefer its own, it builds a full-screen one over the shop.

Product cards are rendered with your template, so there is no second design to maintain.

No. It hooks in through PrestaShop's hooks and adds its own CSS and JS. Uninstall it and your shop goes back to its usual search.

You can ask for a new link at Recover access, giving the email address you registered the shop with.

One thing to bear in mind: we do not store your keys in the clear —which is why we cannot resend them— so we generate new ones and the previous ones stop working. If you already had the module running, it will stop syncing the catalogue until you paste in the new configuration. Your shop's searches keep working in the meantime.

Almost always the cache. PrestaShop keeps templates already compiled and carries on serving the old ones, so the module is installed correctly but cannot be seen.

Clear it from the back office, under Advanced parameters → Performance → Clear cache. Do it from there and not from the console: if your server uses APCu or similar, the command-line cache is a different one from the web's, and clearing one does not touch the other.

If it still does not show up after clearing it, open the module's configuration: it checks the hook points by itself and puts back any that are missing, telling you what it repaired.

A scheduled task syncs it. In the Index tab you have the exact line to add to your hosting's cron.

Until it runs, the search keeps showing the previous catalogue: new products do not appear and price or stock changes are not reflected. If you notice that, it is almost always the cron not running.

Yes, and also by each combination's references, not just the parent product's. You decide how much each field weighs in the Relevance.

There are two modes. From the index is the fast one and works for most shops: the price is updated when the product is saved and is the same for everyone. Exact per customer respects groups, currencies and dated promotions, in exchange for querying your database.

The setting governs the search and the filters at once, so the same product never shows two different prices.

Yes. Each language has its own index, and that is why languages count towards the plan: what takes up memory is products × languages.

Each query to the index. Searching and filtering cost the same — which is why the unit is called a request and not a search.

Anything served from your own server's cache does not count, because it never travels. Measured on a real shop: typing a word is five requests for the first visitor and zero for the ones after with the same text.

You see it flagged in your back office before anything happens.

And you decide what to do if it comes to that: carry on searching with PrestaShop's search —the shop keeps a search box, the usual one, until the quota renews— or drop it altogether. The first is the default.

The same: the shop falls back to PrestaShop's native search. You are never left without a search box because of a problem at our end.

No. Thirty days free, no card. If it does not convince you, you have left nothing behind.

The catalogue goes to the index: name, reference, barcode, brand, categories, short description, price and image.

Analytics is optional and can be switched off whenever you like. If it is on, what is sent is the text searched for, how many results it gave, which product was clicked and whether it ended in an order. No name, email, customer identifier or IP address is sent, nor anything that would allow you to reconstruct who searched for what.

For the better. Addresses with filters are marked as non-indexable and, when you generate the robots.txt from your back office, the module adds only the rules that keep crawlers out of that maze.

It is not hiding anything: those pages add nothing to Google's index —they are variants of a category that is already indexed— and they do cost you server.

One of its own, dropdownsearch_attr, seven days, only so a search can be tied to the order it leads to. It is not shared with third parties and is not used for advertising, but it is worth mentioning in your cookie policy.