DataForSEO
Backlinks Page Intersection
This endpoint will provide you with the list of referring pages pointing to the specified targets. It is especially useful for finding the backlinks that point to your competitors but don’t point to your website.
Usage based DataForSEOSEOdataforseo/backlinks-page-intersectionActive
Use this tool with your agent
Give this to your agent
Use my connected Agentik MCP server. I want to use the tool dataforseo/backlinks-page-intersection (Backlinks Page Intersection). Call inspect_tool with {"tool_id": "dataforseo/backlinks-page-intersection"} first and tell me the price before anything runs. Ask me for the inputs it needs; never invent values, IDs or file URLs. When I confirm, call run_tool with tool_id "dataforseo/backlinks-page-intersection" and my inputs, follow it with get_run if it is still running, and give me the result and the price Agentik reports. If the tool is unavailable, say so and use discover_tools to propose an alternative.Show the prompt
Paste it into Claude, ChatGPT or Codex: your agent takes it from there, and shows the price before it runs.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
targets | object | Yes | domains, subdomains or webpages to get links for required field you can set up to 20 domains, subdomains or webpages a domain or a subdomain should be specified without https:// and www. a page should be specified with absolute URL (includi |
exclude_targets | string[] | No | domains, subdomains or webpages you want to exclude optional field you can set up to 10 domains, subdomains or webpages if you use this array, results will contain the referring pages that link to targets but don't link to exclude_targets e |
backlinks_status_type | string | No | set what backlinks to return and count optional field you can use this field to choose what backlinks will be returned and used for aggregated metrics for your targets; possible values: all - all backlinks will be returned and counted; live |
filters | any[] | No | array of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: regex, not_regex, =, <>, in |
order_by | string[] | No | results sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc - results will be sorted in the ascending order desc - results will be sorted in the descending order y |
offset | integer | No | offset in the results array of the returned backlinks optional fielddefault value: 0 if you specify the 10 value, the first ten backlinks in the results array will be omitted and the data will be provided for the successive backlinks |
limit | integer | No | the maximum number of returned backlinks optional fielddefault value: 100 maximum value: 1000 |
internal_list_limit | integer | No | maximum number of elements within internal arrays optional field you can use this field to limit the number of elements within the following arrays: attributes domain_from_platform_typedefault value: 10 maximum value: 1000 |
include_subdomains | boolean | No | indicates if the subdomains of the targets will be included in the search optional field if set to false, the subdomains will be ignored default value: true |
include_indirect_links | boolean | No | indicates if indirect links to the targets will be included in the results optional field if set to true, the results will include data on indirect links pointing to a page that either redirects to a target, or points to a canonical page if |
exclude_internal_backlinks | boolean | No | indicates if internal backlinks from subdomains to the target will be excluded from the results optional field if set to true, the results will not include data on internal backlinks from subdomains of the same domain as target if set to fa |
intersection_mode | string | No | indicates whether to intersect backlinks optional field use this field to intersect or merge results for the specified URLs possible values: all, partial all - results are based on all backlinks; partial - results are based on the intersect |
rank_scale | string | No | defines the scale used for calculating and displaying the rank, domain_from_rank, and page_from_rank values optional fieldyou can use this parameter to choose whether rank values are presented on a 0–100 or 0–1000 scalepossible values: one_ |
tag | string | No | user-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response |
How your agent calls it
First inspect_tool for the current schema and price, then run_tool with the published example after confirming your inputs:
{
"tool_id": "dataforseo/backlinks-page-intersection",
"input": {
"targets": {
"1": "football.com",
"2": "fifa.com"
},
"exclude_targets": [
"skysports.com"
],
"limit": 10,
"order_by": [
"1.rank,desc"
],
"filters": [
[
"2.domain_from_rank",
">",
400
],
"and",
[
"1.dofollow",
"=",
true
]
],
"internal_list_limit": 10
}
}Price and billing
- Price
- Usage based
- Model
- Usage based
- Detail
- Billed at the cost the provider reports for the call, never above $100. Your agent sees the maximum before running.
- The provider’s price, 0% markup.
- One prepaid balance for every provider; your agent sees the price before it runs.
- Pay for measured usage; unused reservations are released.