Actions28
- Backlink Actions
- SERP Actions
- Business Data Actions
- On Page Actions
- Keywords Data Actions
- Labs Actions
Overview
The node integrates with the DataForSEO API to retrieve backlink-related data. Specifically, the "Get Backlinks Pages Summary" operation fetches summarized backlink information for specified targets such as pages, domains, or subdomains. This is useful for SEO professionals and digital marketers who want to analyze backlink profiles at scale, monitor link-building campaigns, or audit competitors' backlink strategies.
Typical use cases include:
- Aggregating backlink summaries for multiple URLs or domains in bulk.
- Monitoring backlink health and distribution across a website.
- Comparing backlink profiles of different domains or subdomains.
Properties
| Name | Meaning |
|---|---|
| Targets | A collection of up to 1000 targets (pages, domains, or subdomains) for which backlink summaries are requested. Domains and subdomains should be specified without https:// or www. prefixes; pages require full absolute URLs including protocol. The targets cannot belong to more than 100 different domains in total per request. |
| Include Subdomains | Boolean flag indicating whether backlinks from subdomains should be included in the summary. Defaults to true. |
Output
The node outputs an array of JSON objects, each representing the backlink summary data for one of the specified targets. Each object typically contains aggregated backlink metrics such as counts, referring domains, anchor texts, and possibly other SEO-relevant backlink statistics.
If binary data were involved (not indicated here), it would represent downloadable reports or files related to backlink data, but this operation focuses on JSON summary data only.
Dependencies
- Requires an active connection to the DataForSEO API via an API key credential configured in n8n.
- The node sends POST requests to
https://api.dataforseo.com/v3. - Proper API credentials must be set up in n8n to authenticate requests.
Troubleshooting
- Error: "Something went wrong" — This generic error may indicate issues such as invalid input parameters, exceeding API limits (e.g., more than 100 domains in targets), or network/API errors. Verify that the targets conform to the required format and count limits.
- Invalid target format — Ensure domains/subdomains do not include
https://orwww., and pages include full URLs with protocol. - API authentication failures — Confirm that the API key credential is correctly configured and has sufficient permissions.
- Rate limiting or quota exceeded — If the API returns rate limit errors, consider reducing batch sizes or implementing retry logic.