DataForSEO
Seo Labs Google Domain Intersection
This endpoint will provide you with the keywords for which both specified domains rank within the same SERP. You will get search volume, competition, cost-per-click and other data on each intersecting keyword. Along with that, you will get data on the first and second domain’s SERP element discovered for this keyword, as well as the estimated traffic volume and cost of ad traffic. Domain Intersection endpoint supports organic, paid, local pack,
Usage based DataForSEOSEOdataforseo/dataforseo-labs-google-domain-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/dataforseo-labs-google-domain-intersection (Seo Labs Google Domain Intersection). Call inspect_tool with {"tool_id": "dataforseo/dataforseo-labs-google-domain-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/dataforseo-labs-google-domain-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 |
|---|---|---|---|
target1 | string | Yes | domain required field the domain name of the first target website the domain should be specified without https:// and www. |
target2 | string | Yes | domain required field the domain name of the second target website the domain should be specified without https:// and www. |
location_name | string | No | full name of the location required field if you don't specify location_code Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_name by making a separate |
location_code | integer | No | location code required field if you don't specify location_name Note: it is required to specify either location_name or location_code you can receive the list of available locations with their location_code by making a separate request to t |
language_name | string | No | full name of the language required field if you don't specify language_code Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_name by making a separate |
language_code | string | No | language code required field if you don't specify language_name Note: it is required to specify either language_name or language_code you can receive the list of available languages with their language_code by making a separate request to t |
intersections | boolean | No | domain intersections in SERP optional field if you set intersections to true, you will get the keywords for which both target domains specified as target1 and target2 have results within the same SERP; the corresponding SERP elements for bo |
item_types | string[] | No | search results type indicates type of search results included in the response optional field possible values: ["organic", "paid", "featured_snippet", "local_pack"] default value: ["organic", "paid"] |
include_serp_info | boolean | No | include data from SERP for each keyword optional field if set to true, we will return a serp_info array containing SERP data (number of search results, relevant URL, and SERP features) for every keyword in the response default value: false |
limit | integer | No | the maximum number of returned keywords optional field default value: 100 maximum value: 1000 |
offset | integer | No | offset in the items array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in the results array will be omitted and the data will be provided for the successive keywords |
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, <, <=, >, |
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 |
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/dataforseo-labs-google-domain-intersection",
"input": {
"location_code": 2250,
"language_code": "fr",
"target1": "hubspot.fr",
"target2": "salesforce.com",
"intersections": false,
"limit": 5
}
}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.