$ loading_
Automate Google Search Console analytics, inspections, sitemap tasks, and site monitoring.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "google-search-console-automation" skill from askskill: 1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/google-search-console-automation/SKILL.md 2. Save it as ~/.claude/skills/google-search-console-automation/SKILL.md 3. Reload skills and tell me it's ready
Marketing or content teams can regularly query clicks, impressions, CTR, and ranking data for a site to track search traffic changes. It is suitable for baseline performance monitoring and keyword analysis.
Developers can inspect specific URLs to confirm indexing status and review reported issues. This is useful for validating search indexing after a page goes live.
When managing multiple properties, users can list accessible sites first and then review sitemap information for each site. This helps with routine site inventory checks and sitemap submission review.
The README explains how to use Google Search Console through Rube MCP for search analytics queries, URL inspection, site listing, and sitemap-related tasks. It covers prerequisites, connection setup, and core workflow examples. A key instruction is to call `RUBE_SEARCH_TOOLS` first to get the latest tool schemas and confirm the `google_search_console` connection is ACTIVE before running any workflow.
Query search analytics, inspect URLs, manage sitemaps, and monitor search performance using Google Search Console via Rube MCP (Composio).
Toolkit docs: composio.dev/toolkits/google_search_console
RUBE_MANAGE_CONNECTIONS with toolkit google_search_consoleRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit google_search_consoleUse GOOGLE_SEARCH_CONSOLE_LIST_SITES to retrieve all sites the authenticated user owns or has access to.
Tool: GOOGLE_SEARCH_CONSOLE_LIST_SITES
Parameters: (none required)
Returns: List of site entries with siteUrl and permissionLevel
Use GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY to get search performance data including clicks, impressions, CTR, and position.
Tool: GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY
Parameters:
- site_url (required): Site URL (e.g., "https://www.example.com/" or "sc-domain:example.com")
- start_date (required): Start date in YYYY-MM-DD format
- end_date (required): End date in YYYY-MM-DD format
- dimensions: Group by ["query", "page", "country", "device", "date", "searchAppearance"]
- search_type: "web" (default), "image", "video", "news", "discover", "googleNews"
- dimension_filter_groups: Filters for dimensions (operator: equals, notEquals, contains, notContains, includingRegex, excludingRegex)
- row_limit: Max rows (1-25000, default 1000)
- start_row: Pagination offset (default 0)
- aggregation_type: "auto", "byPage", "byProperty", "byNewsShowcasePanel"
- data_state: "final" (default), "all", "hourly_all"
Use GOOGLE_SEARCH_CONSOLE_INSPECT_URL to check the indexing status and issues for a specific URL.
Tool: GOOGLE_SEARCH_CONSOLE_INSPECT_URL
Parameters:
- inspection_url (required): Full URL to inspect (e.g., "https://www.example.com/page")
- site_url (required): Property URL (e.g., "https://www.example.com/")
- language_code: BCP-47 language (default: "en-US")
Use GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS to retrieve all sitemaps submitted for a site.
Tool: GOOGLE_SEARCH_CONSOLE_LIST_SITEMAPS
Parameters:
- site_url (required): Site URL (e.g., "https://www.example.com/")
- sitemap_index: Specific sitemap index URL to list sitemaps from
Use GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP to register or resubmit a sitemap for indexing.
Tool: GOOGLE_SEARCH_CONSOLE_SUBMIT_SITEMAP
Parameters:
- site_url (required): Site URL or domain property (e.g., "sc-domain:example.com")
- feedpath (required): Full sitemap URL (e.g., "https://www.example.com/sitemap.xml")
Use GOOGLE_SEARCH_CONSOLE_GET_SITEMAP to retrieve information about a specific submitted sitemap.
Tool: GOOGLE_SEARCH_CONSOLE_GET_SITEMAP
Parameters:
- site_url (required): Site URL
- feedpath (required): Sitemap URL to retrieve details for
GOOGLE_SEARCH_CONSOLE_SEARCH_ANALYTICS_QUERY with dimensions: ["date"] over a date range to track daily search performance trends.…
It uses Google Search Console through Rube MCP to query search analytics, list sites, inspect URLs, manage or view sitemaps, and monitor search performance.
You need Rube MCP connected and an active `google_search_console` connection created through `RUBE_MANAGE_CONNECTIONS`. You also need verified site ownership or the appropriate Google Search Console permissions.
Because the current tool schemas may change, the documentation explicitly recommends calling `RUBE_SEARCH_TOOLS` first to fetch the latest definitions before running workflows. This helps ensure the tools are called with the correct current parameters.
Automate Salesforce Service Cloud support tasks and ticket workflows via Rube MCP.
Generate creative domain names and check availability across multiple TLDs.
Automate API Ninjas tasks via Rube MCP with schema-first tool discovery.
Automate Gleap feedback and task workflows through Rube MCP.
Automate Yandex tasks and workflows through Rube MCP integrations.
Automate Xero invoices, contacts, payments, and bookkeeping records in the cloud.
Automate Moz SEO tasks via Rube MCP using current tool schemas first.
Automate Google Maps queries, geocoding, routing, and place detail retrieval.
Automate Yousearch tasks through Rube MCP and chain follow-up workflows.
Automate Serpapi workflows through Rube MCP for search data retrieval and processing.
Query Search Console data, manage sitemaps, and inspect URL indexing via AI.
Automate Google Super tasks and cross-tool workflows through Rube MCP.