Coveo AI-Relevance Platform: Enterprise AI Search and Answers

Coveo's main use case was to provide AI-powered search, especially for company documents that were available on almost all web applications, both public and internal, allowing employees to search their documents and customers to search their opportunities.

We were able to index Salesforce cases, case comments, and knowledge articles in Coveo, allowing us to integrate that particular search bar in the internal application where support agents can utilize it to search for cases and knowledge articles, thereby providing clear solutions to customers.

That was the main use case, especially pulling documents from different places and displaying them to people in a way that they can clearly get the results they are looking for.

Coveo positively impacted our organization by drastically reducing the time needed to provide solutions on the support case side, as agents no longer have to sift through all documents, resulting in decreased response time and reduced case volume since customers can verify the knowledge available before creating a case.

The case volume was reduced by about 25 to 30%.

From my experience, AI-powered search was the best feature Coveo had, along with its generative answering capability, which stood out as a good capability.

The generative answering capability works similarly to GenAI, allowing support agents or customers to type in their questions in the search bar and receive summarized results of knowledge documents without needing to open each document, thus saving time with clear steps on how-tos.

Coveo had many out-of-the-box connectors and generic API connectors that allow connections with other repositories or databases, which stood out to me.

Coveo's accuracy and reliability of output are commendable because whatever you ask, you get relevant results, which is crucial.

There are many things we faced when encountering issues, and I would say that several features were missing. For instance, when we create a support ticket, I believe they need to enhance it and then share back the results, which indicates it is an evolving product.

Those were aspects we wished we had, however, I do not have any additional thoughts on improvements at the moment.

Coveo's AI capabilities have a few risks, and I think there were instances where people faced some issues.

I don't have exact details on those security concerns, but they definitely relate to some internal bugs that need to be addressed.

That is all the improvements I think Coveo needs.

I have been using Coveo for the last six years, from 2020 to 2026, until the time I was working at FY.

Coveo is very stable in my experience without any issues relating to downtime or reliability.

Coveo's scalability is good; it can handle increased loads or more users easily.

Customer support was satisfactory in my experience. I would give customer support an eight out of ten.

I previously worked on a different solution at another company.

We do not install anything as Coveo itself is a cloud platform.

I think the pricing was definitely on the higher side, and the professional services were also quite costly.

I'm sure the team evaluated other options before choosing Coveo, but I am not aware of which ones specifically.

I would rate Coveo an eight out of ten.

I chose 8 out of 10 because of its good capabilities and ease of connection.

I'm not aware of whether we purchased Coveo through a cloud marketplace like AWS Marketplace or through a direct purchase since it is an organization-wide decision.

Definitely, I would advise that there are not many options available, and Coveo is straightforward to use without requiring much time to install.

My overall rating for this review is eight out of ten.

My main use case for Coveo is the development and implementation of Coveo search for a client project.

A specific example of how I used Coveo for search in that client project is that we generally implemented Coveo Headless to implement the search functionality to get the data and to use the powerful search capability of Coveo.

In addition to my main use case with Coveo, we utilize product-specific data and its metadata, and we use the enhanced search capability of Coveo.

Coveo has positively impacted my organization by improving the overall search experience, making content easier to find and more relevant to users, reducing the time spent searching for information, and helping users reach the right content more quickly. From a development perspective, Coveo Headless provides flexibility to build a customized search experience.

While I don't have access to organization-wide metrics, the main positive outcome I can share is an improved search experience for users, as we were able to deliver more relevant search results and make it easier for users to find content quickly.

Coveo offers powerful search capability as one of its best features.

What makes the search capability stand out for me is its powerful search capability, relevance tuning, a good headless framework for building a custom search experience, flexible integration with React and Next.js, and good analytics.

One of the standout features of Coveo is its AI-powered search relevance, which helps users find the right content quickly. I also appreciate Coveo Headless because it gives developers the flexibility to build a fully customized search experience with frameworks like React, Next.js, and other UI frameworks.

Regarding Coveo's AI capabilities, it provides strong governance and security capabilities suitable for enterprise environments, offering role-based access control, content source permissions, and secure integration with various systems, which helps ensure users only see content they are authorized to access.

