Skip to main content
Glama

DataForSEO MCP Server

Apache 2.0
627

dataforseo_labs_google_domain_intersection

Identify keywords where two specified domains rank together in SERPs. Retrieve search volume, competition, CPC, impressions, SERP positions, and traffic data for strategic SEO and competitive analysis.

Instructions

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.

Input Schema

NameRequiredDescriptionDefault
filtersNoyou 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, not_in, match, not_match, ilike, not_ilike, like, not_like you can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more characters merge operator must be a string and connect two other arrays, availible values: or, and. example: ["keyword_data.keyword_info.search_volume","in",[100,1000]] [["first_domain_serp_element.etv",">",0],"and",["first_domain_serp_element.description","like","%goat%"]] [["keyword_data.keyword_info.search_volume",">",100],"and",[["first_domain_serp_element.description","like","%goat%"],"or",["second_domain_serp_element.type","=","organic"]]]
ignore_synonymsNoignore highly similar keywords, if set to true, results will be more accurate
include_clickstream_dataNoInclude or exclude data from clickstream-based metrics in the result
intersectionsNodomain 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 both domains will be provided in the results array Note: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million if you specify intersections: false, you will get the keywords for which the domain specified as target1 has results in SERP, and the domain specified as target2 doesn’t; thus, the corresponding SERP elements and other data will be provided for the domain specified as target1only default value: true
language_codeNolanguage code required field example: enen
limitNoMaximum number of keywords to return
location_nameNofull name of the location required field in format "Country" example: United KingdomUnited States
offsetNooffset in the results 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
order_byNoresults 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 you should use a comma to set up a sorting parameter example: ["keyword_data.keyword_info.competition,desc"] default rule: ["keyword_data.keyword_info.search_volume,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["keyword_data.keyword_info.search_volume,desc","keyword_data.keyword_info.cpc,desc"]
target1Yestarget domain 1
target2Yestarget domain 2

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "filters": { "anyOf": [ { "items": [ { "type": "string" }, { "enum": [ "regex", "not_regex", "<", "<=", ">", ">=", "=", "<>", "in", "not_in", "ilike", "not_ilike", "like", "not_like" ], "type": "string" }, { "anyOf": [ { "type": "string" }, { "type": "number" }, { "type": "boolean" }, { "type": "array" } ] } ], "maxItems": 3, "minItems": 3, "type": "array" }, { "items": { "anyOf": [ { "$ref": "#/properties/filters" }, { "enum": [ "and", "or" ], "type": "string" } ] }, "maxItems": 7, "type": "array" } ], "description": "you can add several filters at once (8 filters maximum)\n you should set a logical operator and, or between the conditions\n the following operators are supported:\n regex, not_regex, <, <=, >, >=, =, <>, in, not_in, match, not_match, ilike, not_ilike, like, not_like\n you can use the % operator with like and not_like, as well as ilike and not_ilike to match any string of zero or more characters\n merge operator must be a string and connect two other arrays, availible values: or, and.\n example:\n [\"keyword_data.keyword_info.search_volume\",\"in\",[100,1000]]\n [[\"first_domain_serp_element.etv\",\">\",0],\"and\",[\"first_domain_serp_element.description\",\"like\",\"%goat%\"]]\n [[\"keyword_data.keyword_info.search_volume\",\">\",100],\"and\",[[\"first_domain_serp_element.description\",\"like\",\"%goat%\"],\"or\",[\"second_domain_serp_element.type\",\"=\",\"organic\"]]]" }, "ignore_synonyms": { "default": true, "description": "ignore highly similar keywords, if set to true, results will be more accurate", "type": "boolean" }, "include_clickstream_data": { "default": false, "description": "Include or exclude data from clickstream-based metrics in the result", "type": "boolean" }, "intersections": { "default": true, "description": "domain intersections in SERP\noptional field\nif 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 both domains will be provided in the results array\nNote: this endpoint will not provide results if the number of intersecting keywords exceeds 10 million\nif you specify intersections: false, you will get the keywords for which the domain specified as target1 has results in SERP, and the domain specified as target2 doesn’t;\nthus, the corresponding SERP elements and other data will be provided for the domain specified as target1only\ndefault value: true", "type": "boolean" }, "language_code": { "default": "en", "description": "language code\n required field\n example:\n en", "type": "string" }, "limit": { "default": 10, "description": "Maximum number of keywords to return", "maximum": 1000, "minimum": 1, "type": "number" }, "location_name": { "default": "United States", "description": "full name of the location\nrequired field\nin format \"Country\"\nexample:\nUnited Kingdom", "type": "string" }, "offset": { "description": "offset in the results array of returned keywords\n optional field\n default value: 0\n 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", "minimum": 0, "type": "number" }, "order_by": { "description": "results sorting rules\noptional field\nyou can use the same values as in the filters array to sort the results\npossible sorting types:\nasc – results will be sorted in the ascending order\ndesc – results will be sorted in the descending order\nyou should use a comma to set up a sorting parameter\nexample:\n[\"keyword_data.keyword_info.competition,desc\"]\ndefault rule:\n[\"keyword_data.keyword_info.search_volume,desc\"]\nnote that you can set no more than three sorting rules in a single request\nyou should use a comma to separate several sorting rules\nexample:\n[\"keyword_data.keyword_info.search_volume,desc\",\"keyword_data.keyword_info.cpc,desc\"]", "items": { "type": "string" }, "type": "array" }, "target1": { "description": "target domain 1", "type": "string" }, "target2": { "description": "target domain 2 ", "type": "string" } }, "required": [ "target1", "target2" ], "type": "object" }
Install Server

Other Tools from DataForSEO MCP Server

Related Tools

    MCP directory API

    We provide all the information about MCP servers via our MCP API.

    curl -X GET 'https://glama.ai/api/mcp/v1/servers/ravinwebsurgeon/seo-mcp'

    If you have feedback or need assistance with the MCP directory API, please join our Discord server