Subdomain Search Metrics

Compare a domain's subdomains by organic and paid ranking metrics to see how search visibility spreads across the site.

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

What the tool takes13 settings · 1 required

TargetLimitOffsetFiltersOrder byItem typesLanguage codeLanguage nameLocation codeLocation nameIgnore synonymsHistorical serp modeInclude clickstream data
Source: Settings come from the tool's live input schema, checked on 17 Nov 2026. Your assistant fills them from your request.

Settings Subdomain Search Metrics 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 · up to 255 characters
LimitRows to return (1-1000, default 100).Optional · 1 to 1000
OffsetRows to skip before the first returned row.Optional
FiltersFilter rules as nested arrays: [["field","op",value], "and", [...]], operators =, <>, <, <=, >, >=, in, not_in, like, not_like, regex, not_regex, match, not_match; up to 8 rules. Field names come from this API's filters…Optional
Order bySort rules as 'field,asc' or 'field,desc', e.g. ['keyword_info.search_volume,desc']; up to 3.Optional
Item typesDisplay results by item type (default ['organic', 'paid']; values: ['organic', 'paid', featured snippet, local pack])Optional
Language codeLanguage code, e.g. 'en'. Give language_name or language_code.Optional · up to 10 characters
Language nameFull language name, e.g. 'English'. Give language_name or language_code.Optional · up to 60 characters
Location codeNumeric location code from the locations dictionary, e.g. 2840 (United States). Give one of location_name, location_code, or location_coordinate.Optional
Location nameFull 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
Ignore synonymsIgnore highly similar keywords (default false)Optional
Historical serp modeData collection mode (default live)Optional
Include clickstream dataInclude or exclude data from clickstream-based metrics in the result (default false)Optional

How to use Subdomain Search Metrics 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 Subdomain Search Metrics 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: compare a domain's subdomains by organic and paid ranking metrics to see how search visibility spreads across the site.

Subdomain Search Metrics 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 Subdomain Search Metrics 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 Subdomain Search Metrics?

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 Subdomain Search Metrics from your assistant

Connect once, then ask for it in plain words.