Actions28
- Backlink Actions
- SERP Actions
- Business Data Actions
- On Page Actions
- Keywords Data Actions
- Labs Actions
Overview
The "Get Page Audit Check" operation of the On Page resource performs a comprehensive audit of a specified web page URL. It analyzes various aspects such as loading resources (images, stylesheets, scripts), browser rendering emulation, JavaScript execution, XMLHttpRequest enablement, and additional checks like microdata validation and spell checking. This node is beneficial for SEO specialists, web developers, and digital marketers who want to evaluate the technical health, content quality, and compliance of web pages.
Practical examples include:
- Auditing a landing page to identify broken resources or slow-loading elements.
- Checking if cookie consent popups are properly disabled during automated scans.
- Validating structured data markup on product pages.
- Emulating different device screen sizes and user agents to test responsive design.
- Running spell checks on page content to ensure professionalism.
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 page resources including images, stylesheets, scripts, and even broken resources during the audit. |
| Load the scripts available on a page? | Enable or disable JavaScript execution on the page during the audit. |
| Emulate browser rendering? | Emulate full browser rendering including styles, images, fonts, animations, videos, and other resources to simulate real user experience. |
| Enable XMLHttpRequest on a page? | Allow XMLHttpRequests (XHR) to be executed on the page during the audit. |
| Additional Fields | A collection of optional advanced settings: |
| - Disable the popup requesting cookie consent from the user? | Prevent cookie consent popups from interrupting the audit. |
| - Return data on pages despite the timeout error? | Return partial data even if the page fails to load within 120 seconds due to timeout. |
| - Custom User Agent | Specify a custom user agent string to use when accessing the page. |
| - Accept Language | Set the language header for the HTTP request in any locale format (e.g., "en", "en-US"). |
| - Custom Javascript | Inject custom JavaScript code into the page during the audit. |
| - Enable microdata validation? | Validate microdata markup on the page for correctness. |
| - Store HTML of a crawled page? | Save the raw HTML content of the audited page. |
| - Check spelling? | Perform spell checking on the page content. |
| - Custom threshold values for checks | Define custom threshold values for specific audit checks by name and value. |
| - Switch proxy pool? | Enable switching between proxy pools for the scan. |
| - Proxy Pool | Select a proxy pool region to route requests through (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 representing the audit results for each input URL. The JSON structure typically includes detailed information about the page audit checks performed, such as resource loading status, script execution results, microdata validation outcomes, spell check findings, and any errors or warnings encountered.
If enabled, the output may also contain the raw HTML of the crawled page.
Binary data output is not indicated for this operation.
Dependencies
- Requires an active API key credential for the DataForSEO service.
- Internet access to reach the target URLs and the DataForSEO API endpoint.
- No additional environment variables or n8n configurations are explicitly required beyond the API credential.
Troubleshooting
- Timeout Errors: If the page takes longer than 120 seconds to load, the node may throw a timeout error unless the "Return data on pages despite the timeout error?" option is enabled.
- Resource Loading Issues: Enabling resource loading or browser rendering can increase processing time and may cause failures if the target site blocks automated requests or requires complex authentication.
- Proxy Pool Misconfiguration: Selecting a proxy pool without proper setup or quota may lead to connection failures.
- Invalid URLs: Providing malformed or inaccessible URLs will result in errors; ensure URLs are correct and publicly reachable.
- Custom JavaScript Errors: Injected custom JavaScript that contains errors may affect the audit results or cause unexpected behavior.
- API Credential Errors: Missing or invalid API credentials will prevent the node from functioning and produce authentication errors.