Ranking change: like for like or mix
webops_position_changeDid rankings really fall? Average position in two windows split into like for like, re-weighting, new and lost pairs, with a noise band; pairs moved by more than 2; impressions and clicks to tell position, demand or click loss. Another organization's or an unconnected site answers not found. Read-only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"domain": "<domain>"
},
"name": "webops_position_change"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| by | No | Break each part down by query, page or device. | |
| days | No | Window length in whole weeks of days (7, 14, … 182; default 28), ending on the latest day with data, against the same number of days before. | |
| page | No | One page, exactly as webops_pages returns it. | |
| limit | No | How many of the biggest movers each way (default 5). | |
| query | No | Only this search. | |
| domain | Yes | ||
| after_to | No | Last day of the later window (same length as the earlier one). | |
| before_to | No | Last day of the earlier window. | |
| after_from | No | First day of the later window. | |
| before_from | No | Instead of days: first day of the earlier window (give all four). |