Why did my search count jump in Algolia?

The Algolia help pages give 5 common reasons. The first to rule out: A loop in the site's code can fire search requests over and over, as Algolia's support team notes.

What causes it?

  1. A loop in the site's code can fire search requests over and over, as Algolia's support team notes.

    In the Algolia help: A loop in your code that triggers thousands of search requests. Why has there been a spike in my search usage?, read 2026-11-12.

  2. Pages that refresh on their own can run empty searches each time, raising the count without anyone typing.

    In the Algolia help: Automatic page refreshes that trigger empty searches. Why has there been a spike in my search usage?, read 2026-11-12.

  3. A search box set up to search twice for each action can double the count.

    In the Algolia help: A misconfiguration that sends duplicate or unnecessary requests, such as a widget that searches twice per interaction. Why has there been a spike in my search usage?, read 2026-11-12.

  4. Bots can spread their searches across many addresses, so the extra traffic can be hard to spot from any one source.

    In the Algolia help: Many bots now spread their traffic across hundreds or thousands of IP addresses, each sending only a few requests. Why has there been a spike in my search usage?, read 2026-11-12.

  5. Search engine crawlers visiting search and category pages can add searches too.

    In the Algolia help: legitimate crawlers, such as Googlebot, crawling your search and category pages Why has there been a spike in my search usage?, read 2026-11-12.

How do I check it myself?

  1. Algolia's search logs show where each request came from, which helps tell visitors from automated traffic.

    In the Algolia help: Each request shows its originating IP address and HTTP headers, including the user agent. Why has there been a spike in my search usage?, read 2026-11-12.

  2. Look at the user agent of requests as well as their addresses, since bots can share one address range or spread across many.

    In the Algolia help: Look at user agents as well as IP addresses. Why has there been a spike in my search usage?, read 2026-11-12.

  3. Look for the same query repeated, many requests from one address, or garbled search terms, which can point to bot traffic.

    In the Algolia help: Look for repeated queries, high-frequency access from specific IPs, or malformed search terms. How do I prevent or reduce bot traffic in Algolia Search?, read 2026-11-12.

How does Algolia work with Feder?

  • Connect Algolia to Feder and it joins your Visits apps.
  • When you connect Algolia, Feder checks the connection straight away and shows Connected only when that check passes. If a reading cannot be taken later, Feder shows it as not read, never as zero.

Some numbers are too quiet to judge daily, such as a form filled in a few times a week. Until there is enough of your own history to judge a change, Feder says it is still learning and scores nothing, rather than guessing.

See whether you can trust the numbers in Algolia, one of your Visits apps. Feder only reads. It never changes anything in Algolia.

Where do these answers come from?

Every cause and check on this page comes from the Algolia help pages, quoted above with the date we read them. Last reviewed 2026-11-12. We read them again by 2027-11-12. If one changes, this page changes or comes down.

Know the day a number breaks, not the month after.