SEO GSC Wizard MCP

Compare a site migration (A vs B)

compare_migration

Read-only

Before/after Search Console comparison for a site migration or restructure. Three modes: "cross-property" compares two GSC properties (old domain vs new); "two-urls" compares two URL-prefix sections within one property; "regex" splits one property by two regexes. Returns the daily clicks/impressions trend for each side, per-side totals, and the query and page winners/losers by click delta. Without goLiveDate both sides use the same date window (startDate/endDate): A vs B over one period. With goLiveDate it becomes a before/after comparison around the launch: side A is read over the before window and side B over the after window, placed by windowStrategy ("recent", the default: the last windowDays settled days vs the windowDays days before go-live; "from-go-live": the first windowDays days from go-live vs the windowDays days before it; "full": the 90 days before go-live vs everything since). windowDays defaults to 28; yoyBaseline compares with the same weeks a year earlier instead. The go-live result adds windows (dates, days since go-live, warnings), recoveryPct (B clicks per day as a % of A clicks per day; null under 10 baseline clicks) and trend buckets (lost / declined / stable / improved / new) for queries and pages; pages of two properties are joined by path. For the full health verdict (risk score, redirect checks, recommendations, projected recovery) use get_migration_health. Reads the ClickHouse warehouse when available, else the live Search Console API. Query and page lists cover at most the top 25,000 rows by clicks per side; truncated and truncationNote say when a cap was reached. Regexes are capped at 2,000 characters and must not nest quantifiers (for example (a+)+). Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	Yes	cross-property \| two-urls \| regex.
`limit`	No	Max query/page winners and losers to return per list (default 50).
`regexA`	No	Side A page regex (required for regex mode).
`regexB`	No	Side B page regex (required for regex mode).
`endDate`	No	Optional. Window end as YYYY-MM-DD (e.g. 2026-05-31). You do NOT need to know today's date or the latest available date: omit this and the server uses the latest settled Search Console date (data lags ~2-3 days behind today). Never pass null or the string "null".
`siteUrl`	Yes	Side A property (and the single property for two-urls/regex).
`siteUrlB`	No	Side B property (required for cross-property).
`startDate`	No	Optional. Window start as YYYY-MM-DD (e.g. 2026-05-03). You do NOT need to know today's date. Omit BOTH startDate and endDate to analyze the last 28 settled days automatically (Search Console data lags ~2-3 days). Never pass null or the string "null".
`goLiveDate`	No	Optional. First day the new setup was live, as YYYY-MM-DD. When given, side A is read over the before window and side B over the after window around this date (see windowStrategy), and the result adds windows, recoveryPct and trend buckets. Do not combine with startDate/endDate.
`urlPrefixA`	No	Side A URL prefix (required for two-urls): a full URL ("https://acme.com/old-blog/"), a host ("blog.acme.com/") or a path on any host ("/old-blog/"), as list_migrations returns them.
`urlPrefixB`	No	Side B URL prefix (required for two-urls), in the same forms as urlPrefixA.
`windowDays`	No	Only with goLiveDate. Window length in days for "recent" and "from-go-live" (default 28). Shortened to the post-launch days available.
`yoyBaseline`	No	Only with goLiveDate. Compare the after window with the same weeks one year (364 days) earlier instead of the days before go-live, which removes seasonality. Default false.
`windowStrategy`	No	Only with goLiveDate. "recent" (default): the last windowDays days vs the windowDays days before go-live, where the migration stands now. "from-go-live": the first windowDays days after go-live vs the windowDays days before, the launch dip included. "full": the 90 days before go-live vs every day since (lengths differ; per-day figures and recovery stay comparable).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	No
`note`	No
`pages`	No
`range`	No
`sides`	No
`queries`	No
`summary`	No
`windows`	No
`truncated`	No
`dailyTrend`	No
`dataSource`	No
`recoveryPct`	No
`recoveryNote`	No
`truncationNote`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedOct 11, 2026

