Account

Sites

A site is an installation point — one domain where Seena is live. DNS verification, recrawling, retention, and what's coming for native mobile.

Draft — for review.

A site in Seena is one installation point — usually one production web domain. Every site has its own unique identifier (site_id) that your install snippet references, and its own settings for crawling, agents, and retention.

A site can also be a native application like an iOS app. This capability is coming soon.

Creating a site

From the settings page, click add site. You'll be asked for:

  • Name — a human-readable label. Use something like "Seena Marketing" or "Studio89."
  • Primary domain — the production URL where the widget will run (example.com).

Once you submit, Seena generates a site_id and shows you the install snippet.

Install the widget

See the Install Seena page for instructions on how to install the widget on your site given the specific platform you're using.

What happens after verification

Seena does a one-time crawl of your site to learn what it is. The crawl:

  • Enumerates key pages by following links from your homepage, respecting robots.txt.
  • Extracts the structured content of each page.
  • Uses AI analysis to generate a product map (what your product is, who it's for) and page contexts (the purpose of each key page).

These contexts are what give interview agents enough understanding of your product to have a conversation. Without a crawl, the agent has to ask visitors things the context should already tell it.

The crawl happens in the background and usually finishes within 5-30 minutes depending on site size.

You can also manually edit a page's context from the dashboard. Manual edits are preserved across recrawls — Seena won't overwrite your changes unless you explicitly ask it to.

Native mobile — coming soon

Today, every Seena site is a web property. Native iOS and Android SDKs are in active development; they'll work as their own flavor of "site" in the same dashboard, with the same agents, triggers, and insights. If mobile-native install is on your critical path, let us know — it helps us prioritize.

What to read next