Security
Your RankX AI account's security settings, how sessions are revoked, what credentials exist, and what to do if one leaks.
Account security in RankX AI covers three things: your own sign-in and sessions, the credentials your account has issued, and the credentials your account holds for other systems.
The third is the one worth thinking about hardest, because those reach outside RankX AI.
Sessions
Sign-out revokes your session server-side, not just in the browser. That distinction matters: a client-side sign-out that only clears local state leaves the session valid, so a stolen token keeps working. RankX AI revokes it properly.
Use it from a machine you no longer control, or after you suspect anything.
Credentials your account issues
MCP personal access tokens and OAuth connections. Both can spend credits and, with the right scopes, edit a live public website.
Three properties to keep in mind:
Only the account owner can issue or approve one. That is a deliberate boundary, not friction.
Scopes are fixed at issue. A credential cannot be widened or narrowed later, so issuing one with only the scopes the job needs is the whole of the access control. A read-only token cannot be talked into writing.
They are listed with their last use. The MCP settings page is the inventory: what exists, who created it, when it was last used. Reading it occasionally is the cheapest security practice available here.
See MCP authentication.
Credentials your account holds
A WordPress Application Password, if you connected a site. RankX AI acts as that WordPress user and can never do more than that user could, which is why connecting as an account with the minimum capabilities is a real control rather than a formality.
Google OAuth grants for Search Console and Analytics, which are read-only. RankX AI never writes to either.
To revoke either, revoke it at the source: delete the Application Password in your WordPress profile, or remove the connection in your Google account. Both take effect immediately, and RankX AI reports the connection as needing attention rather than pretending it still works.
If a credential leaks
An MCP token. Revoke it on the MCP settings page. It stops working on its next request. Issue a replacement first if something depends on it: rotation is zero downtime.
An OAuth connection. Disconnect it in the connected-apps list rather than only removing the connector in the client. Disconnecting from RankX AI kills the connection and its current access token together; removing it only in the client leaves the grant alive.
A WordPress Application Password. Revoke it in the WordPress profile it belongs to. That is the whole disconnection: RankX AI holds no other credential for your site.
Then check what happened. The MCP settings page shows last-used times per credential, which is where an unexpected use shows up.
Two protections you get without doing anything
Replaying a used OAuth credential kills the connection. Presenting an authorisation code that has already been exchanged, or a refresh token that has already been rotated, is treated as evidence of theft rather than as an error, and the whole connection is revoked immediately.
The MCP rate limit fails closed. If the limiter cannot be read, the request is denied rather than allowed. On a surface that can spend credits and edit a live site, an unreadable limiter is a reason to stop.
Offboarding someone
Removing a person revokes their access on their next request, and revokes the MCP credentials they created.
That is the behaviour you want and it has a sequence: list the credentials, reissue anything still needed from an account that will remain, update the clients, then remove the person. See team and seats.
What RankX AI will not do
Worth stating, because these are the requests that get made:
- It will not create a WordPress user or an application password. No user writes at all.
- It will not install, activate or update a plugin or theme.
- It will not permanently delete WordPress content. Removal is to the trash, and there is no flag that changes that.
- It will not write to Search Console or Analytics. Both connections are read-only.
Where to go next
- MCP authentication, for scopes and revocation.
- Team and seats, for offboarding.
- The WordPress integration, for what the connection can reach.
Email sending
Sending RankX AI email from your own address. Domain authentication, per-client template overrides, and what still arrives from the platform.
Team and seats
Inviting people to RankX AI, what a seat counts, why Agency Clients do not consume one, and what happens to credentials when someone leaves.