Content SEO has separate counts for usage and planning headroom. Usage tracks blogs that have consumed an allowance. Headroom tracks how many additional blogs can be planned for the current cycle. A queued placeholder can affect planning before it consumes generation quota, so these numbers need not match.
Check the selected project’s Usage indicator and any message returned by the action you are trying to complete. The applicable allowance and reset interval depend on the project’s activation, configured plan features, and any valid override. A generic plan name is not enough to determine every limit.
The short version
- Check the correct project before interpreting its usage or remaining allowance.
- Separate the quota cycle from the subscription’s billing window.
- Planning headroom is not the same as unused generation quota.
- A hidden usage indicator or Generate More button does not, by itself, establish an unlimited plan.
How quota is measured
Per project, not per account
Content SEO counts usage and planned blogs for the selected project. Another project’s blog records do not enter that project’s count. However, the applicable plan feature or override is resolved through the account and project activation; do not assume that creating another project automatically grants a new paid allowance.
Check that each project has the intended Content SEO access and configuration. For account-level billing controls, see Billing.
The billing period and quota cycle
The billing window describes the subscription period. The quota cycle describes the interval used to count generation. The current implementation supports configurable intervals, including monthly, weekly, daily, and the subscription period. Consequently, a renewal date is not a universal explanation for every reset date.
For a monthly anchored cycle, shorter months can use their last day when the anchor day is unavailable. The subsequent cycle retains the original anchor day. Check the reset or expiry information shown for your project rather than applying this monthly behavior to every plan.
The Usage indicator can show Resets or Expires, depending on the resolved cycle. It can also be absent while loading or when quota information is unavailable. If the information does not load, investigate the error rather than interpreting a missing bar as unlimited access.
Check a yearly plan’s usage interval
Annual payment and a monthly generation allowance are different settings. A yearly subscription can use a configured monthly quota cycle, but the current code does not establish that every yearly or longer-term plan has the same monthly allowance.
Check the project’s actual allowance, interval, and expiry. Do not multiply a plan label into an annual pool or assume the full subscription allowance can be generated at once without confirming its configuration.
What each plan includes
Use the selected project’s current allowance and Plans & Pricing controls to understand its access. This page does not quote a universal software tier allowance: current plan-feature and account-override values are required to establish that number.
Generation usage and planning headroom
| Count | What it measures | How to use it |
|---|
| Usage | Blogs with a consumption timestamp inside the quota cycle | Check the generation allowance already consumed |
|---|
| Planning headroom | Allowance minus counted blogs scheduled in the cycle | Check room for additional planned blogs |
|---|
| Reset or expiry | The resolved cycle’s end | Check when that window ends, separately from eligibility to continue |
|---|
What counts toward your period
Usage is based on a consumption timestamp, not a blog’s current calendar date. The quota migration defines that timestamp as a one-time record when a blog reaches a qualifying state after waiting or generating. Rescheduling the blog does not move that recorded consumption into another cycle.
Planning headroom uses scheduled dates inside the cycle and excludes blogs currently marked Missed or Generation Failed. Placeholders and other counted statuses can therefore occupy planning space before generation has consumed an allowance.
Failure needs context. A first generation that fails before reaching a qualifying state has no consumption timestamp under that rule. A blog that already consumed an allowance does not lose its timestamp simply because a later regeneration fails. Do not assume that every failure refunds a slot or that calendar changes erase prior usage.
If a count looks wrong, identify the blog, its status, whether it was generated previously, and the cycle you are inspecting. Those details are more useful than comparing a calendar total with Usage as if they were identical counters.
Planning headroom is the configured allowance minus the blogs counted as planned in that cycle, with no negative headroom available for new requests. The Generate More flow checks this planning room before adding bonus blog placeholders.
Positive headroom does not guarantee that the button is offered or a request will succeed. The current screen hides it for particular plan codes, unlimited configurations, no remaining headroom, or no remaining days. The server also checks access, plan eligibility, the requested count, and a separate request cap.
After a successful request, check the result and choose dates for the added blogs. If title generation only partially succeeds, read the warning and inspect the placeholders instead of assuming every requested title is complete. See Generate More & Bonus Blogs for the workflow.
When you reach the limit
A manual generation request can be blocked when its applicable generation allowance is exhausted. The scheduled worker can defer a quota-exhausted blog to a later cycle, but continued generation still depends on eligible access and the project’s automation settings.
A reset is therefore not a promise that every queued post will generate or publish automatically. Expired access, missing plan features, lookup errors, and publishing configuration can require separate action.
Read the specific error and the project’s reset or expiry date. If considering an upgrade, confirm the resulting allowance and billing terms in the actual account controls before accepting a change. This quota page does not establish automatic charges, refunds, or an immediate increase for every upgrade.
Temporary quota boosts (overrides)
The implementation supports account feature overrides. A valid override can take precedence over a configured plan feature, and Custom can appear in the Usage indicator. An override can have an expiry; an expired or invalid expiry value is not treated as an indefinitely valid boost.
Do not assume an override always increases the allowance, applies only to one project, or lasts until renewal. Ask support to confirm the affected feature, effective value, scope, and expiry when investigating a custom allowance. Override support in the code is not a promise that every requested increase will be approved.
Quick answers
Why didn’t my quota reset at the start of the month?
Check the configured interval and displayed reset or expiry date. Monthly anchored cycles need not begin on the first day; other intervals follow their own rules.
Does every project receive a fresh copy of my plan’s allowance?
Counts are project-scoped, but access and the applicable allowance must be established for that project. Creating a project alone does not establish a new paid entitlement.
Did a failed generation use an allowance?
Check whether that blog had already consumed quota. A later failure does not clear an existing consumption timestamp.
Why is Usage different from planning headroom?
Usage counts consumption in the cycle. Headroom counts scheduled planning space in the cycle. A pending placeholder or rescheduled completed blog can make them differ.
Why is my usage indicator hidden?
An unlimited configuration is one possible reason. Loading, unavailable quota data, or a missing period can also hide it. Check the project’s actual access and error state.