Google Search Console

**Quick judgment**: Strong, focused integration for Google Search Console with well-documented usage and managed OAuth. Well-suited for SEO analytics and sitemap workflows inside OpenClaw. Main constraints are dependence on the Maton gateway, Google API limits, and the inherent scope of Search Console data. **Recommended scenarios** - When a user explicitly wants Google Search Console data (queries, pages, devices, dates) for SEO analysis or reporting. - When automating sitemap registration/cleanup for one or more sites. - When building SEO dashboards or periodic performance summaries for verified properties. **Key strengths** - Clean mapping to official Search Console endpoints (`sites`, `searchAnalytics/query`, `sitemaps`). - Managed OAuth via Maton: the tool only needs the MATON_API_KEY, not direct Google credentials. - Detailed examples (Python/JS) and guidance on URL-encoding, date ranges, dimensions, and pagination. **Risks & limitations** - Requires a Maton account, a valid MATON_API_KEY, and properly configured Google Search Console access, which may be non-trivial for some users. - Data is subject to Search Console constraints: ~16-month date limit, 2–3 day reporting delay, and maximum rows per request (25,000). - The tool can perform state-changing sitemap operations (PUT/DELETE), so the calling agent must avoid destructive changes without clear user intent. - Additional dependency on the Maton gateway and its rate limits (10 req/sec per account) and availability, on top of Google’s own reliability and quotas.