# Add a site
> Add a website to Checkend, install the tracking script with the install prompt, and check that events arrive.
A *site* is a website that sends events to Checkend. This page adds a site, installs the tracking script and checks that events arrive.
## Add the site
Add the site in the web UI with **Add site**, or with `ce`:
```sh
ce sites add example.com
```
You need write access to the project of the site. Checkend shows two things:
- **The script tag.** Put it in the `` of each page.
- **The install prompt.** Paste it into your coding agent. The agent installs the tag for you.
To select a privacy mode now, add `--privacy`:
```sh
ce sites add example.com --privacy strict
```
The default mode is `standard`. See [Privacy modes](#privacy-mode) below.
## The script tag
The tag loads the tracking script from your Checkend server:
```html
```
The script is smaller than 2 KB gzip. It records page views, route changes of single-page apps, outbound links, file downloads, 404 pages and web vitals. It sets no cookies.
Some frameworks need a small change:
| Framework | File | Note |
|---|---|---|
| Next.js | `app/layout.tsx` (App Router) or `pages/_document.tsx` (Pages Router) | Put the plain `
```
The web server of your site then sends two paths to Checkend:
| Path on your site | Goes to |
|---|---|
| `/ce/script.js` | `https://stats.example.com/js/script.js` |
| `/ce/e` | `https://stats.example.com/api/e` |
The install prompt has tested snippets for Next.js, Nginx and Caddy. Nginx example:
```nginx
location = /ce/script.js {
proxy_pass https://stats.example.com/js/script.js;
proxy_set_header Host stats.example.com;
proxy_ssl_server_name on;
}
location = /ce/e {
proxy_pass https://stats.example.com/api/e;
proxy_set_header Host stats.example.com;
proxy_ssl_server_name on;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
```
> **Caution**
> Add the address of the site's proxy to `--trusted-proxies` on the Checkend server. Without it, Checkend sees the proxy address for each visitor, and the countries are wrong.
> **Caution**
> Do not trust a Next.js server alone. Next.js rewrites pass the `X-Forwarded-For` header of the visitor through and do not add the visitor address, so a visitor can send a false address. Trust Next.js only when a proxy in front of it sets `X-Forwarded-For`, and visitors cannot reach Next.js directly.
## Privacy mode
Each site has one privacy mode: `strict`, `standard` (the default) or `extended`. The mode controls what Checkend keeps about each visitor. See [Privacy](/docs/concepts/privacy.md).
Change the mode of a site:
```sh
ce sites set example.com --privacy strict
```
The new mode applies to new events. Ingest keeps sites in memory for a short time (5 seconds by default), so a change takes effect within this time.
## Next step
[Connect your agent](/docs/start/connect-your-agent.md).
## Prompt for a coding agent
```text
Add Checkend analytics to this project.
1. Find the production domain of this project. Ask me if it is not clear.
2. Run `ce sites add `. If the site already exists, skip this step.
3. Run `ce sites prompt ` and read the `prompt` field of the JSON. It is the install prompt.
4. Follow the install prompt: add the script tag to the root layout, add the goal events for the signup and purchase forms, and add the goals.
5. After the deploy, run `ce sites verify --wait 5m`. Exit code 0 means that the first page view arrived.
If ce exits with code 2, tell me to run `ce login `.
```