Websites, workspaces and accounts
RankX AI has three levels. An account is billed and holds one credit wallet, a Client Workspace is one agency client, and a Website is one site you track.
RankX AI has three levels of structure. An account is the organisation that is billed, and it holds one credit wallet.
A Client Workspace is one client business, and only agency accounts have more than one. A Website is one site you track, and almost everything else belongs to a Website.
Most of the product is scoped to a Website, and billing, team and access are scoped to the account. Very little is scoped to a workspace, and knowing which is which explains most of the navigation.
How do the three levels fit together?
graph TD
A[Account: billed, one credit wallet] --> W1[Client Workspace]
A --> W2[Client Workspace]
A --> WP[Your own workspace: never capped by a client budget]
W1 --> S1[Website]
W1 --> S2[Website]
W2 --> S3[Website]
S1 --> D[Prompts, keywords, audits, content, history]A direct account has exactly one workspace, its own, and RankX AI hides the client level entirely rather than showing a level with one item in it. See choosing your track.
What is a Website?
A Website in RankX AI is one site you track. It carries a domain, a market, a brand profile and a competitor set, and it owns:
- Tracked AI visibility prompts and their check history.
- Tracked keywords, their positions and their AI Overview captures.
- AI Shopping prompts and the products it monitors, when the AI Shopping module is on.
- Website Audits and their findings.
- Content: briefs, articles and the Content Autopilot plan.
- Tasks.
- Its integrations: WordPress, Shopify, Search Console, Google Analytics and Bing Webmaster Tools.
If a screen asks which Website you mean, that is why: almost every measurement in RankX AI is a measurement of one site.
What is a Client Workspace?
A Client Workspace is one client business on the RankX AI agency track. It holds that client's Websites, its visibility permissions, its credit ceiling, its report schedules and its client users.
It is the unit an agency reports on and shares. Every agency also has its own workspace, which is not a client and is never capped by a client budget. See Client Workspaces.
What does an account hold?
A RankX AI account is the organisation that is billed. It holds:
- One credit wallet. There is never more than one, on either track.
- The plan, and every structural limit that comes with it.
- The team and its seats.
- MCP credentials for connecting AI agents.
- Email sending settings and, on the agency track, white label.
What is scoped where?
| Scoped to | Examples |
|---|---|
| A Website | Prompts, keywords, audits, content, tasks, brand profile, competitors, WordPress and Google connections |
| A Client Workspace | Visibility permissions, the credit ceiling, report schedules, client users |
| The account | The wallet, the plan, the team, MCP credentials, email sending, white label |
Settings follow the same split, in three bands. Website settings ask you to pick a Website, organisation settings never do, and account settings are about you. A settings section never mixes two bands, which is why the Website picker appears on some settings screens and not others.
Which words do these docs use?
These docs use one word per thing, as the product does:
| We say | Not |
|---|---|
| Website | project, site or property, for the object |
| Client Workspace | organisation, sub-account, client account |
| Agency Owner, Agency Admin, Agency Client | client user, client viewer, client admin |
| AI Overviews | the abbreviation |
| AI Answer Citations | Citation Sources |
The last two are retired names. The abbreviation reads as a fourth product area
to anyone who has not met it before, and the current citation names say which
engine each list comes from. The one place you will meet "project" is the
MCP server, where tools take a projectId.
How do plan limits follow this model?
Each limit is counted at the level it belongs to:
- Websites are counted per account. On the agency track they are a pool you distribute across workspaces however you like.
- Client Workspaces are counted per account.
- Tracked keywords and prompts are capped per Website, so a plan allowing 300 keywords allows 300 on each Website rather than 300 in total.
- Seats are counted per account. See team and seats.
- Credits are one balance per account.
The figures are in plans and limits.
Where to go next
- Choosing your track, if you are deciding between direct and agency.
- Client Workspaces, for the agency layer.
- Plans and limits, for the numbers.
- Glossary, for every RankX AI term in one sentence.
Questions
Do I need a Client Workspace if I only track my own site?
No. A direct account has one workspace of its own, and RankX AI hides the client level entirely. Client Workspaces exist only on the agency track.
Is the keyword limit per Website or per account?
Per Website. Tracked keywords and AI visibility prompts are capped for each Website, so a plan that allows 300 keywords allows 300 on every Website. See plans and limits.
Why do the MCP tools talk about projects?
A project is the internal name for a Website. The RankX AI interface says Website everywhere, while MCP tools such as list_projects take a projectId, which is the Website's id. See the MCP docs.
Last updated