In my experience, Coveo AI is generally accurate and reliable in delivering relevant search results, especially when it has access to quality content and is properly configured. Features such as relevance tuning, usage analytics, and machine learning help improve search results over time based on user behavior.

Coveo is a powerful platform, but there are a few areas where it could improve. The learning curve can be steep for new developers, especially when working with relevance tuning, query pipelines, and advanced configurations. Simplifying some of these concepts while providing a more guided setup experience would help teams get up to speed faster.

There are opportunities to improve the developer experience with Coveo, as the initial setup and understanding of concepts such as query pipelines, relevance tuning, and machine learning models can take time for new team members.

I have been using Coveo in my previous project for more than one year.

I gave Coveo a rating of nine because it provides powerful search capability, strong relevance tuning, and a flexible headless architecture that works well with modern frameworks such as React and Next.js, along with useful analytics and customization options that help deliver a better search experience. The reason I didn't give it a ten is that there is still a learning curve for new developers.

In my organization, Coveo is deployed as a cloud-based solution, leveraging Coveo cloud platform to power the enterprise search experience and integrate content from various sources.

I am not directly involved in the infrastructure side, so I am not certain which cloud provider is used for our Coveo deployment.

I would recommend Coveo to organizations that need a scalable enterprise search solution and want to deliver a personalized search experience across multiple content sources.

My advice to others looking into using Coveo is to spend time understanding Coveo's core concepts, such as relevance tuning, query pipelines, analytics, and content indexing, before starting implementation.

My main use case for Coveo was to index the search results on our search pages like insights, listings, articles, stories, and other content.

One specific example of how Coveo worked for one of our search pages is when we had an external database managed by another team. We used to import those database items into a Sitecore master database, and while those items were getting published, they would also get indexed in Coveo, allowing us to search for specific items using their item ID or listing name, which would then appear in the search results managed by Coveo.

I faced some challenges regarding the accuracy of the search results with Coveo. For instance, if we searched for properties, listings would appear based on the property names, but the search accuracy wasn't always perfect. Suggestions in Coveo, such as office spaces, would yield popular office options that were cost-effective.

Coveo positively impacted my organization because the majority of our users who visit our website primarily use the search pages, making it a major functionality of our site.

I definitely noticed an increase in user satisfaction and improved search accuracy as a result of using Coveo.

The best feature Coveo offers is that items imported into the master database of Sitecore get indexed in Coveo very quickly, probably under a minute, allowing those items to be visible on the search page promptly.

The speed of Coveo's indexing helped our business users in many ways, specifically by ensuring their business campaigns and client expectations weren't negatively impacted due to slow search results.

The integration of Coveo with Sitecore is very good, particularly regarding implementation, customization, widgets, maps, and facets.

I believe Coveo can be improved by integrating artificial intelligence features. For example, if I type 'office spaces' looking for cheap and average sizes, improving AI could provide better search results based on user search history.

I have been using Coveo for the last 3.9 years, and recently we have replaced Coveo search with a Sitecore search in our project.

Coveo has never experienced downtime or issues in my experience.

Coveo is definitely scalable and can handle large volumes of data and users.

I reached out to Coveo's customer support many times, and it was one of the best experiences I had with their support team. I would rate the customer support as a nine on a scale of one to ten.

We are currently using Sitecore search in place of Coveo, which we recently replaced.

I do not have metrics related to return on investment with Coveo currently.

I didn't work on the licensing part of Coveo because I was an employee and not the manager.

Coveo was the first option in my mind before making a choice.

The quick indexing into the search results is the best scenario I faced with Coveo. In terms of accuracy and reliability of output, I believe Coveo is probably the best in market scenarios. Coveo is deployed in my organization as software as a service and integrates with my code base directly. I am not sure about Coveo's governance and security regarding its AI capabilities. I would rate Coveo an eight on a scale of one to ten.

One of my main use cases for Coveo is enterprise knowledge search and contextual content retrieval. For example, in one project, we had information spread across sources like SharePoint, CRM systems, and internal documents, and we used Coveo to index that content and provide a unified search experience. We configured the indexing pipeline to normalize and enrich the content, and then used query pipeline and relevance tuning to make sure the most relevant documents were surfaced. On top of that, we have integrated the search capability into an AI-powered assistant, so when a user asks something like, 'What is the latest account summary for this customer?', the application retrieves the relevant Coveo content and uses it as context for the AI response. In simple terms, Coveo handles the enterprise search and relevance layer, while the AI assistant uses those results to provide a contextual answer.

