Settings Historical Google Search Results takes
You describe the task in plain words and your AI assistant fills these in. In code you pass them yourself.
| Setting | What it controls | Tip |
|---|---|---|
| Keyword | Keyword | Required |
| Date to | Ending date of the time range | Optional |
| Date from | Starting date of the time range | Optional |
| Language code | Language code, e.g. 'en'. Give language_name or language_code. | Optional · up to 10 characters |
| Language name | Full language name, e.g. 'English'. Give language_name or language_code. | Optional · up to 60 characters |
| Location code | Numeric location code from the locations dictionary, e.g. 2840 (United States). Give one of location_name, location_code, or location_coordinate. | Optional |
| Location name | Full location name exactly as listed in the locations dictionary, e.g. 'London,England,United Kingdom' or 'United States'. Give one of location_name, location_code, or location_coordinate. | Optional · up to 200 characters |
How to use Historical Google Search Results with your AI assistant
Connect AI/ML API
Click Try it now, pick your client and add the MCP server. You sign in with your AI/ML API account once.
Describe the task
Say what you need in one sentence, including the keyword.
Get the result
Your assistant runs Historical Google Search Results and shows what came back.
Keep going in the chat
Ask it to filter, compare or summarize the result, or to save it as a table.
Ways to use it
- For a search-research brief: inspect monthly snapshots of Google results for a keyword to compare how the search results changed over time.
Historical Google Search Results in your code
In your code
REST · your AI/ML API key, JSON records back
The same tool runs over REST with your AI/ML API key, so a backend, a script or a scheduled job can call Historical Google Search Results directly. Start with the Toolbox REST quickstart.
Pricing
Pay as you goBilled per run from your AI/ML API balance
- No subscription
- No seat fee
- One balance for every tool
Each run is billed from your AI/ML API balance, with no subscription or seat fee. Check the current price in your dashboard before large runs.
FAQ
Do I need a separate account for Historical Google Search Results?
No. It runs on your AI/ML API account and balance, from your AI assistant over MCP or from your code over REST.
Which AI assistants can use it?
Claude, ChatGPT, Cursor, Hermes, OpenClaw and other MCP clients. Add the AI/ML API MCP server once with the MCP quickstart.
Run Historical Google Search Results from your assistant
Connect once, then ask for it in plain words.