Bot key limits: articles, product writes, post edits, research and deletes
Each bot key on SEOBetter, then AI bot access has its own daily limits, so a bot can never run away with your allowance or your content. Set them when you create the key, or change them in the key's row and click Save. Every limit resets at midnight in the site's time zone. The Today column shows what each key has used.
| Limit | Default | Maximum | What counts |
|---|---|---|---|
| Articles per day | 10 | 200 | Each new article the bot starts, and each item of a bulk article batch |
| Product writes per day | 50 | 2,000 | Each product SEOBetter writes for the bot: write-product, optimise-product (from Agent 0.5.6), each preview, a new product with SEOBetter writing its copy, and each such row of a product batch. Applying a preview does not count again |
| Post edits per day | 50 | 200 | Fixes, optimise and refresh on existing posts, rewrites of a post or page, and changes to a product's text, SEO fields, facts or back-in-stock date (update-product, set-seo-meta, add-product-facts, set-availability-date) |
| Keyword research calls per day | 20 | 200 | Each keyword research or clustering call (each one spends on your DataForSEO account) |
| Deletes | 5 a day | fixed | Every move to the trash. You can still delete as much as you like from wp-admin |
Product writes have their own limit
From SEOBetter Agent 0.5.1, product writes never use up Articles per day, so a shop can add a large catalogue and still publish its daily articles. Existing keys were given 50. A product batch that needs more writes than the key has left today is refused whole, and nothing is done. On top of the daily limit, creating and writing products are each limited to 500 an hour per user.
Your plan's allowance still applies
The daily limits only decide how fast a bot may go. Every article and every product write still counts against your plan's monthly SEOBetter Cloud allowance, or runs on your own AI key, exactly as it does when you work on the screens.
The bot can check its own limits
A bot can read its limits and what it has used today from get-site-context (the bot_key part), so it can plan its work instead of hitting a limit.
When a limit is reached
The bot gets a clear message such as "This bot key has started its 10 articles for today" or "This needs 30 product writes but this bot key has 20 of its 50 product writes left for today, so nothing was done". Raise the limit in the key's row, or wait for midnight. See "My bot cannot connect, or stops partway through".