Plans, team, and security

What counts toward a limit

A crawl counts when it starts, whether you launched it by hand or a schedule did. Opening reports, filtering, comparing crawls, and exporting never count. A site larger than your per-crawl URL cap is crawled up to the cap, never failed, and a crawl that would pass your monthly allowance is blocked with a clear message rather than silently billed. The app shows your usage before every run.

How metered credits behave

Features that call paid providers, AI fixes, the writer and paraphraser, AI visibility checks, rank checks, ad image generation, and Studio workflows, are metered. Three protections apply everywhere: the feature says it uses credits before you run it, your workspace shows observed usage in plain numbers, and monthly ceilings per plan bound the total. Deterministic features, reports, patches, planners, and the free tools never touch a provider.

Team roles and seats

Seats run from 1 on Free and Starter to 3 on Pro, 8 on Growth, and 16 on Scale. Invites go out by email with a tokenized link. Four roles: owner and admin can approve costly actions and manage the workspace, members do the daily work, and the read-only viewer exists for stakeholders who should see everything and touch nothing.

How your data is protected

Google connections are read-only and their tokens are encrypted at rest; disconnecting takes one click. API and share tokens are stored only as SHA-256 digests and shown once at creation. Guest report links expire, can carry passwords, and revoke instantly. Crawl artifacts live in private object storage behind short-lived signed URLs. And everything exports, xlsx, CSV, printable, API, so your data is never hostage to your subscription.

When something fails

Failures are designed to be boring. A crawl that a host rate-limits fails with a plain explanation and a re-crawl button; saved data from earlier crawls is never touched. Background jobs retry safely, stuck work is reaped automatically, and a provider outage marks the affected check as unavailable instead of overwriting your last good result. If a state ever looks confusing, the in-app troubleshooting guide walks the usual suspects, and the Support button reaches a person with your context attached.