# Manage websites

> Switch between the websites Mark tracks, add one, pick the primary one, copy each site's snippet, and set how each site captures its lead form.

Source: https://docs.use-mark.com/docs/manage-websites

**Settings** > **Websites** shows one site at a time. The site's name at the
top is a menu: select it to switch to another site, or to add one. The page
opens your primary site.

The first site is **primary**. It's the site **Home** shows. Each site has its
own snippet and its own readiness score, and every site reports into one
analytics project.

Until you add a site, the page says "No websites yet. Add one to get its tag,
a site audit, and an AI readiness score." Select **Add website** there to add
the first one.

## Switch sites

Select the site's name at the top of the page. The menu lists every site,
primary first, with a **Primary** badge on the primary one. Under each name
it shows the site's tag status and its readiness score once it has one.
Select a site to open it.

The tag status says when a page on that site last loaded its tag:

* **Tag seen** with how long ago, like "Tag seen 3 hours ago".
* **Tag not seen yet**. The snippet is ready, but no page on the site has
  loaded it. It updates within an hour of the first visit after you paste it.
* **Tag not seen in N days**. The tag loaded before, but not in the last
  week. The snippet may have been removed from the site.
* **No snippet yet**. See [When there's no snippet yet](#when-theres-no-snippet-yet).

When another site's tag is not seen yet, or not seen in a week, a link next
to the site's name says so, like "1 other site needs setup". Select it to
open that site. Only pages on the site's own domain, or a subdomain like
`www.`, count. A site that tells browsers to send no referrer
(`Referrer-Policy: no-referrer`) always reads **Tag not seen yet**, even when
its tag works.

## Add a website

1. Select the site's name at the top, then **Add website** at the bottom of
   the menu.
2. Enter the **Hostname**, like `verdella.com`. Use the bare hostname, with no
   `https://`, port, or path.
3. Optionally enter a **Name (optional)**, like "Main site". The menu shows
   the name, or the hostname if there's no name.
4. Select **Add website**. The button reads **Adding…** while it runs.

The new site opens with its snippet at the top, ready to install. If the
hostname isn't valid or the site is already listed, the dialog says so and
nothing is added.

## Edit a site

Under **Site details**, change the **Hostname** or **Name (optional)**, then
select **Save**.

## Make a site primary

1. Open the site you want **Home** to show.
2. Select **More actions** (**⋯**) next to **Site audit**, then **Make primary**.

The primary site has no **Make primary** option, and it shows a **Primary**
badge next to its name.

## Remove a site

1. Open the site, select **More actions** (**⋯**), then **Remove website**.
2. A dialog asks to confirm, like "Remove verdella.com?"
3. Select **Remove website** to confirm, or **Cancel** to keep the site.

Removing a site stops its tag working and deletes its readiness, audit, and
ranking history. The page then opens your primary site.

## Copy a site's snippet

Each site has its own snippet under **Tag**. Check the name at the top before
you copy, so you install the right site's snippet.

1. Select **Copy**. It always copies the whole snippet. If the snippet is
   long, select **Show all N lines** to read it, and **Show less** to fold it
   again.
2. Paste it in the head of every page of that site, in the order given.

Mark's tag updates itself. You paste again only after a change to the
snippet, covered under form capture below. For the paste steps a site
owner follows, and what the capture and consent settings do on the site, see
[Install the site tag](/docs/install-the-site-tag).

### When there's no snippet yet

The snippet sends analytics through your own domain, so **Tag** shows no
snippet until that's set up. In its place, it shows a notice that says what's
missing:

* **No snippet yet: PostHog is not attached**. Mark has no analytics project
  for your workspace yet.
* **No snippet yet: reverse proxy not checked**. The project is attached, but
  Mark hasn't checked whether analytics runs through your domain. Select
  **Check again**.
* **Reverse proxy not enabled** or **Reverse proxy is not live**. Analytics
  doesn't run through your domain yet. Once it does, select **Check again**.

The other notices link to the PostHog connection, where Life With Data
finishes the setup. Every site's snippet appears once analytics runs through
your domain.

## Set up form capture

**Form capture** shows what that site's tag reports when a
visitor submits a form: the capture method, honeypot field, Google Tag
Manager, Cookiebot, and cookie consent. Each site has its own settings,
because the form on your main site usually isn't the form on a landing page.

1. Select **Edit capture**.
2. Pick a **Capture method**:
   * **No form capture**: the tag runs analytics only.
   * **A form in the site's own markup**: enter the **CSS selector** that
     matches the form, like `#enquiry` or `form.contact-form`.
   * **A HubSpot form**: optionally enter the **HubSpot form GUID
     (optional)**. Leave it blank to capture every HubSpot form on the page.
     HubSpot Forms V4 isn't supported.
3. Fill in any optional fields the site needs:
   * **Honeypot input name (optional)**: the name of the site's bot-trap
     input. A submission with it filled in is dropped.
   * **Google Tag Manager container id (optional)**: adds Tag Manager to this
     site's snippet.
   * **Cookiebot id (optional)**: adds Cookiebot to this site's snippet.
4. Pick a **Cookie consent** setting: **No cookie banner, track every visit**
   or **Wait for the cookie banner's answer**. Adding a Cookiebot id switches
   it to wait. You can change it back.
5. Select **Save**. The section shows "Capture settings saved."

Tag Manager, Cookiebot, and consent settings change the snippet itself. After
you change one, copy the site's snippet again and replace the old one on the
site. For what each setting does on the site, see
[Install the site tag](/docs/install-the-site-tag).

## Track AI assistant fetches

Under **AI assistant tracking**, a site built on Next.js 16 or later gets a
file that records each AI assistant fetch in your PostHog project. Copy the
file, deploy it, then select **Check AI assistant tracking**. For the steps
and what each result means, see
[Track AI assistant traffic](/docs/track-ai-assistant-traffic).

## Check a site's health

Select **Site audit** next to the site's name to open that site under
**Analysis** > **Website**. The badge next to the name shows the site's latest
readiness score. For what that page shows, see
[Check site readiness](/docs/check-site-readiness) and
[Site audit](/docs/site-audit).