Open-source SEO, GEO, and marketing skills for AI agents.
Analytics Operating Contract
Read this before using Search Console or Google Analytics data.
- Follow
../../docs/mcp-connection.md. Let the live connector determine tool selection and schemas; establish the requested platform and property from current connection data. - State the property, timezone, source, date window, comparison window, dimensions, filters, and metric or conversion definition beside material findings.
- Prefer one broad, batched read over repeated narrow calls. Respect the tool's current quota and fan-out limits rather than copying limits from another platform.
- Separate observed facts, inferences, and recommendations. State freshness, sampling, thresholding, row caps, attribution, or tracking limitations.
- Keep Google Analytics, Search Console, and ad-platform attribution distinct. Reconcile their definitions before comparing values.
- Use capabilities whose current contract supports the requested change. Show the exact current/proposed state and rollback, then obtain explicit approval for sitemap or measurement-configuration changes.
- Confirm writes with returned before/after evidence or a fresh read. Never call an analysis, recommendation, or configuration draft published without live confirmation.