Actions29
- 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 specified 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 elements.
Typical use cases include:
- Monitoring keyword rankings and visibility.
- Analyzing competitor presence on SERPs.
- Extracting structured search result data for reporting or further processing.
- Tailoring SEO strategies based on real-time search results from specific locations, languages, and devices.
Example: You can input a keyword like "best running shoes," specify the location as "United States," language as "English," device as "desktop," and get a parsed list of Google search results relevant to that query and context.
Properties
| Name | Meaning |
|---|---|
| Keyword | The search query string (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 simulate where the search is performed. Supported locations are listed in the DataForSEO documentation. |
| Language | Full name of the search engine language to simulate the language setting of the search. Supported languages are listed in the DataForSEO documentation. |
| Device | The type of device to simulate the search from. Options: Desktop, 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 to override automatic selection based on location and language. Examples: google.co.uk, google.com.au, google.de. |
| Depth | Number of search results to retrieve, between 1 and 700. Default is 100. |
| Target | Optional filter to restrict results to a specific domain, subdomain, or webpage. Supports wildcards (*) for pattern matching. Examples: example.com (homepage URLs), example.com* (all pages under domain), *example.com* (all pages and subdomains), example.com/example-page* (all URLs starting with specified path). This narrows down the returned SERP elements to those containing URLs matching the target pattern. |
Output
The node outputs an array of JSON objects representing the parsed SERP data for each input item. Each object contains detailed information about the search results including organic listings, paid ads, featured snippets, knowledge panels, and other SERP features as provided by the DataForSEO API.
The exact structure depends on the API response but typically includes fields such as:
- Position/rank of each result.
- Title, snippet, and URL of each listing.
- Type of SERP element (organic, ad, local pack, etc.).
- Additional metadata like rich snippets, reviews, or images if available.
No binary data output is produced by this operation.
Dependencies
- Requires an active API key credential for the DataForSEO service configured in n8n.
- Internet access to call the DataForSEO v3 API endpoint at
https://api.dataforseo.com/v3. - Proper configuration of the node's credentials with valid API authentication tokens.
Troubleshooting
- Invalid or missing API credentials: The node will fail if the API key is not set or invalid. Ensure the API key credential is correctly configured.
- Unsupported location or language: Using unsupported values for location or language may cause errors or empty results. Refer to the official DataForSEO documentation for supported values.
- Exceeding depth limits: Requesting more than 700 results will be rejected. Keep the depth parameter within allowed bounds.
- Malformed keyword encoding: Improperly encoded special characters in the keyword may lead to unexpected results or errors. Use
%25for%and%2Bfor+as instructed. - Network issues or API downtime: Temporary connectivity problems or API service interruptions will cause execution failures. Retry after some time or check network status.