The OnPage API is designed to crawl any website according to customizable parameters and analyze its performance against a multitude of benchmarks.
This API includes multiple endpoints that let you run advanced website health and performance analysis, spot duplicate tags and content on pages, assess keyword density, retrieve page-specific data, and more. Additionally, you can apply a broad set of crawl rules and parameters to control the crawl process and get more specific results.
Your account will be billed based on the number of pages you need to crawl, as well as other paid parameters you specified in the API request.
Pricing by mode
| Endpoint | Mode | Turnaround time * | Billing unit | Price |
|---|---|---|---|---|
Site Crawl
/on_page/task_post
|
Crawl modePOST + POST | Depends on crawl size and settings | Per crawled page | $0.00015$0.15 per 1K pages |
Instant Pages
/on_page/instant_pages
|
Live modeSingle POST request | Up to 2 seconds on average | Per task | $0.00015 |
Content Parsing
/on_page/content_parsing/live
|
Live modeSingle POST request | Up to 2 seconds on average | Per task | $0.00015 |
Page Screenshot
/on_page/page_screenshot
|
Live modeSingle POST request | Up to 2 seconds on average | Per task | $0.0048 |
Parameter support differs by endpoint. Check the endpoint documentation before applying parameters.
Turnaround times are averages and can vary slightly with load and task complexity.
Parameters & per-page cost Each parameter adds a fixed amount on top of the $0.00015 base; they stack additively
| Parameter | What it does | Per page total | Added cost |
|---|---|---|---|
load_resources |
Load images, stylesheets, scripts; detect broken resources | $0.00045 | +$0.0003 |
enable_javascript |
Execute page scripts during crawl | $0.0015 | +$0.00135 |
enable_browser_rendering |
Full browser emulation: styles, fonts, video. Required for Core Web Vitals (LCP, CLS, FID). Already bundles load_resources and enable_javascript; do not add those fees separately. | $0.0051 | +$0.00495 |
enable_content_parsing |
Parse page content structure and extract plain text | $0.0003 | +$0.00015 |
calculate_keyword_density |
Keyword density analysis per page | $0.0003 | +$0.00015 |
FAQ
Questions about OnPage API
How do I know when a crawl is finished?
Unlike most of our endpoints, a Site Crawl task runs over time rather than returning everything at once, so results become available progressively. Make a request to the OnPage Summary endpoint and check the crawl_progress field, which returns in_progress until the crawl completes and finished afterward, alongside crawl_status showing how many pages have been crawled and how many are still in the queue. You can also specify pingback_url when setting the task, and we will notify you as soon as the crawl is done.
Can I set custom thresholds for on-page checks?
Yes. The checks_threshold field in the Task Post request lets you customize the default threshold values for the parameters included in the checks array of OnPage API responses, so your crawl flags issues against your own benchmarks rather than our defaults. Note that only integer threshold values can be modified. Setting custom thresholds does not change the price of the crawl.
How do I keep a crawl within a predictable budget?
Since your account is billed per crawled page, the max_crawl_pages field is effectively the spending cap for the task: multiply it by the rate for your chosen parameter set to get the maximum you can be charged. You can narrow the crawl further with max_crawl_depth, crawl_sitemap_only, allowed_subdomains, and disallowed_subdomains.
How is the price for OnPage API endpoints calculated?
Your account is billed for each crawled page, and the rate depends on the parameters you set. The base rate is $0.00015 per crawled page, or $0.15 per 1,000 pages, and it covers 60+ on-page parameters, internal links, HTML, duplicate pages, page speed insights, non-indexable pages, and custom JavaScript.
So a crawl of 10,000 pages with the base parameter set is calculated as follows:
10,000 × 0.00015 = $1.50
The same crawl with browser rendering enabled is calculated as follows:
10,000 × 0.0051 = $51
The instant endpoints are priced per page as well: Instant Pages and Content Parsing Live cost $0.00015 per page, while Page Screenshot costs $0.0048 per page.