SEO GSC Wizard MCP

GA4 error pages

get_ga4_error_pages

Read-only

Reports GA4 error pages for the property linked to a site: sessions, page views, active users and bounce rate per error page, broken down by page title AND URL. GA4 has no native 404 signal, so error pages are identified by matching the pageTitle dimension against saved patterns (operators contains / equals / starts_with / ends_with / regex, case-insensitive, OR-ed together). By default it uses the patterns saved for the site in GSC Wizard; pass titleFilters to override them for one call without saving anything. Returns notConfigured when Google Analytics is not connected or no GA4 property is linked, and noPatterns when the site has no saved patterns and none were passed. totals counts each session and user once across all matching pages (not the sum of the rows), and bounceRate is a fraction 0-1, not a percentage. 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
`limit`	No	How many error-page rows to return, ordered by sessions.
`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
`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".
`titleFilters`	No	Override the page-title patterns for this call only (nothing is saved). Omit to use the patterns saved on the site in GSC Wizard's Error Pages report.
`comparisonEndDate`	No	Optional. End of the comparison period as YYYY-MM-DD. Provide BOTH comparison dates to compare two periods; omit both for no comparison (prev* fields are then 0 and hasComparison false).
`comparisonStartDate`	No	Optional. Start of the comparison period as YYYY-MM-DD. Provide BOTH comparison dates to compare two periods; omit both for no comparison (prev* fields are then 0 and hasComparison false).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`hint`	No
`range`	No
`reason`	No
`totals`	No
`account`	No
`siteUrl`	No
`patterns`	No
`timeZone`	No
`truncated`	No
`dataSource`	No
`errorPages`	No
`noPatterns`	No
`prevTotals`	No
`propertyId`	No
`hasComparison`	No
`notConfigured`	No
`patternSource`	No
`reauthRequired`	No
`comparisonRange`	No
`matchedRowCount`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

addedOutput schema / properties / prevTotals

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "activeUsers": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        },
+        "screenPageViews": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        },
+        "sessions": {
+          "$ref": "#/properties/range/anyOf/0/properties/days"
+        }
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / reauthRequired

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

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?