Overall, the process of integrating Coveo search with my AI-powered assistant was fairly smooth, but there were a few challenges, mainly around making Coveo results reliable enough for the AI layer. The integration itself was straightforward; we used Coveo APIs to execute searches, retrieve relevant documents, and pass the results as context to the AI assistant. The bigger challenge was relevance and context quality. Sometimes the search returned technically relevant documents, but not necessarily the exact information the user was looking for. We addressed that through query pipeline configuration, query extensions, filtering, metadata enrichment, and relevance tuning. Another challenge was controlling the amount of content sent to the LLM, as we did not want to pass a large number of documents blindly, so we applied result filtering and ranking before sending the context to the AI. The API integration was relatively smooth; however, getting the search results to be strictly accurate and AI-ready required more tuning and testing.

I would add that I see Coveo as the retrieval and relevance layer rather than just a search box. In the AI assistant integration, the quality of the final answer depends heavily on the quality of the content retrieved from Coveo. We paid particular attention to metadata, security permissions, relevance tuning, and grounding the AI response in the retrieved content. That also made monitoring important, as we validated both sides independently—whether Coveo was returning the right results and whether the AI was using those results correctly. Overall, the integration worked well, but the key learning was that good AI responses start with good enterprise search and well-structured content.

The biggest positive impact Coveo has made on my organization is reducing the time people spend manually searching across different enterprise systems. In one of our implementations, we brought content from multiple sources into a unified Coveo search experience and then exposed those results through an AI assistant. This reduced the need for users to manually go through SharePoint, CRM records, and internal documentation. From a business perspective, we saw faster information retrieval and reduced manual effort, particularly for teams that frequently work with customer and account information.

In one of the AI search implementations I worked on, we measured roughly forty to sixty hours of manual effort saved per week across the team by automating the retrieval and processing of information that previously required people to search multiple sources manually.

In my experience, a few Coveo features stand out, with the first being relevance tuning—the ability to control how results are ranked through query pipelines, ranking expressions, query extensions, and ML-based relevance, which is very useful for enterprise search. The second is the broad range of connectors and indexing capabilities, as being able to bring content from systems like SharePoint, Salesforce, websites, and other enterprise sources into a unified index is a major advantage. The third is Coveo Machine Learning; features such as automatic relevance tuning and recommendation models can improve the experience without having to manually configure every ranking scenario. Finally, I find the APIs and Headless framework particularly useful because they allow us to integrate Coveo into custom applications rather than being limited to Coveo's out-of-the-box UI. The combination of enterprise content ingestion, strong relevance capabilities, ML, and developer flexibility is what I find the most valuable.

If I had to pick one, I would say relevance tuning has been the most impactful feature for my projects. In enterprise search, simply indexing a large amount of data or content is not enough, as users need the right result at the top, and what is considered relevant can vary significantly by business context. For example, we had a scenario where multiple documents could match a customer or account query, but the user needed the latest and most contextually relevant document rather than just a keyword match. We used query pipelines, ranking expressions, metadata, and ML-based relevance capabilities to improve how those results were ordered. The biggest benefit was that we could continuously tune the search experience based on actual user behavior and search analytics rather than hard-coding every possible scenario. Connectors solve the 'How do we get the content into Coveo?' problem, while relevance tuning helps solve the most important 'How do we get the right content in front of the user?' problem.

Coveo's full value really comes from how these features work together. For example, connectors bring the enterprise content into the index, indexing pipelines enrich and structure the content, relevance and ML determine what should surface, and the APIs allow us to integrate the experience into custom applications or AI assistants. I would also highlight security and permissions; in enterprise environments, it is not enough to return relevant content. We need to make sure users only see content they are authorized to access. The combination of relevance, enterprise security, content ingestion, and developer flexibility is what makes Coveo particularly useful for large-scale enterprise search.

