# Discourse and Coveo

**URL:** https://meta.discourse.org/t/discourse-and-coveo/328091
**Category:** Development
**Created:** [September 25, 2024, 4:16pm UTC](https://meta.discourse.org/t/discourse-and-coveo/328091 "2024-09-25T16:16:30Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)
#### Post date: [September 25, 2024, 6:28pm UTC](https://meta.discourse.org/t/discourse-and-coveo/328091/3 "2024-09-25T18:28:56Z")

</div>

> [@Claire\_C](#):
>
> Has anyone here used Coveo with their Discourse?

There is a post from a few months ago where someone mentioned that they were indexing their Discourse site with Coveo: [Issue with API for indexing with Coveo](https://meta.discourse.org/t/issue-with-api-for-indexing-with-coveo/301517).

They posted a reply in that topic that shows how Coveo is configured to index the site. It seems that the configuration is auto generated by Coveo.

Looking at it now, when using this approach, you’d need to be sure that the API requests to Discourse could be rate limited to a maximum of 1 request per second. Without a rate limit you’d risk triggering timeout errors on Discourse.

This approach could work on any of the hosting plans that allow for API access.

---

_[View the full topic](https://meta.discourse.org/t/discourse-and-coveo/328091)._