Getting started
Connect a Google account, review the requested read-only permissions and list the Search Console and GA4 properties available to that account.
VelaPrism combines focused tools with general Search Console and GA4 query engines. The service remains read-only and limited to properties your connected Google account can already access.
Connect a Google account, review the requested read-only permissions and list the Search Console and GA4 properties available to that account.
Focused reports plus explicit date ranges, dimensions, filters, search types, aggregation, data state and pagination.
Property discovery, metadata discovery, compatibility checks and flexible Core Reporting queries.
How identity, permissions, token handling, revocation and property-level access work.
The general Search Console engine accepts explicit startDate and endDate values, dimensions such as query, page, country, device and date, AND-combined filters, search type, aggregation mode, finalized or fresh data state, and pagination up to the upstream Search Console row limit.
The GA4 Core Reporting engine accepts one to four explicit date ranges, up to nine dimensions, up to ten metrics, common dimension and metric filters, sorting, metric aggregations and paginated results. Use metadata discovery to find property-specific custom fields and compatibility checks before combining uncertain dimensions and metrics.
Focused top-query, top-page and landing-page tools return up to 200 rows. The general Search Console engine supports up to 25,000 rows per request; the general GA4 engine deliberately caps MCP responses at 10,000 rows per request and supports offsets for pagination.
Search Console and GA4 data can have processing delays. VelaPrism does not make fresher data appear than the upstream Google APIs provide.
If a property does not appear, first confirm that the same Google account can access it in Search Console or GA4. Requests to a property the account cannot access return a structured permission error rather than the upstream Google error payload.
The normalized data engine is designed to support server-side period comparisons, decline and opportunity detection, Search Console-to-GA4 landing-page blending, dashboard views and additional data-source adapters without changing the MCP transport layer.
See Support for safe troubleshooting guidance.