Understand limits, credits, seats, and account security

What counts as a limit

A crawl counts when it starts, regardless of whether you started it manually or on a schedule. Opening reports, filtering, comparing site scans, and exporting never count. A site larger than your URL limit per crawl will be crawled to the limit without an error occurring, and a crawl that would exceed your monthly quota will be blocked with a clear message and will not be silently billed. The app shows your consumption before each run.

How measured credits behave

Features calling paid providers, AI corrections, the author and paraphraser, AI visibility checks, rank checks, ad image generation and studio workflows are measured. Three protections apply across the board: the feature indicates that credits are being used before you run it, your workspace shows observed usage in simple numbers, and monthly caps per plan limit the total. Deterministic features, reports, patches, schedulers, and free tools never touch a vendor.

Team roles and seats

The places range from 1 for Free and Starter to 3 for Pro, 8 for Growth and 16 for Scale. Invitations are sent via email with a tokenized link. Four roles: Owner and admin can approve costly actions and manage the workspace, members do the day-to-day work, and the read-only viewer is there for stakeholders to see everything and touch nothing.

How your data is protected

Google connections are interpret-only and their tokens are encrypted at rest; Disconnecting is done with one click. API and share tokens are stored solely as SHA-256 digests and are displayed once upon creation. Links to guest reviews expire, may contain passwords, and are immediately revoked. Crawl artifacts reside in private object storage behind the short-lived signed URLs. And everything is exported, xlsx, CSV, printable, API, so your data is never held hostage to your subscription.

If something fails

Failures are supposed to be boring. A crawl where a host imposes a speed limit will fail with a simple explanation and a re-crawl button; Saved data from previous crawls is never touched. Background jobs are safely retried, stuck work is automatically harvested, and a provider failure marks the affected check as unavailable rather than overwriting your last good result. If a condition ever seems confusing, the in-app troubleshooting guide tackles the usual suspects and the support button puts you in touch with a person with your context.