Skip to main content
Should you create one large index for all your , or create multiple indices? It depends on your ranking strategy and which user experience you want to create. The number of indices you can create depends on your plan. Federated search lets users search across different sources or types of content from one interface. For example, users can search a product catalog and support articles at the same time. Depending on how you want to organize and present the search results, you can create one index for all data sources or separate indices for each data source. To implement a search interface that queries multiple indices, see Multi-index search with InstantSearch.js. To combine results from several indices into a single response, use compositions. Use multiple indices when different types of content need separate configurations. For example, use one index for movies and another for actors if they need different ranking strategies. For a step-by-step example, see Autocomplete with Federated Search. Use one index when you want to rank different types of records together with the same relevance configuration. For example, store movies and actors in one index to show them together in a single results list. You can search multiple indices in one API request. Each query returns a separate result set, ranked using that index’s settings. If you combine the result sets into one list, you must decide how to order results from different indices.

Multiple indices for Query Suggestions

Query Suggestions suggest popular searches to help users search faster. Algolia stores these suggestions in a separate index from your content.

Multiple indices for different ranking strategies

Each Algolia index can have one ranking strategy. If you want to let users switch between different ranking strategies, for example, to allow sorting by price, you can use replica indices: one index per sorting strategy. A replica index lets you apply a different ranking strategy to the records in a primary index. Algolia synchronizes record changes from the primary index to its replicas. For more information, see Create replica indices.

Multiple indices for different environments

Use separate indices for staging and production environments to keep test queries out of production analytics and make it easier to distinguish test data from production data. Configure access restrictions to control who can use each index. For full separation, use a different Algolia application for each environment. You can use common prefixes to distinguish the different environments, for example, staging_products and prod_products. To reduce the number of indexing operations, you can reduce the number of records in your staging environments, for example, only using 10% of your records. For more information, see Manage your Algolia applications.

See also

For guidance on child-level, group-level, and parent-level records, see Structure your records.
Last modified on November 11, 2026