Actions29
- Backlink Actions
- SERP Actions
- Business Data Actions
- On Page Actions
- Keywords Data Actions
- Labs Actions
Overview
The node integrates with the DataForSEO API to perform an on-page audit check of a specified web page URL. It analyzes various aspects of the page such as loading resources, executing JavaScript, browser rendering emulation, and more, to provide detailed audit data. This is useful for SEO specialists, web developers, and digital marketers who want to assess the quality, performance, and compliance of web pages.
Typical use cases include:
- Checking SEO-related issues on a webpage.
- Validating microdata markup and spelling.
- Emulating browser behavior to see how a page renders with scripts and styles.
- Collecting raw HTML or custom JavaScript execution results.
- Using proxy pools or custom user agents to simulate different browsing environments.
Properties
| Name | Meaning |
|---|---|
| Target Page URL | The URL of the web page to audit. |
| Load image, stylesheets, scripts, and broken resources? | Whether to load all images, stylesheets, scripts, and even broken resources during the audit. |
| Load the scripts available on a page? | Whether to enable JavaScript execution on the page during the audit. |
| Emulate browser rendering? | Enables full browser rendering emulation including styles, images, fonts, animations, videos, and other resources. |
| Enable XMLHttpRequest on a page? | Whether to allow XMLHttpRequests (XHR) on the page during the audit. |
| Additional Fields | A collection of optional advanced settings: |
| - Disable the popup requesting cookie consent from the user? | Option to disable cookie consent popups during the audit. |
| - Return data on pages despite the timeout error? | If enabled, returns data even if the page fails to load within 120 seconds due to timeout. |
| - Custom User Agent | Specify a custom user agent string for the HTTP request. |
| - Accept Language | Set the language header for accessing the website; supports all locale formats (e.g., "en", "en-US"). |
| - Custom Javascript | Inject custom JavaScript code to be executed on the page during the audit. |
| - Enable microdata validation? | Enable validation of microdata markup on the page. |
| - Store HTML of a crawled page? | Save the raw HTML content of the audited page. |
| - Check spelling? | Enable spell checking on the page content. |
| - Custom threshold values for checks | Define custom threshold values for specific audit checks by specifying check names and their threshold values. |
| - Switch proxy pool? | Enable switching between proxy pools for the audit requests. |
| - Proxy Pool | Select a proxy pool region to use for scanning (options: Empty, US, DE). |
| - Preset for browser screen parameters | Choose a preset for browser screen size parameters (options: Empty, Desktop, Mobile, Tablet). |
| - Browser Screen Width | Set a custom browser screen width in pixels. |
| - Browser Screen Height | Set a custom browser screen height in pixels. |
| - Browser Screen Scale Factor | Set a custom scale factor for the browser screen. |
Output
The node outputs an array of JSON objects containing the audit results for each input URL. The structure includes detailed information about the page audit checks performed, such as resource loading status, JavaScript execution results, microdata validation, spelling check results, and any custom thresholds applied.
If the option to store raw HTML is enabled, the output will also contain the full HTML content of the audited page.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the DataForSEO API via an API key credential.
- The node sends POST requests to
https://api.dataforseo.com/v3. - No additional external dependencies are required beyond the configured API credentials.
- Optional proxy pool usage depends on availability of proxy services configured by DataForSEO.
Troubleshooting
- Timeout errors: Pages taking longer than 120 seconds to load may cause timeouts. Enabling the "Return data on pages despite the timeout error?" option can help retrieve partial data.
- Resource loading failures: If images, scripts, or stylesheets fail to load, ensure that the target URL is accessible and not blocking automated requests.
- JavaScript execution issues: Some pages heavily reliant on client-side scripts may require enabling both "Load scripts" and "Emulate browser rendering" options for accurate audits.
- Proxy pool misconfiguration: Selecting a proxy pool without proper access or quota may result in failed requests.
- Invalid URLs: Ensure the "Target Page URL" is correctly formatted and reachable.
- Custom JavaScript errors: Injected custom JS should be syntactically correct to avoid runtime errors during page evaluation.