The cost of all additional On-Page API parameters explained
There are two factors that make up the cost of using DataForSEO On-Page API: the number of crawled pages and additional parameters enabled for the crawl. Importantly, you are in full control of both factors, because when setting a task to On-Page API, you can specify the maximum number of pages to crawl and enable or disable certain crawl parameters.
Below, we will explain everything that concerns the cost of using On-Page API and all additional parameters.
The basic price of On-Page API
Additional parameters and their prices
“load_resources”
“enable_javascript”
“enable_browser_rendering”
“custom_js”
“calculate_keyword_density”
All On-Page API cost variations
The basic price of On-Page API
As we’ve already mentioned, one of the factors that influence the final cost of your On-Page request is the volume of crawled pages. The cost of one crawled page is the basic price for using On-Page API.
| Basic price – 1 page | 1,000 pages | 10,000 pages | 100,000 pages | 1,000,000 pages |
| $ 0.000125 | $ 0.125 | $ 1.25 | $ 12.5 | $ 125 |
You can avoid excessive spendings if you set a limit for pages to crawl in the body of your POST request to On-Page API, e.g.: “max_crawl_pages”: 1000.
Note that your account is charged for the actual number of crawled pages. If you specified more pages than a website contains, the difference will be automatically refunded to your account after a task is completed.
Additional parameters and their prices
In DataForSEO On-Page API, each additional parameter has its own price which applies to each crawled page. The price for using a parameter is then added to the basic price per page, and thus the final cost of the task increases.
Simply put, the price per crawled page will vary depending on the parameters you enable. We will list all additional parameters with their prices and will show you how the price per crawled page changes.
“load_resources”
When set to true, this parameter allows our crawler to load images, stylesheets, scripts, and broken resources.
| Parameter price | Final cost per page | How we calculate final cost |
| $ 0.00025 | $ 0.000375 | Basic price + Basic×2 $ 0.000125 + $ 0.00025 |
“enable_javascript”
When set to true, this parameter will instruct our crawler to load the scripts available on a page.
| Parameter price | Final cost per page | How we calculate final cost |
| $ 0.001125 | $ 0.00125 | Basic price + Basic×9 $ 0.000125 + $ 0.00125 |
“enable_browser_rendering”
When set to true, this parameter instructs our crawler to emulate browser rendering and measure Core Web Vitals. If you use this parameter, you also need to set enable_javascript and load_resources to true. However, note that the price for enable_browser_rendering already includes the price for enable_javascript and load_resources.
| Parameter price includes “enable_javascript” and “load_resources” |
Final cost per page | How we calculate final cost |
| $ 0.004125 | $ 0.00425 | Basic price + Basic×33 $ 0.000125 + $ 0.004125 |
“custom_js”
This parameter allows you to specify a custom JavaScript that will be applied to the crawled pages, e.g. a script to check if the pages contain a Google Tag Manager tracking code. If you use this parameter, you will receive the results of script execution in the “custom_js_response” array.
| Parameter price | Final cost per page | How we calculate final cost |
| $ 0.000125 | $ 0.00025 | Basic price + Basic×1 $ 0.000125 + $ 0.000125 |
“calculate_keyword_density”
When set to true, this parameter will instruct our crawler to calculate keyword density values for target site or specified webpages.
| Parameter price | Final cost per page | How we calculate final cost |
| $ 0.000125 | $ 0.00025 | Basic price + Basic×1 $ 0.000125 + $ 0.000125 |
All On-Page API cost variations
Below you can see a single table illustrating how the cost per crawled page or 1,000 pages varies depending on the applied parameter.
| Pages | Basic price | Cost of task with load_resources | Cost of task with enable_javascript | Cost of task with custom_js | Cost of task with calculate_keyword_density | Cost of task with enable_browser_rendering includes load_resources + enable_javascript |
|---|---|---|---|---|---|---|
| 1 | $ 0.000125 | $ 0.000375 | $ 0.00125 | $ 0.00025 | $ 0.00025 | $ 0.00425 |
| 1000 | $ 0.125 | $ 0.375 | $ 1.25 | $ 0.25 | $ 0.25 | $ 4.25 |
In order to calculate the cost of tasks with several parameters at once, we use the formula below. Note that the formula explains the calculation of cost for one crawled page. To calculate the full cost of your crawl, simply multiply the number of crawled pages by the obtained cost of one page.
cost = $ 0.000125 + $ 0.000125 × (2 + 9 + 1 + 1 + (33 – 2 – 9)) = $ 0.0045
And here’s what the numbers in this formula stand for.
cost = Basic + Basic × (load_resources + enable_javascript + custom_js + calculate_keyword_density + enable_browser_rendering - load_resources - enable_javascript))
The table below indicates the coefficients (weight) for each parameter and can be used for reference when calculating costs.
| Parameter | Coefficient |
| load_resources | 2 |
| enable_javascript | 9 |
| custom_js | 1 |
| calculate_keyword_density | 1 |
| enable_browser_rendering includes load_resources + enable_javascript |
33 |