Settings Shared Page Ranking Keywords 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 |
|---|---|---|
| Pages | Numbered targets, e.g. | Required |
| Limit | Rows to return (1-1000, default 100). | Optional · 1 to 1000 |
| Offset | Rows to skip before the first returned row. | Optional |
| Filters | Filter 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 by | Sort rules as 'field,asc' or 'field,desc', e.g. ['keyword_info.search_volume,desc']; up to 3. | Optional |
| Item types | Search results type (default ['organic', 'paid']; values: ['organic', 'paid', featured snippet, local pack]) | Optional |
| Exclude pages | URLs of pages you want to exclude | 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 |
| Ignore synonyms | Ignore highly similar keywords (default false) | Optional |
| Include serp info | Include data from SERP for each keyword (default false) | Optional |
| Intersection mode | Indicates whether to intersect keywords (values: union, intersect union) | Optional |
| Include subdomains | Indicates if the subdomains will be included in the search (default true) | Optional |
| Include clickstream data | Include or exclude data from clickstream-based metrics in the result (default false) | Optional |
How to use Shared Page Ranking Keywords 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 pages.
Get the result
Your assistant runs Shared Page Ranking Keywords 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
- Before planning a page or campaign, use Shared Page Ranking Keywords and compare the returned search signals within the same market.
Shared Page Ranking Keywords 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 Shared Page Ranking Keywords 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 Shared Page Ranking Keywords?
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 Shared Page Ranking Keywords from your assistant
Connect once, then ask for it in plain words.