> ## Documentation Index
> Fetch the complete documentation index at: https://docs.videntic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Create a Project, review the questions it measures, and read your first results.

Have your Website URL and two or three real customer questions ready. This path follows the current Project setup flow; the Plan and checkout steps can differ for a Workspace with an existing or externally managed subscription.

## 1. Choose the Workspace and Market

1. [Create an account](https://app.videntic.com/signup) or sign in, then start a new Project. Choose the Workspace where it belongs if you have more than one.
2. Enter your primary Website URL. Choose the Market's country and language. If you serve a specific city or region, select that scope and enter the place.
3. If the pages for this Market live under a path such as `/se`, add that localized path under the Website URL.

**You should see:** the correct Website and Market before you continue. One Project measures one Market. For another country or language, [set up another Project](/how-to/set-up-multiple-markets). The localized path helps select Website content for this Market; it does not create another Market or change which domain you own for Citations.

**If this looks wrong:** correct the URL or Market now. Changing the domain after setup work has begun can discard context gathered for the previous domain. See [Add a Project website](/getting-started/add-a-website).

## 2. Choose a Plan

Review the Plan's Prompt, Competitor, and Technical Audit allowances. If prompted, complete hosted checkout before continuing. Any Trial offer and first charge are shown at checkout; do not assume every Workspace follows the same purchase path. [Compare Plans](/billing/plans).

**You should see:** the next setup step for your Brand. If checkout returns you to the Plan step, check whether payment completed before trying again.

## 3. Check the context Videntic found

Review the suggested Brand Profile, Target Keywords, and Competitors. Correct the Brand's offerings, remove unrelated Keywords, and keep only Competitors you genuinely want to compare. Then describe your audience and add Seed Questions in the words customers use.

For example, a Swedish supplier might use “Vilka leverantörer levererar till Göteborg?” as a Seed Question for a Swedish Market. A question copied from another language or Market can make the resulting Prompt set less useful.

**You should see:** suggestions that describe this Brand and Market. If the Website did not explain an offering clearly, enter the facts you know rather than accepting a poor suggestion.

## 4. Review what will be measured

On the final Prompt step, read the proposed questions. Edit unnatural wording, remove duplicates or irrelevant questions, and add missing customer questions. These become the active Prompts used in future Analyses. The library is a set of questions you choose to monitor, not a count of real searches.

**You should see:** a Prompt set that covers your important customer needs without repeating the same question. See [Build your Prompt Library](/how-to/manage-prompts) for importing and organizing more later.

## 5. Read the baseline

Finish setup to open **Project Overview**. The initial Analysis may still be running; check **Analysis History** for its status. Once it completes:

1. Read **AI Visibility** in Project Overview.
2. Open **Analytics → Share of Voice** to compare Brand Mentions with tracked Competitors. Review **Mentions** and **Citations** separately: a Mention is Brand text in a response; a Citation is a linked source.
3. Open **Prompts → Library** to confirm the questions behind the result.
4. Check **Technical Audit** separately for Website findings. Its Audit Run is a different process from an Analysis.

**You should see:** a first measurement to investigate, not proof that a particular page or change caused it. If a number seems surprising, open the response evidence and check the Prompt, Market, AI Platform, and Competitor set before acting. [Review your first Analysis](/how-to/run-your-first-audit) walks through that investigation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.