addedInput schema / properties / goLiveDate

Added value: +{
+  "description": "Optional. First day the new setup was live, as YYYY-MM-DD. When given, side A is read over the before window and side B over the after window around this date (see windowStrategy), and the result adds windows, recoveryPct and trend buckets. Do not combine with startDate/endDate.",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

changedInput schema / properties / urlPrefixA / description

Previous value: -"Side A URL prefix (required for two-urls)."New value: +"Side A URL prefix (required for two-urls): a full URL (\"https://acme.com/old-blog/\"), a host (\"blog.acme.com/\") or a path on any host (\"/old-blog/\"), as list_migrations returns them."

changedInput schema / properties / urlPrefixB / description

Previous value: -"Side B URL prefix (required for two-urls)."New value: +"Side B URL prefix (required for two-urls), in the same forms as urlPrefixA."

addedInput schema / properties / windowDays

Added value: +{
+  "description": "Only with goLiveDate. Window length in days for \"recent\" and \"from-go-live\" (default 28). Shortened to the post-launch days available.",
+  "maximum": 365,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / windowStrategy

Added value: +{
+  "description": "Only with goLiveDate. \"recent\" (default): the last windowDays days vs the windowDays days before go-live, where the migration stands now. \"from-go-live\": the first windowDays days after go-live vs the windowDays days before, the launch dip included. \"full\": the 90 days before go-live vs every day since (lengths differ; per-day figures and recovery stay comparable).",
+  "enum": [
+    "recent",
+    "from-go-live",
+    "full"
+  ],
+  "type": "string"
+}

addedInput schema / properties / yoyBaseline

Added value: +{
+  "description": "Only with goLiveDate. Compare the after window with the same weeks one year (364 days) earlier instead of the days before go-live, which removes seasonality. Default false.",
+  "type": "boolean"
+}

addedOutput schema / properties / recoveryNote

Added value: +{
+  "$ref": "#/properties/mode"
+}

addedOutput schema / properties / recoveryPct

Added value: +{
+  "$ref": "#/properties/range/anyOf/0/properties/days"
+}

addedOutput schema / properties / truncated / $ref

Added value: +"#/properties/windows/anyOf/0/properties/yoyBaseline"

removedOutput schema / properties / truncated / type
```
Removed value: -[
-  "boolean",
-  "null"
-]
```

addedOutput schema / properties / windows

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "after": {
+          "$ref": "#/properties/windows/anyOf/0/properties/before"
+        },
+        "before": {
+          "anyOf": [
+            {
+              "additionalProperties": false,
+              "properties": {
+                "days": {
+                  "$ref": "#/properties/range/anyOf/0/properties/days"
+                },
+                "end": {
+                  "$ref": "#/properties/mode"
+                },
+                "start": {
+                  "$ref": "#/properties/mode"
+                }
+              },
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "daysSinceGoLive": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        },
+        "equalLength": {
+          "$ref": "#/properties/windows/anyOf/0/properties/yoyBaseline"
+        },
+        "goLiveDate": {
+          "$ref": "#/properties/mode"
+        },
+        "latestDate": {
+          "$ref": "#/properties/mode"
+        },
+        "strategy": {
+          "$ref": "#/properties/mode"
+        },
+        "timeline": {
+          "$ref": "#/properties/windows/anyOf/0/properties/before"
+        },
+        "warnings": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "code": {
+                "$ref": "#/properties/mode"
+              },
+              "message": {
+                "$ref": "#/properties/mode"
+              },
+              "severity": {
+                "$ref": "#/properties/mode"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "windowScale": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        },
+        "yoyBaseline": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

Changed2 schema fields changedOct 10, 2026
- addedOutput schema / properties / truncated
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / truncationNote
```
Added value: +{
+  "$ref": "#/properties/mode"
+}
```
First observedOct 7, 2026

TDQS

Score is being calculated.

All SEO GSC Wizard MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?