dataforseo_labs_google_historical_rank_overview

This endpoint will provide you with historical data on rankings and traffic of the specified domain, such as domain ranking distribution in SERPs and estimated monthly traffic volume for both organic and paid results

Server Dataforseo dataforseo-mcp-server
Category Read
Risk class Low
Parameters 51 required

What dataforseo_labs_google_historical_rank_overview does on Dataforseo

AI agents call dataforseo_labs_google_historical_rank_overview 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.

ParameterTypeRequiredDescription
target string Yes target domain
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.

Why dataforseo_labs_google_historical_rank_overview needs a policy

This tool queries and retrieves historical ranking and traffic metrics from DataForSEO's database. It performs a read-only operation that returns aggregated SEO performance data. There are no side effects, no data modification, no code execution, and no financial transactions.

From the tool's definition Tool description states it 'will provide you with historical data on rankings and traffic' and 'estimated monthly traffic volume' — purely retrieval of analytics data with no modification, deletion, or execution of external operations.

Questions about dataforseo_labs_google_historical_rank_overview

What does the dataforseo_labs_google_historical_rank_overview tool do? +

This endpoint will provide you with historical data on rankings and traffic of the specified domain, such as domain ranking distribution in SERPs and estimated monthly traffic volume for both organic and paid results. It is categorised as a Read tool in the Dataforseo MCP Server, which means it retrieves data without modifying state.

What parameters does dataforseo_labs_google_historical_rank_overview accept? +

dataforseo_labs_google_historical_rank_overview accepts 5 parameters: target, language_code, location_name, ignore_synonyms, include_clickstream_data. Required: target. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on dataforseo_labs_google_historical_rank_overview? +

Register the Dataforseo MCP server in PolicyLayer and add a rule for dataforseo_labs_google_historical_rank_overview: 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.

What risk level is dataforseo_labs_google_historical_rank_overview? +

dataforseo_labs_google_historical_rank_overview is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit dataforseo_labs_google_historical_rank_overview? +

Yes. Add a rate_limit block to the dataforseo_labs_google_historical_rank_overview 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.

How do I block dataforseo_labs_google_historical_rank_overview completely? +

Set action: deny in the PolicyLayer policy for dataforseo_labs_google_historical_rank_overview. 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.

What MCP server provides dataforseo_labs_google_historical_rank_overview? +

dataforseo_labs_google_historical_rank_overview 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.