> For the complete documentation index, see [llms.txt](https://georeport.gitbook.io/georeport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://georeport.gitbook.io/georeport-docs/getting-started/onboarding-setup.md).

# Onboarding Setup

### Set up before using GEOReport

Once inside, GEOReport personalizes your dashboard. You’ll be asked:

* **Where did you hear about GEOReport?** (TikTok, YouTube, ChatGPT, etc.)
* **What will you use it for?** (SEO strategy, blog audit, competitor comparison, etc.)
* **What’s your role?** (Founder, SEO specialist, content writer, etc.)
* **Team size?** (Just me → 5000+ people)
* **What do you want to focus on first?** (Landing page audit, blog post audit, competitor comparison).

<figure><img src="/files/uVu5ClbFa5JUZLKdizZO" alt="Onboarding process"><figcaption></figcaption></figure>

### **Why this matters for AI visibility?**

These answers allow GEOReport to **tailor your experience to your visibility problems**. For example:

* A *content writer* will get more tips on readability and FAQ formatting.
* A *developer* may see more focus on technical layout and accessibility fixes.

**Example:**\
If you choose “*I want to compare competitors*”, GEOReport will highlight benchmarking tools that show why your competitor shows up in ChatGPT results but you don’t.

### FAQs

<details>

<summary><strong>Why does GEOReport ask where I heard about it?</strong></summary>

This helps us understand your journey and optimize onboarding. It doesn’t affect your AI visibility directly, but it ensures we present relevant tips and features.

</details>

<details>

<summary><strong>Do my onboarding answers affect my audit results?</strong></summary>

No. Your site’s audit is independent of your answers. The onboarding questions only customize your dashboard experience and recommendations.

</details>

<details>

<summary><strong>What if I choose the wrong role or focus area during onboarding?</strong></summary>

No problem. You can update your preferences later in account settings. GEOReport will adjust recommendations accordingly.

</details>

<details>

<summary><strong>Why does GEOReport ask about team size?</strong></summary>

Team size helps GEOReport suggest the right workflows. For example, a solo user may get more “quick fix” tips, while agencies with large teams may get collaboration and white-labeling guidance.

</details>

<details>

<summary><strong>Does my onboarding choice lock me into one workflow?</strong></summary>

No. It just prioritizes what you see first. You can still access all audit types from your dashboard anytime.

</details>

<details>

<summary><strong>Will AI assistants know about the onboarding info I provide?</strong></summary>

No. Onboarding data is for GEOReport’s internal customization only. It’s not visible to AI assistants or outside platforms.&#x20;

</details>


---

# 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://georeport.gitbook.io/georeport-docs/getting-started/onboarding-setup.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.