In my experience, Coveo's governance and security are particularly important strengths for enterprise AI use cases, especially because Coveo can operate on sensitive enterprise content. The key aspect for me is permission-aware retrieval, as you do not want the AI assistant to retrieve information that the requesting user is not authorized to access. Coveo's security model and permission handling help maintain those access boundaries.

From a developer's perspective, there are a few areas where Coveo could be improved. The first is configuration and troubleshooting; Coveo is very powerful, but for someone new to the platform, understanding why a particular document is not indexed or why a result is ranked a certain way can take time. More guided diagnostics and clearer error explanations would help. Second, the developer experience could be more streamlined. Having a more unified experience across APIs, Headless, query pipelines, and ML configuration would reduce the learning curve.

While Coveo's documentation is generally good, it can sometimes be difficult to find the exact guidance for a specific implementation scenario. For example, when troubleshooting indexing or relevance issues, it would be helpful to have more end-to-end scenario-based examples rather than having to piece information together from different documentation sections.

The main reason I rate it an eight out of ten is that while Coveo is very capable, there is still some room for improvement regarding the developer experience. The biggest gaps for me are troubleshooting and observability, documentation discoverability, configuration complexity, and AI or RAG workflows.

One additional area I would mention regarding improvements needed is cost visibility and optimization.

I have been using Coveo for around two years, primarily gaining hands-on experience that includes Coveo indexing data sources, indexing pipeline, query pipelines, relevance tuning, Coveo ML, and API integrations. I have also worked on troubleshooting issues around indexing failures, search relevance, query behavior, and integrating Coveo search into enterprise applications.

In my experience, Coveo has been stable for our enterprise workloads, as we have not experienced major stability issues with the core search service. Most of the issues we have encountered have been more related to indexing configuration, data source connectivity, permissions, or query configuration rather than Coveo itself.

From my experience, Coveo has been quite scalable for our enterprise search, as we have used it with multiple data sources and a growing volume of indexed content while supporting concurrent users and API-based search from our backends. One thing I like about the SaaS model is that we do not have to manage the underlying search infrastructure ourselves, allowing us to scale the application and integration layer independently while Coveo handles the search infrastructure.

Coveo scales well for enterprise search, and we have not hit a fundamental platform limitation as indexed content and usage grew. The areas we pay attention to as usage increases are indexing volume, query API traffic, connector throughput, and relevance performance, which can require architectural and configurational adjustments.

Overall, my experience with Coveo's customer support has been positive; for technical indexing, query pipelines, or API behavior, the support team has generally been helpful in narrowing down the root cause. The main area I would improve is speed and depth for more complex issues, as some problems require multiple rounds of investigation, particularly when they involve a combination of indexing, permissions, and relevance configuration. I also think having more self-service diagnostic tools and scenario-specific documentation would reduce the need to raise support tickets in the first place. Overall, support is reliable, but there is room to make troubleshooting faster and more self-service oriented. I would rate Coveo's customer support an eight out of ten.

Before using Coveo, we relied more on native search capabilities across individual systems, such as SharePoint and CRM search, rather than having a unified enterprise search layer. The main challenge was that information was fragmented across multiple systems, requiring users to search each source separately, and the relevance and ranking were different from one system to another. We moved toward Coveo because we wanted a centralized search and relevance layer that could bring those sources together, apply consistent relevance and service controls, and expose the results through APIs for our AI assistant. The main driver was not that the previous tools were inadequate individually; it was the need for a unified enterprise search, better relevance, and easier integration with our AI experience.

The clearest ROI metric from our implementation was the time saved rather than a direct headcount reduction. By combining Coveo search with an AI assistant and workflow automation, we estimated roughly forty to sixty hours of manual effort saved per week across the team, as previously, users had to search multiple sources and manually consolidate all the data.

From my experience, the setup process itself was fairly straightforward, but the pricing and licensing can be more complex because they depend on factors such as usage, data volume, features, and specific enterprise agreements. I was not directly responsible for negotiating Coveo's contract, so I cannot provide a specific dollar figure for my organization.

We looked at a few approaches before choosing Coveo, including native search capabilities from platforms like SharePoint and Salesforce, as well as building a more custom search solution using APIs and search engines such as Elasticsearch or OpenSearch.

