rankwatch
Login

How to respond when you hit a credit or seat limit

Diagnose RankWatch credit vs seat/package blocks and take safe operator actions until capacity is restored.

Prerequisites

  • Org owner for billing changes; operators may pause keywords with keyword manage rights

When an action fails, decide whether you hit credits, a seat/member limit, or a package limit. Fixes differ — spending less does not unlock a missing AI Visibility flag.

respond when you hit a credit or seat limit
respond when you hit a credit or seat limit

Steps

  1. Note the exact error (credit insufficient, seat limit, permission denied, or feature not enabled).
  2. Open Organization settings → Billing as org owner and compare credit usage vs package limits and seat/member caps.
  3. Credit pressure: pause low-value keywords, lower recheck cadence, defer large tool runs, and review pause or adjust tracking when credits are tight. Prefer pausing over deleting history.
  4. Seat / member limit: remove inactive members or archive unused workspace access before inviting more people; do not share logins.
  5. Feature gate (AI / Tools missing): confirm the package feature is off — upgrading or enabling the feature is required; more credits alone will not help.
  6. If you need more capacity, contact RankWatch support / your account manager. In-product online upgrades may show as coming soon on billing.

Outcome

Tracking and invites fail closed until capacity or package limits is restored. Document what you paused so you can resume after the next credit cycle or plan change.