> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/publishers/sites-and-zones/create-site.md).

# Adding a Site

As a Publisher, you add each website or traffic source to your account as a site. You must create a site before you can create ad zones on it.

* To add a site, navigate to the **Sites & Zones** tab.
* Click the **New Site** button.

{% hint style="info" %}
**Note**: One account can have a maximum of 200 active sites. There is no maximum number of archived sites.
{% endhint %}

![](https://2421941036-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoiffCg2y27CXM9bLruG3%2Fuploads%2FoPZtJaPgtW24zCLXOlQg%2FAdd-New-Site.png?alt=media\&token=3c29550f-f62d-4ef8-9ee4-e3490b36e491)

## Entering the Details for the Site <a href="#entering-the-details-for-the-site" id="entering-the-details-for-the-site"></a>

To finish adding the site, you need to complete each of the fields in the **New Site** box that appears.

![](https://2421941036-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoiffCg2y27CXM9bLruG3%2Fuploads%2FXuF24VvpoXD7BpD55bjl%2F1070new-site-details.gif?alt=media\&token=26d1bb3a-cf21-49fa-b11b-07fceadef8de)

**Name**

Enter a site name that lets you recognize the site in the [**Statistics**](/publishers/publisher-statistics.md) tab, for example, "example.com - Mainstream" or "Site 1".

**Description**

Enter a brief description of the site. If the website qualifies for Premium status, this description is displayed to advertisers.

**Type**

Select the type of site you are adding. For example, if it is a single site, you would select **Website**. Choosing the wrong option may prevent you from receiving the correct advertising and could negatively impact the revenue potential.

{% hint style="info" %}
**Note**: The available site types are determined by the Ad Server configuration.
{% endhint %}

**URL**

If your site type requires a URL, enter it here, including the "http(s)://" at the start.

**Main category**

Ensure that the category selection matches the submitted URL content. An incorrect category may result in site rejection. For example, a website containing nudity should use **Adult**, not **Entertainment & Lifestyle**.

When you have entered the details, click **Create Site**.

## Site Validation <a href="#site-validation" id="site-validation"></a>

After clicking **Create Site**, if you set the type as **Website**, you must validate ownership of the site before you can create ad zones. Follow the instructions on the pop-up that appears:

![](https://2421941036-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoiffCg2y27CXM9bLruG3%2Fuploads%2Fp48J2vKwchrqDVQpecLJ%2F1070site-verification.gif?alt=media\&token=3f355366-2f1f-486f-a06b-8808e9a60327)


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.exads.com/publishers/sites-and-zones/create-site.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
