What happens when a budget is spent

Every plan runs an analysis the same way and finds the same gaps. The one step of it that asks a language model — grouping the finished worklist into topics — spends the AI budget rather than the lookup budget, so it happens only on a plan that has one and only while it lasts. Otherwise what a larger plan buys is more of the same, and the allowances are stated on the pricing page rather than restated here, because a figure written in two places is a figure that goes wrong in one of them.

The kinds of allowance

• Projects: how many sites in how many markets you can hold at once.
• Keyword searches a day: a rate rather than a cap, reset each day.
• Tracked keyword slots: scheduled weekly checks, one per keyword and two for a keyword on a project tracking mobile as well.
• Audit pages a month: what a crawl spends by the page.
• Pages per crawl: the most one crawl reads, however much of the month is left.
• A monthly budget for looking things up, which every paid call is counted against.
• A monthly budget for AI visibility, which a plan either includes or does not. Drafting a post and grouping a worklist into topics spend it too.

The pricing table carries one further allowance that this list does not name — one only the larger plans include. That table is the complete list, with every figure in it. The workspace home shows your current figures for projects, keyword searches today, tracked keyword slots, audit pages this month and, on a plan that has one, the AI budget, each read from the same place its refusal reads, so a number there that looks like it fits does fit. The lookup budget and the allowance this list does not name are not among them: neither has a figure there. Pages per crawl is not used up at all — it is the most one crawl may read — and the Site audit screen states it beside its Crawl now button.

What stops, and what does not

Work that pauses

When a monthly lookup budget is spent, the work that brings new information into the workspace pauses — starting a run, a keyword search, a live look at a result page, a rank check, a crawl, a volume refresh, a backlink analysis, and the weekly checks behind the allowance the pricing table names and this list does not. Each of those is refused before anything is asked of anybody, so a refusal costs nothing.

Work that carries on

Everything that only rearranges what you have already paid for: sorting the worklist, marking a row done or not worth it, rebuilding the worklist from a finished run, saving a draft, tagging a tracked keyword, renaming anything. A run already started also finishes — its money is committed, and leaving it stuck halfway would be worse for everybody than letting it complete.

Read-only

A lapsed subscription puts a workspace into read-only, which is the same line drawn in a different place: anything you ask for that brings new information into the workspace or sends anything out of it is refused, and anything that rearranges what is there is allowed. It does not stop work already started — a run under way finishes, as it does when a budget runs out — and it disconnects nothing, so a connected Search Console or Analytics property goes on syncing its daily figures until it is disconnected. Nothing is deleted. Every project, run, worklist and import stays readable, so you can see exactly what you are not using.

The Free plan costs nothing and asks for no card, so a workspace on it is not in read-only — it simply has the smaller allowances that plan states.

No screen here shows you an amount owed

What suppliers charge this product for a lookup and what this product charges you are two different things, and no screen here adds them together or compares them. A plan is a flat fee, paid monthly or yearly, and it does not move with how much of an allowance you used. Paid yearly, every allowance and budget still counts per month. The first subscription goes through Stripe’s own checkout and every change after it through Stripe’s own billing portal, both reached from the Billing screen inside the app.