> 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/getting-started/quickstart.md).

# Quickstart

This guide takes you from a new account to your first useful Reach insights.

## 1. Create your workspace

Enter the primary domain for the brand you want to monitor. A workspace keeps that brand's domain, competitors, markets, prompts, and analytics together.

Use a separate workspace for each brand or market that needs independent tracking.

## 2. Complete onboarding

Reach researches the domain and prepares an initial view of the business, audience, competitors, topics, and prompts. Review each step and correct anything that does not represent the brand accurately.

The information you approve becomes context for analysis across the product. You can review it later from **Your data**.

## 3. Review your prompts

Prompts represent the questions buyers ask AI engines. Open **Prompts** to review the initial set, disable anything irrelevant, and add important questions that are missing.

Choose prompts that reflect real buying situations rather than variations written only to mention your brand.

## 4. Read the first visibility results

Open **AI Analytics** to see whether the brand is mentioned or cited, how it compares with competitors, and how results vary by AI engine.

New workspaces may need time to collect enough responses for stable trends. Treat the first results as a baseline rather than a final score.

## 5. Connect Google data

Connect Google Search Console and Google Analytics 4 from **Settings → Integrations**. This adds first-party search and traffic context to Search Demand and Page Insights.

See [Connect Google data](/getting-started/connect-google.md) for the complete flow.

## 6. Pick the next opportunity

Use:

* **Search Demand** to find keywords and questions worth targeting.
* **Topics Explorer** to understand coverage across themes.
* **Page Insights** to identify pages that should be created, updated, or fixed.

Reach is most useful as a loop: measure visibility, investigate why, take action, and compare the next period with the baseline.


---

# 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/getting-started/quickstart.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.