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 impressions data on each intersecting keyword. Along with that, you will get data on the first and second domain's SERP element ...
AI agents call dataforseo_labs_google_domain_intersection to retrieve information from Dataforseo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum number of keywords to return |
offset | number | — | offset in the results array of returned keywords optional field default value: 0 if you specify the 10 value, the first ten keywords in |
filters | array | — | Array-based filter expression. A single condition is a 3-element array: [field, operator, value]. Combine conditions with ["and"|"or"] between them: [condition, |
target1 | string | Yes | target domain 1 |
target2 | string | Yes | target domain 2 |
order_by | array | — | 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 sorte |
item_types | array | — | display results by item type indicates the type of search results included in the response |
intersections | boolean | — | 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 t |
language_code | string | — | language code required field example: en |
location_name | string | — | full name of the location required field only in format "Country" (not "City" or "Region") example: 'United Kingdom', 'United States', 'Canada' |
ignore_synonyms | boolean | — | ignore highly similar keywords, if set to true, results will be more accurate |
include_clickstream_data | boolean | — | Include or exclude data from clickstream-based metrics in the result |
Parameters from the server's own tool schema.
This is a data retrieval tool that queries the DataForSEO API for SEO analytics (domain intersection analysis, keyword rankings, search metrics). It performs no modifications, deletions, executions, or financial transactions. The tool simply returns analytical data about public search results and keyword metrics, making it a classic Read operation with low security risk even if misused by an AI agent.
From the tool's definition The tool 'dataforseo_labs_google_domain_intersection' retrieves and queries data about keyword rankings and metrics—'provide you with the keywords', 'You will get search volume, competition, cost-per-click and impressions data', 'you will get data on the…
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
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 impressions 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. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.
dataforseo_labs_google_domain_intersection accepts 12 parameters: limit, offset, filters, target1, target2, order_by, item_types, intersections, language_code, location_name, ignore_synonyms, include_clickstream_data. Required: target1, target2. The full parameter table on this page comes from the server's own tool schema.
Register the Dataforseo MCP server in PolicyLayer and add a rule for dataforseo_labs_google_domain_intersection: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Dataforseo. Nothing to install.
dataforseo_labs_google_domain_intersection is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dataforseo_labs_google_domain_intersection rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for dataforseo_labs_google_domain_intersection. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
dataforseo_labs_google_domain_intersection is provided by the Dataforseo MCP server (dataforseo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.