Search Traffic History

Follow a website's estimated organic and paid search traffic over time to compare longer-term acquisition trends.

  • 7 settings
  • REST API + MCP
  • Billed per run
  • Checked

1Your request

Use the AI/ML API MCP Search Traffic History tool. Show this website's organic and paid traffic history.

2What the tool takes7 settings · 2 required

TargetDate fromModeCountryDate toProtocolHistory grouping
Source: Settings come from the tool's live input schema, checked on 17 Nov 2026. Your assistant fills them from your request.

Settings Search Traffic History takes

You describe the task in plain words and your AI assistant fills these in. In code you pass them yourself.

SettingWhat it controlsTip
TargetTargetRequired
Date fromStart date of the historical period in YYYY-MM-DD format.Required
ModeScope of the target: exact (this URL only), prefix (URLs starting with the target), domain (the domain without subdomains), or subdomains (default, the domain and all its subdomains).Optional · default subdomains · one of exact, prefix, domain, subdomains
CountryTwo-letter country code (ISO 3166-1 alpha-2), e.g. 'us'.Optional · up to 2 characters
Date toEnd date of the historical period in YYYY-MM-DD format. Defaults to today.Optional
ProtocolProtocol of the target: both (default), http, or https.Optional · default both · one of both, http, https
History groupingTime bucket size for history rows: daily, weekly, or monthly (default). Each bucket is one billed row.Optional · default monthly · one of daily, weekly, monthly

How to use Search Traffic History with your AI assistant

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

  2. Describe the task

    Say what you need in one sentence, including the target.

  3. Get the result

    Your assistant runs Search Traffic History and shows what came back.

  4. 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: follow a website's estimated organic and paid search traffic over time to compare longer-term acquisition trends.

Search Traffic History in your code

In your AI assistant

MCP · sign in once with your AI/ML API account

MCP setup guide ↗

In your code

Backend, script or scheduled job

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 Search Traffic History 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.

See pricing

FAQ

Do I need a separate account for Search Traffic History?

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 Search Traffic History from your assistant

Connect once, then ask for it in plain words.