SERP billing, limits and tokens
SEOMER separates included Standard monitoring quota from token-based Live and Priority workflows so users can control how often and how deeply they check SERP results.
How SERP usage is estimated
SEOMER shows billing previews before SERP runs and monitor saves. The goal is to help you understand how many checks a configuration may use before it starts running on a schedule.
Standard quota
Standard monitoring is the scheduled project workflow. Depending on the workspace plan, a monthly included Standard quota may be available. When the included quota is available, Standard checks use it first.
If usage exceeds the included quota and token overage is available, Standard checks may continue by using tokens. If no quota or tokens are available, checks may stop or produce an alert depending on workspace settings.
Live checks
Live checks are instant and token-based. They are intended for urgent validation, spot checks and one-off research. Because they run immediately, they should not be treated as routine scheduled monitoring.
Priority checks
Priority SERP is used for workflows that need faster or separate processing, such as backlink donor index checks. In that workflow, SEOMER checks whether a source URL appears in search results. This is not the same as Standard project-domain monitoring.
Depth and pages
Depth is counted in blocks of 10 results. Each block is treated as another page of results:
- Depth 10 = 1 page.
- Depth 20 = 2 pages.
- Depth 50 = 5 pages.
- Depth 100 = 10 pages.
Higher depth costs more because SEOMER has to inspect more result pages.
Stop on target found
If stop on target found is enabled, actual usage can be lower than the maximum estimate. For example, if the selected depth is 100 but the target is found on page 2, the check may only need the pages up to the found result.
The billing preview may reserve or estimate a maximum first, then actual usage depends on how much of the depth was needed.
HTML and screenshot snapshots
HTML and screenshot snapshots add storage and processing work. Enable them when you need proof, debugging or a visual record of the SERP. For routine monitoring, keep snapshots off unless you really need them.
How to reduce usage
- Use lower depth for routine daily checks.
- Enable stop on target found when confirmation is enough.
- Use Standard monitors for routine project tracking and Live only for urgent checks.
- Keep snapshots disabled unless you need HTML or screenshots.
- Use schedule previews to estimate monthly usage before saving.
Related SERP documentation
Related SERP guides
Continue through the SERP documentation cluster depending on what you want to configure next.
- SERP Monitoring Documentation — overview of Standard, Live, Priority and project-domain reporting.
- Standard SERP monitoring setup — scheduled monitoring for the project domain and its subdomains.
- Live SERP checks — instant token-based checks for spot validation.
- SERP reports — how to read keyword results, domains, features and snapshots.
- SERP billing, limits and tokens — how depth, schedules and snapshots affect usage.
- Backlink donor index checks — how donor source URLs are checked separately from project-domain reports.