Agent skill · marketing growth · composiohq
google_search_console-automation
Automate Google Search Console tasks via Rube MCP (Composio): search performance, URL inspection, sitemaps, and indexing status. Always search tools first for current schemas.
Why this skill is useful
Adds specific automation workflows and commands for Google Search Console that the AI wouldn't reliably generate on its own.
What it needs
Requires google_search_console account access. About 2k tokens when loaded. Last updated 2026-07-24. 71,973 stars on the source repository.
What this skill does
Google Search Console Automation via Rube MCP Automate Google Search Console operations through Composio's Google Search Console toolkit via Rube MCP. Toolkit docs: composio.dev/toolkits/googlesearchconsole Prerequisites Rube MCP must be connected (RUBESEARCHTOOLS available) Active Google Search Console connection via RUBEMANAGECONNECTIONS with toolkit googlesearchconsole Always call RUBESEARCHTOOLS first to get current tool schemas Setup Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming RUBESEARCHTOOLS responds 2. Call RUBEMANAGECONNECTIONS with toolkit googlesearchconsole 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. Confirm connection status shows ACTIVE before running any workflows Tool Discovery Always discover available tools before executing workflows: This returns: Available tool slugs for Google Search Console Recommended execution plan steps Known pitfalls and edge cases Input schemas for each tool Core Workflows 1. Discover Available Google Search Console Tools Review the returned tools, their descriptions, and input schemas before proceeding. 2. Execute Google Search Console Operations After discovering tools, execute them via: 3. Multi-Step Workflows For complex workflows involving multiple Google Search Console operations: 1. Search for all relevant tools: RUBESEARCHTOOLS with specific use case 2. Execute prerequisite steps first (e.g., fetch before update) 3. Pass data between steps using tool responses 4. Use RUBEREMOTEWORKBENCH for bulk operations or data processing Common Patterns Search Before Action Always search for existing resources before creating new ones to avoid duplicates. Pagination Many list operations support pagination. Check responses for nextcursor or pagetoken and continue fetching until exhausted. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills composiohq/google_search_console-automation