Settings
Every section of RankX AI's settings, grouped by what it belongs to. The three scopes, what a client user never sees, and where each one is documented.
RankX AI's settings are organised into three bands, by what the setting belongs to: one Website, the whole organisation, or you personally. That is the only structure worth learning here, because it answers the question people actually arrive with: change something in the Website band and it affects one site, change something in the organisation band and it affects every site and every colleague.
A section never mixes bands. If a setting is scoped to a Website it carries the Website in its address, and switching sites switches the setting you are editing.
The Website band
These are scoped to one Website. Switching Websites switches what you are editing.
| Section | What it holds | Open to an Agency Client | Documented at |
|---|---|---|---|
| Modules | The optional parts of RankX AI switched on for this Website, such as AI Shopping | Yes, to see; switching a module needs an admin | AI Shopping |
| Brand Book | Identity, products and services, voice, knowledge, authors and competitors | Yes, apart from removing rows | Brand Book |
| Content & CMS | Categories and tags, article defaults, publishing preferences | Yes | Publishing articles |
| Integrations | Search Console, Analytics and CMS connections | Yes | Integrations |
| Dashboard | Which cards appear on this Website's dashboard | Yes | The Dashboard |
| Products Monitored | The products RankX AI watches for in AI shopping answers, chosen from your store, from a suggestion or from a file | No | Products monitored |
| Shopping Surfaces | The shopping surfaces this Website's products are checked on | No | Shopping surfaces |
| Automation | Schedules for each check family with live credit estimates, Content Autopilot, and this Website's alerts | No | Check cadence |
| WordPress | Browse and edit the connected WordPress site | No | WordPress |
| AI Models | Which AI platforms track this Website, each with its per-check credit cost | No | Tracked platforms |
| Danger Zone | Delete this Website | No | Websites, workspaces and organisations |
Modules comes first because it decides what the rest of the band contains. Products Monitored, Shopping Surfaces and the AI Shopping tab of Automation appear once AI Shopping is switched on for the Website.
That third column is one rule applied eleven times rather than eleven decisions, and the rule is stated below under what an Agency Client never sees. Read it there rather than inferring it from the table: more than one of the closed sections looks harmless until you notice what running it spends or destroys.
Dashboard is worth calling out because it is the one people expect to be locked and is not. It changes which cards a single person sees on their own screen, spends nothing, and alters no agency-owned configuration, so locking it would put it out of reach of exactly the people most likely to want a simpler dashboard.
The organisation band
These are shared across every Website in the account, and every one of them is staff-only.
| Section | What it holds | Documented at |
|---|---|---|
| Organisation | Organisation details, all Websites, and who gets notified | Websites, workspaces and organisations |
| Team | The people in your organisation, their roles and invitations | Team and seats |
| Billing & Credits | Plan, credit wallet, usage history and invoices | Credits and billing |
| Sending domain and templates | Email sending | |
| AI Agent Access | Connect Claude, ChatGPT and other assistants: tokens and connected apps | MCP authentication |
AI Agent Access is hidden on a white-label domain. Its connect panel prints
rankxai.com endpoints, and a platform-branded endpoint inside a white-labelled
product is a brand leak. The server side already refused those requests; hiding
the panel aligns the interface with it. See white label.
The account band
These are yours, not the organisation's, and they follow you across every Website you can see.
| Section | What it holds | Documented at |
|---|---|---|
| Profile | Your photo, name and email. There is nothing else in it | Nowhere else, and it needs nothing |
| Privacy & Security | Sign-in methods, active sessions, and your data | Security |
What an Agency Client never sees
An Agency Client is somebody an agency invited to look at their own workspace. The boundary RankX AI enforces is one sentence: a client user may read their Website's data, and may not reach anything that spends the agency's money, alters agency-owned configuration, or exposes agency-internal information.
That is declared once, on the section, rather than being re-decided per screen. Hiding a section from the navigation is not on its own a gate, because typing the address ignores navigation, so every hidden section also refuses the request server-side. A test asserts the two agree, which is what stops a new section inheriting whichever behaviour the fall-through happens to give it.
See what clients can see for the whole picture from the client's side.
Automation: schedules, Content Autopilot and alerts
The Automation section carries schedules for Site Audit, Rank Tracking, AI Visibility and AI Shopping, each with a live credit estimate beside it, so you can see what a cadence costs before you choose it.
The Content tab switches Content Autopilot on for the Website and sets its cadence, monthly cap, article length and whether finished articles wait for review or publish. The topics it will write next are planned on Content Studio's Plan tab. The same tab sets whether an article must be approved before anyone publishes it, and how often your indexed pages are re-read.
The Alerts tab chooses which events this Website raises, overriding your organisation-wide defaults for this site alone.
RankX AI's rule here is worth knowing, because it is why you will not find a toggle that does nothing: no control without a stored setting behind it, and no stored setting without something that acts on it.
AI Shopping has its own tab rather than a row inside AI Visibility, because the two schedules are independent and priced differently. A shared control would imply one schedule where there are two.
The cadence rules themselves, including the floors that apply during a trial, are in check cadence.
Where to go next
- Brand Book, the largest section here and the one most of the product reads.
- Check cadence, for what the Automation section is setting.
- Plans and limits, for what your plan allows.
- Roles and permissions, for who can edit what.
Last updated