GA4 Analytics

## Quick judgement A capable, focused analytics toolkit that unifies GA4, Search Console, and Indexing API access into a consistent, script-friendly interface. It’s well-suited for agents or power users who need to answer concrete traffic/SEO questions or generate recurring reports, provided a Google Cloud project and service account are correctly configured. ## What it does well - **End-to-end analytics workflow**: From fetching data (GA4, Search Console, Indexing) to auto-saving raw JSON and generating markdown summaries. - **High-level functions for common questions**: `siteOverview`, `trafficAnalysis`, `contentPerformance`, `searchConsoleOverview`, `liveSnapshot`, etc. cover most analytics and SEO reporting tasks. - **SEO + traffic combined**: Being able to use GA4 and Search Console together (e.g., traffic + query data) is a strong fit for “why is traffic changing?” questions. - **Flexible date ranges**: Supports shorthands (`"30d"`), explicit dates, and GA4-style relative ranges, making it easy for an agent to map natural language queries to API calls. - **Result management**: Automatic JSON storage plus utilities (`listResults`, `loadResult`, `getLatestResult`) allow downstream analysis, audits, or reproducible reports. ## Key risks and limitations - **Credential and setup sensitivity**: Requires a correctly configured Google Cloud project, service account, and enabled APIs (Analytics Data, Search Console, Indexing). Misconfiguration will lead to failures that the agent must handle gracefully. - **Secret management risk**: GA4 private key and service account credentials are supplied via environment variables; improper handling could expose sensitive access. - **External dependency and quotas**: All operations depend on Google APIs (network reliability, rate limits, quotas, permissions). Heavy use (especially Indexing API) may hit limits. - **No built-in governance**: The skill will issue indexing requests (`reindexUrls`) as asked; there is no native guardrail around volume or URL scope. - **Developer-oriented interface**: While the functions are clear, initial setup requires familiarity with Node/TypeScript and Google Cloud. ## Recommended scenarios Use this skill when: - The user explicitly asks about **GA4 metrics, traffic, or engagement**, such as: - “Check site traffic for the last 30 days.” - “What pages get the most traffic?” - “What is my bounce rate and engagement rate this month?” - The user asks about **SEO/Search Console data**, such as: - “What are my top search queries?” - “Which pages get the most search clicks?” - “How do my search queries differ by device or country?” - The user needs **real-time analytics**: - “Who’s on the site right now?” - “Which pages are being viewed right now?” - The user requests **indexing actions or status checks**: - “Reindex these URLs.” - “Check if these URLs are indexed.” - The user asks to **compare periods** or track changes over time: - “Compare this month vs last month for traffic and conversions.” - “How has revenue changed compared to last quarter?” Avoid or be cautious when: - Valid Google credentials are not available or the user cannot provide a service account with the required access. - The user’s request involves **non-Google analytics systems** (e.g., Matomo, Adobe Analytics) or general BI operations outside GA4/Search Console/Indexing. - The user requests bulk or aggressive indexing operations that could trigger API limits or violate their own SEO strategy; apply rate and scope sanity checks in the calling agent. Overall, this skill is strong for data-rich, Google-centric web analytics and SEO workflows, assuming secure credential management and properly configured Google Cloud resources.