Skip to main content

Algolia DevCon - June 28-29, 2023

Discover the future of the AI Stack with Algolia, be the first to see new platform demos and announcements, and get the most out of Algolia through interactive workshops.

REGISTER FOR FREE DON'T SHOW AGAIN
×

How can I make sure Algolia NeuralSearch is working correctly?

  • Updated

You can review our documentation on getting started with NeuralSearch.

Broadly, you'll want to ensure that:

  1. You are on an eligible plan (either the Elevate or Elevate Ecomm plan).
  2. You have enabled NeuralSearch on your index as per this guide.
  3. You've configured your searchable attributes as per this guide and your relevance as per this guide. This ensures that queries not yet generating a semantic score will still generate a relevant keyword score.  
  4. The data structure of your record is a good use case for NeuralSearch (see "Data Structure" section below).
  5. You are sending events (see "Events" section below).
  6. Your use case doesn't conflict with any of the known limitations (see "Limitations" section below).

 

Data Structure

Here's an example of a record structure and settings that would work with NeuralSearch:

name_brand.png

 

 

NeuralSearch is not the best solution for search implementations that only search on SKUs or other exact matches.

 

Events

  • Have you implemented events?
  • Are your events meeting the prerequisite requirements for NeuralSearch? The requirements for the number of events may change, but the latest information can be found in this documentation. 
  • Are your events valid?
    • Use the Events Debugger to assess whether or not your events are valid. Valid events will have a green dot in the "Status" column as shown below:

      latency_app_events.png


You should also make sure that you aren't sending bot-generated events. For more information, please refer to our guide on how to deal with bots.

 

Limitations 

NeuralSearch currently has some feature differences and limitations, including:

  • Multi-region DSN is not currently supported.
  • Index size is limited to 100 GB.
  • Application size is limited to 1 TB.
  • English is currently the only supported language.
  • You cannot use the deleteBy operation. Use the delete method instead, which is significantly more performant.
  • Custom dictionaries are not currently available.
  • Real time logs are not currently available.
  • Vault is not currently available
  • NeuralSearch is not currently HIPPA compliant.
  • There are some internal indexing differences.

 

 

 

Related articles