Actions28
- Backlink Actions
- SERP Actions
- Business Data Actions
- On Page Actions
- Keywords Data Actions
- Labs Actions
Overview
The "Get Parsed SERP" operation of the DataForSEO node retrieves and parses Google Search Engine Results Pages (SERP) data based on a specified keyword and search parameters. This node is useful for SEO professionals, digital marketers, and analysts who want to programmatically obtain detailed search results information such as organic listings, ads, featured snippets, and other SERP features.
Typical use cases include:
- Monitoring keyword rankings and visibility in different locations and languages.
- Analyzing competitor presence on SERPs.
- Extracting structured search result data for reporting or further processing.
- Customizing search queries by device type and operating system to simulate real user searches.
Example: A marketer wants to check how their website ranks for a specific keyword in the UK on mobile devices using iOS. They can configure this node with the keyword, location ("United Kingdom"), language ("English"), device ("mobile"), and OS ("iOS") to get parsed SERP data tailored to that scenario.
Properties
| Name | Meaning |
|---|---|
| Keyword | The search query keyword (up to 700 characters). Special URL-encoded characters like % and + must be encoded as %25 and %2B respectively. |
| Location | Full name of the search engine location to target (e.g., "United States", "United Kingdom"). Determines the geographic context of the search. Supported locations are listed in the DataForSEO documentation. |
| Language | Full name of the search engine language (e.g., "English", "French"). Defines the language context of the search. Supported languages are listed in the DataForSEO documentation. |
| Device | The device type to simulate for the search. Options: Desktop or Mobile. |
| OS | Operating system of the device. If Desktop is selected, options are Windows or macOS. If Mobile is selected, options are Android or iOS. |
| Search Engine Domain | Optional custom search engine domain (e.g., google.co.uk, google.com.au). By default, the domain is automatically chosen based on location and language. |
| Depth | Number of search results depth to retrieve, from 1 up to 700. Default is 100. |
| Target | Optional filter to specify a target domain, subdomain, or webpage to narrow down results. Supports wildcards (*) for flexible matching. Examples: - example.com — matches homepage URLs.- example.com* — matches all pages under the domain.- *example.com* — matches all pages and subdomains.- example.com/example-page* — matches URLs starting with the specified path. |
Output
The node outputs an array of JSON objects representing parsed SERP data for each input item. Each object contains detailed structured information about the search results, including but not limited to:
- Organic search results with titles, URLs, snippets.
- Paid ads and ad extensions.
- Featured snippets, knowledge panels, and other SERP features.
- Pagination and ranking metadata.
If binary data is present (not typical for this operation), it would represent associated media or files related to the SERP results, but this operation primarily returns JSON data.
Dependencies
- Requires an active API key credential for the DataForSEO service.
- Internet access to call the DataForSEO API endpoint at
https://api.dataforseo.com/v3. - Proper configuration of the node's credentials within n8n to authenticate API requests.
Troubleshooting
- Invalid keyword encoding: Ensure special characters in the keyword are properly URL-encoded as described (e.g.,
%as%25). - Unsupported location or language: Verify that the location and language names match those supported by DataForSEO; refer to their official documentation.
- API authentication errors: Confirm that the API key credential is correctly set up and has sufficient permissions.
- Depth value out of range: The depth must be between 1 and 700; values outside this range will cause errors.
- Empty or incomplete results: Check if the target filter is too restrictive or if the keyword yields no results in the specified location/language/device combination.
Common error messages typically indicate issues with parameter validation or authentication failures. Reviewing the node’s input parameters and credentials usually resolves these.