Coveo's accuracy is strong when configured properly, but I would not consider the output automatically reliable just because Coveo is involved.

In our organization, Coveo is primarily used as a cloud-based enterprise search and retrieval service rather than something we deploy directly on our own infrastructure.

For Coveo itself, we classify our consumption as a SaaS platform, so we do not directly manage or select the underlying cloud infrastructure where Coveo's service runs.

My main advice for others looking into using Coveo would be to start with a clearly defined business use case and measurable success criteria rather than starting with the technology. I recommend identifying key data sources and security models early, investing time in relevance tuning, prototyping with real user queries and real enterprise data, and planning for AI integration from the beginning if you are going to use Coveo for RAG or AI assistant. You also have to define metrics upfront. I rate Coveo an eight out of ten overall.

Coveo's main use case revolves around content indexing and search integration, primarily when working with Sitecore as a CMS implementation.

In our Sitecore CMS implementation, we have very large content volumes, and Coveo helped us significantly with relevance through the use of indexing, query pipelines, and security features. Relevance was the most valuable feature for us. We were able to determine what content was shown to users and which was not, so Coveo provided substantial value from a relevance perspective.

From a business perspective, Coveo's biggest value is having more control over how users discover content, including relevance, ranking, personalization, and analytics, which can help improve the search experience without requiring a developer to change application code for every small adjustment. The exact value obviously depends on how well the organization configures and uses those capabilities.

Before moving to Coveo, we had metrics of user clicks around two million, but after we went live with Coveo, user clicks and all view analytics jumped up over 3.5 million, which was a significant upgrade after implementing Coveo.

In my view, the best feature that Coveo offers is relevance, which is one of the strongest areas. You have more control than you would typically get with a basic search implementation, particularly through query pipelines and ranking configuration. The important thing is that good relevance still requires proper configuration and understanding of your content, so I would not expect the platform to solve every relevance problem automatically.

I find query pipelines particularly useful because they give you a way to influence search behavior based on the context of the query without having to pull that logic into your application. For example, you can apply different ranking on query behavior depending on the situation, which provides a good separation between the application and search configuration.

Recently, I have been exposed to working with Coveo Atomic while working on the headless Sitecore implementation, and I appreciate the Atomic library because it provides reusable search components, so you don't have to build every part of the search interface from scratch. It makes the front-end integration faster while still allowing the developer to customize the experience when needed.

The main area I would improve is the learning curve because there are many concepts and configuration options, and understanding how indexing, query pipelines, security, and all those pieces work together requires experience. Coveo's onboarding experience could be simpler, especially for developers using the platform for the first time, and I believe that improvement on the documentation is also needed because while Coveo has extensive documentation, it is sometimes difficult to find exactly what you need.

As a developer, when trying to find something regarding how to do indexing, I have to read the documentation, but if there were screenshots showing how it can be done, it would make a developer's life simpler. Additionally, including code examples would greatly enhance the experience for developers.

I have been using Coveo mainly in enterprise search implementation, particularly in Sitecore environments, so I have been working with Coveo for the last five to six years.

From an enterprise perspective, scalability is one reason we consider a platform Coveo because we don't have to build and maintain the underlying search infrastructure ourselves, and the platform is designed for large content environments. My direct experience is more focused on implementation and integration, but I haven't seen scalability become a major limitation.

I recommend starting with search requirements rather than starting with product features. Understand your content sources, security model, and relevance.

So far, I haven't touched Coveo's AI-powered solutions, so I may not be able to comment on that because my experience is mostly with integrating Coveo, but not with the AI-powered solution models. I haven't used those AI features much, so I cannot provide insight on the accuracy and reliability of output.

I would rate Coveo an eight out of ten. I choose this rating because the platform is powerful, has strong relevance, and enterprise capabilities, but I deduct a couple of points mainly due to the learning curve and some areas that can take time to understand when implementing Coveo for the first time.

My main use case for Coveo is the search page. I use Coveo for my search page by creating sources in Coveo cloud organization and then providing it with data from our website and then displaying that search result on the search page.

Coveo has impacted my organization positively, as the search has been very good; the search terms and fuzzy search have all become very effective. I don't have particular data regarding specific outcomes or metrics at this time.

