> ## 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.

# Set up multiple Markets

> Create a separate Project for each country and language you want to measure.

A Project measures one Brand in one Market. Its country, language, and optional city or region define the measurement context. If you serve customers in more than one Market, set up a separate Project for each. A localized Website path helps Videntic read pages for one Market; it does not add another Market to that Project.

## Plan your Project scopes

Suppose one Brand serves Sweden in Swedish and Denmark in Danish from `example.com`:

| Project | Market | Localized Website path | Example customer question |
| - | - | - | - |
| Sweden | Sweden · Swedish | `/se` | “Vilka leverantörer levererar till Stockholm?” |
| Denmark | Denmark · Danish | `/da` | “Hvilke leverandører leverer til København?” |

Use a path only when the relevant pages actually live there. If the Website has no localized path for a Market, leave the field empty and review suggested Brand context and Prompts especially carefully. Do not assume changing the app's interface language changes a Project's Market or its measured Prompt language.

## Create each Project

1. Start a new Project in the appropriate Workspace. Enter the same primary Website domain if both Markets belong to that Brand.
2. Choose the first Market's country and language. If you measure one city or region, choose that scope and enter the place; otherwise use the country scope.
3. Enter the corresponding localized path under the Website URL, if one exists. Review the Website and Market before continuing.
4. Choose the Plan shown for that Project. Review its allowances and any checkout step.
5. Check the Brand Profile, Target Keywords, Competitors, audience, and proposed Prompts against that Market. Use customer questions in its language.
6. Finish setup, then repeat for the next Market. Choose its own country, language, path, and Prompt set.

**Expected result:** each Project has its own Prompt Library, Analyses, and Market-specific results. You can open each Project and inspect its evidence separately.

## Keep comparisons meaningful

* Reuse the Brand's canonical name and core facts across Projects. Localize customer questions and Market-specific offerings or Competitors where they differ.
* Keep a small set of comparable customer needs in each language, but write naturally rather than translating every Prompt word for word.
* Compare trends within a Project's Market and Prompt set. Two Projects may use different questions, Competitors, and AI Platforms, so their percentages are not automatically like-for-like.
* A localized path selects context for extraction and generation. It does not, by itself, make another domain a Brand-owned Citation source. Review Website ownership separately if you use additional domains.

If setup says the same domain is already tracked for that country, language, and city or region, check your existing Projects, including other Workspaces you own. Use a genuinely distinct Market for the next Project; changing only the localized path does not create a different Market.

Next, [review your first Analysis](/how-to/run-your-first-audit.md) in each Project. For Website and localized-path details, see [Add a Project website](/getting-started/add-a-website.md).


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