> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/getting-started/creating-a-new-client.md).

# Creating a new client

A client keeps one brand's knowledge, integrations, projects, Activity, audits, tracking, and Serena context together. Create a separate client only when the work needs an independent brand and evidence boundary—not simply because you want another project for the same website.

## What you need

Prepare:

* The client's primary website domain.
* The public brand name you expect Rankability to learn from that site.
* The primary language and service area when location matters; you can review these after the client exists.

You can connect Google services, add private sources, and refine the brand voice after the client exists.

1. Open **Clients**.
2. Select **New client**.
3. Enter the website, such as `example.com`. Rankability accepts the bare domain and validates that it looks like a complete website address.
4. Select **Add client**. Rankability creates the client and starts its initial brand setup.

Creating the client and its initial knowledge setup is included. On a per-website subscription, connecting the domain uses one paid website slot; Rankability asks an organization admin to confirm any required Stripe quantity change before activation. Grandfathered customers keep unlimited client websites at their protected price.

## If the domain already exists

When Rankability detects an existing accessible client for the same domain, use that client instead of creating a duplicate. This protects the brand knowledge, sources, Activity history, measurements, and existing work that Serena already uses.

If you intentionally need a second, isolated client for the same domain, create it only through a flow that explicitly warns you about the duplicate and offers **Create anyway**. The second client starts from scratch and does not inherit the original client's context.

## What to do next

1. Review the client name and domain in [Client settings](/account-and-settings/client-settings-reference.md).
2. Check the initial website context and add missing client material under **Settings → Sources**. See [Serena sources and data connections](/serena/advisor-knowledge-base-and-data-connections.md).
3. Connect the correct GSC, GA4, GBP, or other supported property only when the workflow needs it. A connected Google account is not complete until the intended property or profile is selected.
4. Ask Serena about the client or open **Activity**, then choose **Research**, **Create**, **Audit**, **Promote**, **Track**, or **Automate** for the next outcome.
5. Review the usage impact before starting an unusually large content, research, tracking, audit, promotion, or enrichment action.

Full-platform tools are included. Later high-impact actions can display a usage estimate before on-demand work begins. Your organization chooses whether to start or publish that work.

## Troubleshooting

* **The create button is unavailable** — Enter a complete dotted domain.
* **The suggested brand is wrong** — Correct the name and Brand & voice fields after creation in Client settings.
* **The wrong location was learned** — Correct the default location or service-area evidence in Client settings before location-sensitive work.
* **An existing client opens** — The domain already belongs to an accessible client. Continue there to preserve its history.
* **Client creation is blocked by the account state** — Follow the billing or upgrade action shown in the product. Existing clients remain available.
* **The site cannot be fully read** — Finish creating the client, then add the important material under **Settings → Sources**.

Continue with the [Quickstart checklist](/getting-started/quickstart-checklist.md) after the client opens.