One thing that stands out to me about using Coveo for this process is that, as it is a cloud platform, it is very easy to integrate with your website as compared to other search options available.

The best features Coveo offers are the machine learning models and Coveo API. What I like about the machine learning models is that they are very easy to integrate; you just need to create some settings in the cloud organization, and then when you start using the search, it automatically learns from those searches and provides auto-suggestion in the search box.

Regarding Coveo's AI capabilities, I think its governance and security are good; as it is a cloud-based platform, the security is already very good as it uses SSO or login features. The accuracy and reliability of output from Coveo comes when the machine learning models learn from the searches that are done on your live site, so it becomes better over time, and I think those are reliable.

In terms of integration capabilities with other platforms or tools I use, I think it is pretty good; integration is straightforward. I have done it with Sitecore as well, and it provides out-of-the-box packages to integrate it, so it is very easy. I would describe the user interface and overall user experience with Coveo as very good.

I think Coveo can be improved by providing a sandbox for developers, even if you are not part of an organization, and the API configurations can be made a bit easier because there are a lot of options right now which confuses users. If I had to rate Coveo's flexibility regarding customization for my specific needs, I think it would be six out of ten.

I have been using Coveo for two years.

I think Coveo is stable.

I think Coveo's scalability is good.

The customer support for Coveo is very good.

I have used Solr before Coveo, and we switched to Coveo to utilize its AI capabilities.

Coveo is deployed in my organization as a SaaS-based software, so you don't need to deploy it; it comes by default on a cloud and it basically will provide you an organization so you can log in and then work with Coveo.

I can't say I have seen a return on investment with Coveo; I don't have these metrics.

I was not part of the pricing and licensing experience as it is handled by my organization, so I'm not aware.

Before choosing Coveo, we did not evaluate other options.

I would rate Coveo an eight out of ten. I chose eight out of ten because, as this is a cloud-based platform, there are some limitations, but overall it's a good tool.

Coveo already has a very good e-learning platform with multiple courses to learn and certifications to achieve, so it is very good in terms of the learning curve for new users or developers working with it. The documentation and resources available for Coveo are helpful, and even if you are a new learner, you can go through the documentation and it covers everything related to Coveo.

As far as I have used it, Coveo's performance and speed with large data sets is pretty good. I would advise others looking into using Coveo that it's a great product; just start looking into the documentation and utilize it well so your search page becomes better.

Our main use case for Coveo is to retrieve data efficiently. Before using Coveo, we stored this data in Salesforce itself, which took longer. We migrated our database to Coveo.

A specific example of how we use Coveo to retrieve and store data is related to our website, which functions as a doctor's website. Previously, we stored all data related to our doctors' content in Salesforce directly. When a doctor searches for it on our website or opens our record page, content pages, or content landing pages, content loading time took around 300 milliseconds. While not a major difference, in terms of user experience, it matters. After migrating to Coveo, it took less than 10 milliseconds to load all this data. This is our main use case, and we also have other use cases, such as content recommendation to our doctors based on trending content and personalized content.

Regarding the content recommendation use case, Coveo helps us personalize content for doctors with an ML-related feature. We send every detail of the doctor's viewing of pages to Coveo directly with the help of Google Analytics. First, we send the data from Salesforce to GA once a doctor views any particular content, and GA sends all this data to Coveo to train our ML models. With the help of those ML models, we see what the trending content is currently. Our doctors are specialized in 12 to 13 different specialties. Based on their specialties, we recommend content directly on the dashboard pages and on the content detail pages.

The best features Coveo offers include content recommendation, which is one of the best features. Additionally, the retrieval of data takes less time. It has moved from 300 milliseconds from our Salesforce data retrieval to less than 10 milliseconds in our Coveo retrieval. This is one of the other best features. The best thing is that we do not need to make an API callout for every communication between Salesforce and Coveo. I believe we are using headless communication, which is considerably faster. These are the best features I have observed.

Coveo has positively impacted my organization primarily by reducing the waiting time from 300 milliseconds to 10 milliseconds. Coveo also provides us very high data storage. We store our Salesforce records directly into Coveo as well. It syncs, and it takes around one hour to have a sync between Salesforce and Coveo.

