> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/configurations/keywords.md).

# Keywords

### About Keywords

A keyword is a **word or phrase you want Reo to watch for**. It could be your product name, a competitor, a technology, or anything.

Developers talk about tools in public, across developer forums and communities. **Keywords surfaces those conversations for you, so you don't have to check them manually.** 

You can track keywords across the following developer communities: 

* Reddit
* Stack Exchange
* Slack
* Hacker News
* Dev.to
* Product Hunt

Once you add a keyword, Reo starts scanning every developer community you've turned on, for that word. **Whenever someone posts about it, it shows up in your list.**

{% hint style="info" %}
**Note:** Only open communities are tracked. Gated or invite-only communities, regardless of platform, are excluded. This ensures that only relevant, publicly available developer conversations are included in the insights.
{% endhint %}

***

### Step 1: Open Keywords configuration

* From the left navigation menu, click **Settings >** select **Configurations**
* Within the **Keywords** card > select **Configure**

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FYRJvlxXq0fegXgPqOnYV%2FScreenshot%202026-09-16%20at%2012.20.58%E2%80%AFPM.png?alt=media&amp;token=5666350e-f4c9-4f04-a04d-7e331303e5a5" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2Fn0KG6zpCSiAbNykIBxX5%2FScreenshot%202026-09-16%20at%2012.22.08%E2%80%AFPM.png?alt=media&amp;token=4fab040e-55c3-4c18-a009-aaa98312e8bb" alt=""><figcaption></figcaption></figure>

### Step 2: Choose which communities to track

* At the top of the page > under **Currently Tracking**, you'll see the supported communities
* Each one has a toggle:
  * **On** = Reo searches that community for your keywords
  * **Off** = it doesn't
* Turn off any community that isn't relevant. For example, if your buyers don't use Product Hunt, turn it off
* This choice applies to every keyword you add

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FpAJ4OQ5R8y3PlDDPQE18%2FScreenshot%202026-09-16%20at%2012.23.36%E2%80%AFPM.png?alt=media&amp;token=5e0305fe-8bb4-4318-9aff-d3d20d12c035" alt=""><figcaption></figcaption></figure>

### Step 3: Add what you want to track

* Under **Keywords**, type in a word or phrase

{% hint style="info" icon="lightbulb" %}
**Key point:** you can track up to 5 active keywords at a time. Toggle one off and another on whenever your priorities change.&#x20;
{% endhint %}

* Each keyword has its own toggle (on to track it, off to pause it)

***How you write it changes what it matches:***

<table><thead><tr><th width="180.5390625">Type</th><th width="234.015625">Write it like this</th><th>Matches</th></tr></thead><tbody><tr><td>Exact match</td><td><mark style="color:red;"><code>Postman</code></mark></td><td>Just that word</td></tr><tr><td>Phrase</td><td><mark style="color:red;"><code>"API testing"</code></mark></td><td>That exact phrase</td></tr><tr><td>Wildcard</td><td><mark style="color:red;"><code>Graph*</code></mark></td><td>Any version, like <mark style="color:red;"><code>GraphQL</code></mark></td></tr></tbody></table>

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FBSK15R0OaS6rKaiPYo54%2F4.png?alt=media&amp;token=284c6770-7daf-4270-ad7e-c482175ed6ca" alt=""><figcaption></figcaption></figure>

### Step 4: Check what's already been found

* Some keywords already show results with a **View Conversations** link next to it
* Select **View Conversations** to read the actual posts

{% hint style="info" %}
*No count shown yet? Reo hasn't found any mentions of that keyword*
{% endhint %}

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FKyRimwxNAb1mAgxp9ujD%2F5.png?alt=media&amp;token=bcdf1835-425a-49da-bb43-13b1f81f3ffc" alt=""><figcaption></figcaption></figure>

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FZmQrzwDMNeOvcjb5iyEx%2F6.png?alt=media&amp;token=f58f6db1-c143-466a-8ee1-faadbc8e8447" alt=""><figcaption></figcaption></figure>

### Step 5: Paused keywords keep their history

* Turning a keyword off only pauses the tracking, it doesn't delete anything
* Next to a paused keyword, you'll see an info icon. Hover over it to see when you turned tracking off
* Turn it back on any time, and everything it found before is still there

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2FN9LrW4aklKFnsPVLRut7%2F7.png?alt=media&amp;token=8e38ed3c-a3bd-45b7-b04c-f52e1dfabbdd" alt=""><figcaption></figcaption></figure>

### Step 6: Add more keywords

* Select **+ Add New Keyword** for a new field
* Type in what you want to track, select **Save**

<figure><img src="https://2705882080-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx46P5sAHxDG7PqOdVLxI%2Fuploads%2F10BfldmH7kafUWv5iaSX%2FScreenshot%202026-09-16%20at%2012.31.47%E2%80%AFPM.png?alt=media&amp;token=a8064dca-0c95-47eb-9338-fafd1a2121d2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reo.dev/configurations/keywords.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.