Control your usage

Use Rankability's pooled usage confidently, avoid duplicate work, and understand rolling recovery windows.

Rankability is designed to be used without pricing every action. Full-platform on-demand work is pooled across the organization and shown as remaining percentages in Billing.

Work normally while usage is healthy

The usage indicator stays quiet during normal work. You do not need to optimize a credit wallet or compare tool prices. Use the scope that produces a useful result for the client.

It is still good operational practice to:

Confirm the correct client, project, market, and website.
Check whether equivalent work is already running or recently completed.
Avoid unnecessary platforms, locations, pages, competitors, or duplicate keywords.
Use a stable idempotency key for API or MCP creates and keep the returned job ID.
Review a high-impact estimate before starting a large crawl, scan, or generation batch.

When usage is low

Billing shows rolling 24-hour burst and 7-day general windows. Capacity recovers continuously as older activity rolls out. If a window reaches zero, new on-demand work pauses and the product returns a recovery time. Saved results and existing projects remain available.

Do not repeatedly retry a limited request. Wait until the returned recovery time, reduce avoidable parallel work, or contact support if a normal workload repeatedly reaches the cap.

Scheduled work

Scheduled tracking and monitoring are kept separate from on-demand windows. If scheduled work does not run, check the schedule, integration health, provider status, and queue state rather than treating it as pooled-usage consumption.

Usage by website

Billing shows relative low, typical, or high activity by website without exposing internal units. Use it to identify a client producing an unusual share of work, not to allocate action prices or rebill every task.

See Understanding billing and usage for plan allowances, protected legacy terms, and subscription changes.