Google Relevant Pages Live
/dataforseo_labs_google_relevant_pages_live
- Finished calls, last 7 days
- 0
Cancellations excluded. Execution times cover successful calls.
Use it with your agent
Set up https://www.agentrouter.to/SKILL.md, then use DataForSEO’s /dataforseo_labs_google_relevant_pages_live endpoint through AgentRouter.
Inputs
targetRequired- domain required field the domain name of the target website the domain should be specified without https:// and www.
location_nameOptional- full name of the location optional field if you use this field, you don't need to specify location_code you can receive the list of available locations with their location_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available locations example: United Kingdom
location_codeOptional- location code optional field if you use this field, you don't need to specify location_name you can receive the list of available locations with their location_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available locations example: 2840
language_nameOptional- full name of the language optional field if you use this field, you don't need to specify language_code you can receive the list of available languages with their language_name by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available languages example: English
language_codeOptional- language code optional field if you use this field, you don't need to specify language_name you can receive the list of available languages with their language_code by making a separate request to the https://api.dataforseo.com/v3/dataforseo_labs/locations_and_languages ignore this field to get the results for all available languages example: en
item_typesOptional- display results by item type optional field indicates the type of search results included in the response Note: if the item_types array contains item types that are different from organic , the results will be ordered by the first item type in the array; you will not be able to sort and filter results by the types of search results not included in the response; possible values: ["organic", "paid", "featured_snippet", "local_pack"] default value: ["organic", "paid"]
limitRequired- the maximum number of returned pages optional field default value: 100 maximum value: 1000
offsetOptional- offset in the results array of returned pages optional field default value: 0 if you specify the 10 value, the first ten pages in the results array will be omitted and the data will be provided for the successive pages
historical_serp_modeOptional- data collection mode optional field you can use this field to filter the results; possible types of filtering: live — return metrics for SERPs in which the specified target currently has ranking results; lost — return metrics for SERPs in which the specified target had previously had ranking results, but didn't have them during the last check; all — return metrics for both types of SERPs. default value: live
ignore_synonymsOptional- ignore highly similar keywords optional field if set to true , only core keywords will be returned, all highly similar keywords will be excluded; default value: false
filtersOptional- 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 , not_in example: ["metrics.paid.count",">",0] [["metrics.organic.count",">",50],"and",["metrics.organic.pos_1","<>",0]] [[""metrics.organic.count",">",50"], "and", [["metrics.organic.pos_1","<>",0],"or",["metrics.organic.pos_2_3","<>",0]]] for more information about filters, please refer to Dataforseo Labs - Filters or this help center guide
order_byOptional- 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 you should use a comma to specify a sorting type example: ["metrics.paid.etv,asc"] Note: you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules example: ["metrics.organic.etv,desc","metrics.paid.count,asc"] default rule: ["metrics.organic.count,desc"] Note: if the item_types array contains item types that are different from organic , the results will be ordered by the first item type in the array
include_clickstream_dataRequired- Basic tariff only; the paid clickstream upgrade is disabled.
Example input
{
"target": "amazon.com",
"language_name": "English",
"location_code": 2840,
"filters": [
[
"metrics.organic.pos_1",
"<>",
0
],
"or",
[
"metrics.organic.pos_2_3",
"<>",
0
]
],
"limit": 3,
"include_clickstream_data": false
}Output
Native task result envelope; includes items, aggregates and pagination where supported.