Billing & plans4 min read
Usage limits, quotas, and fair use
Quotas protect infrastructure and keep pricing predictable. Usage may be measured in pages crawled, jobs queued, API calls, or premium module runs depending on your plan.
Subscriptions, payments, invoices, and usage limits.
Steps
- Open usage or plan details in settings and note the reset window (monthly vs billing period).
- Identify which actions consume the most quota: full-site recrawls, Lighthouse batches, or frequent GEO refreshes.
- Schedule heavy jobs off-peak or stagger projects if you are near the limit.
- Upgrade or purchase add-on capacity if your team legitimately needs more volume.
- Contact support if usage looks wrong after a failed job that may have retried internally.
Common pitfalls
- Re-running the same huge crawl daily when weekly or diff-based monitoring would suffice.
- Ignoring warning banners until jobs start hard-failing at submission time.
Frequently asked questions
Do failed jobs still count toward usage?
Policies differ. Partial or failed runs may still consume resources; check your plan documentation or ask support with a job id.