> For the complete documentation index, see [llms.txt](https://docs.usereach.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usereach.ai/find-opportunities/search-demand.md).

# Search Demand

Search Demand brings together keywords, questions, competitor rankings, Search Console data, and opportunity signals so you can decide what content deserves attention.

## Relevant keywords

This is your working keyword portfolio. Use filters for topic, volume, difficulty, ranking status, labels, and intent to narrow the list to a practical decision set.

Opportunity scores help prioritize, but they are not a substitute for judgment. Check relevance to the business and the search results before committing resources.

## Competitor keywords

Compare the queries competitors rank for with your own coverage. Promote a relevant gap into your keyword portfolio when it represents demand you genuinely want to serve.

## User questions

User Questions collects question-shaped demand from search results and other discovery sources. Use it to find specific problems that can become sections, FAQs, comparison pages, or standalone content.

## Topic clusters

Clusters group related keywords so you can plan coverage at topic level instead of producing isolated pages. For deeper topic management, use [Topics Explorer](/find-opportunities/topics-explorer.md).

## Search Console

Connected Search Console data shows the queries already driving impressions and clicks. Look for:

* pages close to page one or the top positions;
* high impressions with weak click-through rate;
* declining queries that need investigation; and
* relevant queries not yet included in research.

## A practical workflow

1. Filter to a relevant topic or journey stage.
2. Compare demand, difficulty, current ranking, and business relevance.
3. Inspect the current search results and competing pages.
4. Decide whether to create, improve, consolidate, or distribute content.
5. Track the selected keyword and review progress over time.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.usereach.ai/find-opportunities/search-demand.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.