Commerce search implementation checklist (Legacy)
Commerce search implementation checklist (Legacy)
This section provides information on how to implement search interfaces that interact with the Coveo Search API, which is no longer recommended for Coveo for Commerce implementations. New Coveo for Commerce implementations should use the Coveo for Commerce API, which provides a more efficient and flexible way to interact with the Coveo Platform. See Build commerce interfaces for documentation on how to build commerce interfaces using the Coveo for Commerce API. |
This article provides a checklist of the steps required to implement Coveo for Commerce search core features.
You can use this checklist as a guide to ensure that your implementation incorporates the necessary parts to build a working and robust, commerce-oriented search experience.
Content indexing
-
Have you ensured that all your products, their variants, and the various availability channels are correctly indexed within your Catalog source? See Stream your catalog data to your source for details.
-
Are the standard commerce fields appropriately mapped to relevant metadata in your catalog configuration?
-
Have you set up fields to help you structure your catalog entity with products, variants and/or availability, and mapped them to the relevant metadata? See catalog structure fields for details.
-
Have you created and mapped additional commerce fields with relevant metadata?
-
Has your catalog entity been fully set up to accommodate your products, their variants, and their availabilities?
-
Have you implemented a system that allows for convenient content updates without the necessity to re-upload your entire catalog data each time?
Data tracking
-
Have you determined which approach to use for tracking analytics data?
-
Are you tracking standard events for search and click actions?
-
Are you tracking commerce-specific events?
-
Have you verified that the events are being sent to Coveo Usage Analytics and contain accurate information?
Building the search interface
-
Have you opted for one of Coveo’s provided frameworks (Atomic or Headless) to construct your search interfaces?
-
Have you integrated search hubs for every search interface, using suitable names that adhere to naming conventions?
-
If you leverage content security to determine who can access indexed content, are you using search token authentication to authenticate requests originating from your search interfaces?
-
Do your search interfaces encompass all the recommended features?
-
If you use the Atomic library, have you applied customized styling to your interfaces?
-
Are you making use of result templates?
-
Have you optimized your interfaces for search engine optimization (SEO)?
Optimize the search experience
-
Have you established distinct query pipelines to effectively direct the queries that originate from each of your search interfaces?
-
Have you correctly implemented the appropriate query routing mechanism?
-
Have you configured the query pipelines with the essential settings necessary for Coveo for Commerce implementations?
-
Have you linked your catalog entity with the relevant query pipeline(s) to which queries requesting your product inventory are directed?
-
If you utilize product grouping, have you appropriately configured the query pipeline to accommodate this feature?
-
Have you created the relevant Coveo Machine Learning (Coveo ML) model types and associated them with your query pipeline?
-
Query Suggestions (QS)
-
Did you perform validation to ensure proper query pipeline and Coveo ML configurations?
-
Utilizing the relevance inspector
-
Conducting A/B tests
-
Using Advanced Reports
-