Besides the improved speed and data storage, I have noticed increased productivity. Productivity has increased. The improvement is good, but I do not have the exact metrics of those details.

Coveo almost fulfills all my use cases, so I do not have any other recommendations or suggestions for Coveo.

One other suggestion is that as of now, the sync between our Salesforce and Coveo is one hour. I know we can make it real-time also. I do not know much about it, but I think it costs higher if we make it real-time. I would say that could be one of the improved features. It can give us more satisfaction if it is a real-time sync.

I have been using Coveo for a year.

Support is very good with Coveo.

It was great working with a product such as Coveo and integrating that product with our Salesforce. The experience has been good. I would rate this review a 9.

I used Coveo for content indexing and content search from AEM, and I have used it for multiple languages. The content was available in English language and Chinese language, so our requirement was to index the content and then search the content from Coveo.

Coveo has a push API which indexes the content with a certain structure and JSON payload for the page properties that exist in AEM pages. For example, a page title, page description, page tags, and metadata properties from the page are indexed in Coveo with the help of Coveo push API. There are certain request headers such as UTF-8 encoding. We wrote an HTTP client which makes calls to Coveo push API to index the content. To search the content, we used the Coveo endpoint and the page ID as the path, basically the page path as a resource to pull the content from Coveo.

We used Coveo for multiple languages with English language content and Chinese language content. We faced challenges initially because we had not added UTF encoding in the header, so the Chinese content was not properly indexed and instead showed question marks. We added the header with UTF-8 encoding, and after invoking the same API, we were successfully able to index the Chinese content. We fixed this issue and successfully indexed and fetched the Chinese content from Coveo.

Coveo is an enterprise-grade search and index platform that can be integrated with any CMS platform; in our case, it was Adobe Experience Manager. Since it is API-based, Coveo can also be used in other CMS platforms.

We did not face challenges in the integration process with Adobe Experience Manager specifically. We went to Coveo platform, reviewed the API integration methods, and learned how to pass the key and authentication methods in the API. We configured the OSGi configurations, which is typically how AEM supports any kind of configurations. We used the OSGi configurations in AEM and configured these API endpoints and the authentication methods, OAuth tokens, and other security measures. We invoked that API in our code base; in our code, we have OSGi services and Sling Servlets which are invoking Coveo's APIs.

Coveo is scalable and I have not seen any latency issue. The content immediately reflects the moment you index it, and in a couple of minutes, it is reflecting on the Coveo server. It is easy to use, easy to navigate, and you can easily find your content which is indexed on Coveo platform. Coveo is a specialized platform in the field of indexing and searching and is a known search platform. We seamlessly integrated and benefited, especially because indexing the content was taking too much time when we were indexing to other platforms such as Solr. However, in Coveo, we have not faced any latency issue and we were quickly able to index the content and search the content.

Coveo is easy to integrate and it hardly takes a few lines of code that we need to write. There are not many complex configurations we have to write for integration. A small configuration for the API endpoint, the API payload, and the authentication methods allows us to write a few lines of code for an HTTP client to invoke these APIs. It is easy to integrate and we can easily maintain it. If there are any changes in the future, we can easily make these changes.

Coveo can improve by supporting a few more languages. For example, we have tested with English and Chinese and a bit of French. I think Coveo can come up with indexing and searching with non-native languages apart from these known languages.

When we have to scroll down to search for particular pages, maybe they can provide easier navigation and links to find content, either with the help of page paths or another method. We have seen that if we have multiple pages or many pages published to Coveo to index, then it is time-consuming to scroll down and see the content, especially if it is indexed properly.

I have used Coveo for more than two years.

Coveo is deployed in our organization on a public cloud with API integrations and authentication methods, and we call this publicly hosted Coveo platform on the cloud.

We have used AWS, if I remember correctly, because it was a long time ago, almost more than two to three years back now.

There was a separate team actually accessing Coveo console and they were aware of that; we were using those APIs and the configurations as a vendor.

If others are looking into using Coveo, I would advise that if they have a use case for scalable solutions for enterprise-wide search capability or indexing content, then Coveo is the right choice.

I would rate Coveo a seven out of ten.