n8n Google Search Console MCP Server: SEO Tools

Turn n8n into a Google Search Console MCP Server for real SEO data—one credential, 18 tools

This n8n workflow exposes Google Search Console capabilities through an MCP Server interface, so any MCP client (like Claude or Cursor) can call SEO-focused tools for search analytics, URL inspection, sitemap management, Indexing API notifications, site verification, and PageSpeed/Core Web Vitals—without writing code nodes or building sub-workflows.

What this workflow does

• Makes n8n act as a Google Search Console MCP Server that auto-discovers tools when an MCP client connects to the MCP Server Trigger endpoint.
• Provides 18 single-call HTTP Request Tools, each making one Google API request via one shared Google credential (no Code nodes, no sub-workflows).
• Manages Search Console sites: list, get, add, and delete Search Console properties.
• Handles verification & ownership: generate FILE/META/DNS verification tokens, verify ownership, and list/update verified owners using the Site Verification API.
• Manages sitemaps: list sitemap index/children, fetch sitemap status, submit, or delete.
• Pulls search analytics: clicks, impressions, CTR, and position by query/page, plus filters (country, device) with pagination and optional server-side dimension filters.
• Inspects URLs: index status, coverage, canonical, mobile usability, and rich results.
• Calls the Indexing API: notify/update or delete single or bulk URLs (up to 100) and read notification metadata.
• Runs PageSpeed Insights: returns real-user Core Web Vitals (LCP, INP, CLS) and a performance score.

Use cases

• Automate SEO reporting by querying Google Search Console analytics by country/device and date range.
• Verify new Search Console properties and configure ownership using token-based verification.
• Submit updated URLs via the Indexing API and track notification metadata for debugging.
• Check URL index coverage, canonical, and mobile usability when investigating performance or indexing issues.
• Fetch PageSpeed/Core Web Vitals to prioritize fixes using LCP/INP/CLS data.

Technical details

• Setup: in Google Cloud, enable Google Search Console API and Web Search Indexing API (four APIs total as required by the workflow).
• n8n tools/nodes: n8nn8n-nodes-langchainmcp trigger (MCP Server Trigger) and HTTP Request Tool endpoints.
• Execution model: each MCP tool is a single HTTP request mapped to the relevant Google API for SEO automation.