The Better Google Search Console MCP server downloads your entire GSC dataset into local SQLite databases (no 1,000-row API limit) and provides powerful SEO analysis tools through Claude.
Setup & Sync
Discover all GSC properties, sync them individually or in parallel, and track background job progress or cancel if needed
Supports up to 16 months of historical data; all data stays locally on your machine
Analysis & Insights
Overview dashboard — View all properties at a glance with clicks, impressions, CTR, position, and trend sparklines
Property dashboard — Deep-dive into hero metrics, trend charts, top queries/pages, country breakdown, ranking distribution, new/lost queries, and branded split
16 pre-built insight types — including summary, top_queries, top_pages, growing/declining_queries/pages, opportunities (queries ranking 5–20 — quick wins), device_breakdown, country_breakdown, daily_trend, new_queries, lost_queries, and branded_split
Period comparison — Side-by-side comparison of two arbitrary date ranges across query, page, device, or country dimensions
Custom SQL queries — Run any read-only SELECT against the local search_analytics table for tailored analysis
Data Management
Automatic retention policy after each sync prunes low-value rows (e.g., zero-click impressions) while preserving actionable data
Manual pruning with a preview mode before deleting; reclaims disk space via VACUUM
Connects to Google services to retrieve and manage search analytics data for performance monitoring and keyword research.
Utilizes Google Cloud service accounts and API management to authenticate and facilitate secure access to Search Console property data.
Integrates with the Google Search Console API to download and analyze search performance data, enabling detailed SEO auditing through pre-built insights and custom SQL queries.
This project has been superseded by SEO Audit Console.
Better Search Console pulled your Google Search Console data into a local SQLite database so you could ask it real questions. That idea was right, and it is now the Search Console half of a bigger tool.
SEO Audit Console does everything this did - the API sync, the local database, the pre-built queries, the dashboards - and then joins it to a first-party crawl of your site and on-demand DataForSEO market data. The queries you came here for still exist. They just have more to work with.
Your crawl is intent. Search Console is reality. The money is where they diverge.
git clone https://github.com/houtini-ai/seo-audit.gitDocs and setup: github.com/houtini-ai/seo-audit
Related MCP server: seoagent
The npm package still installs. @houtini/better-search-console is deprecated, not unpublished. Nothing you have running will break.
This repository is archived. The code stays readable and every existing link keeps working, but there are no further releases, and issues and pull requests are closed.
Your data is unaffected. The SQLite databases this wrote are yours and stay where they are. SEO Audit Console builds its own.
There is no automated migration. SEO Audit Console syncs GSC itself, so point it at the same property and let it pull the history:
sync_gsc for https://example.com/It will fetch the window you ask for and build its own database, joined on a normalised URL key so the crawl and Search Console line up.
Part of the Houtini open-source MCP set. Questions: hello@houtini.com.
Cancel a running sync job. The job will stop gracefully after completing the current API call.
Inputs: jobId (required).
Check the status of a background sync job. If no jobId provided, returns all active and recent jobs. Use after sync_gsc_data or sync_all_properties to monitor progress.
Inputs: jobId.
Compare two arbitrary date ranges side-by-side across any dimension (query, page, device, country). Shows absolute and percentage changes. Useful for before/after analysis, seasonal comparisons, or measuring the impact of changes. Requires synced data — run setup first if needed.
Inputs: siteUrl (required), period1Start (required), period1End (required), period2Start (required), +4 more.
Drill into a single property. Shows an interactive dashboard with hero metrics, trend chart, top queries, top pages, country breakdown, ranking distribution, new/lost queries, and branded split. Use the siteUrl from get_overview results. Requires synced data — run setup first if needed.
Inputs: siteUrl (required), dateRange, comparisonMode, matchWeekdays, +1 more.
Run pre-built analytical queries against synced GSC data. Choose from 16 insight types: summary, top_queries, top_pages, growing_queries, declining_queries, growing_pages, declining_pages, opportunities (queries ranking 5-20 with high impressions — your quick wins), device_breakdown, country_breakdown, page_queries, query_pages, daily_trend, new_queries, lost_queries, branded_split. Requires synced data — run setup first if needed.
Inputs: siteUrl (required), insight (required), dateRange, pageFilter, +7 more.
See all your sites at a glance. Shows an interactive grid of every synced GSC property with clicks, impressions, CTR, position, percentage changes, and sparkline trends. Click any property card to open its full dashboard. If no data appears, run setup first to sync your properties.
Inputs: dateRange, sortBy, search.
List all Google Search Console properties accessible via the service account, with permission level and local sync status. Usually not needed — setup handles this automatically.
Inputs: no named parameters.
Apply data retention policy to a synced property database. Removes low-value rows (zero clicks, low impressions) from older data while preserving all recent data and actionable historical data. Runs VACUUM afterwards to reclaim disk space. This runs automatically after each sync, but you can also trigger it manually. Use preview_prune first to see what would be deleted.
Inputs: siteUrl (required), recentDays, targetMinImpressions, preview.
Run a read-only SQL query against a synced GSC property database. Supports any SELECT query. INSERT/UPDATE/DELETE/DROP/ALTER/CREATE are blocked. The table is "search_analytics" with columns: date, query, page, device, country, clicks, impressions, ctr, position. Requires synced data — run setup first if needed.
Inputs: siteUrl (required), sql (required), params.
First time? Start here. Connects to Google Search Console, syncs all your properties (fetches up to 3 months of data), and shows a visual overview of every site. Takes a few minutes depending on how many properties you have. After setup, use get_overview to see all sites at a glance, or get_dashboard to drill into one.
Inputs: no named parameters.
Sync search analytics data for ALL accessible GSC properties in one call. Syncs up to 2 properties in parallel for faster completion. Returns immediately with a job ID — use check_sync_status to monitor progress.
Inputs: startDate, endDate, dimensions, searchType.
Fetch Google Search Console search analytics data into a local SQLite database. Supports full pagination to capture ALL rows (no 1,000-row limit). Default date range is 3 months. Pass explicit startDate for longer ranges (up to 16 months). Returns immediately with a job ID — use check_sync_status to monitor progress.
Inputs: siteUrl (required), startDate, endDate, dimensions, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 12 tools
Most tools have distinct purposes, such as setup for initial configuration, sync_gsc_data for data fetching, and get_insights for analysis. However, there is some overlap between sync_gsc_data and sync_all_properties, as both handle data syncing but differ in scope (single vs. all properties), which could cause minor confusion for agents. Overall, descriptions help clarify differences, but the redundancy in syncing tools slightly reduces clarity.
Tool names consistently follow a verb_noun pattern, such as cancel_sync, check_sync_status, compare_periods, and get_dashboard. All tools use snake_case without deviations, making the naming predictable and easy to parse. This uniformity enhances agent usability and reduces cognitive load when selecting tools.
With 12 tools, the server is well-scoped for managing Google Search Console data, covering setup, syncing, monitoring, analysis, and maintenance. Each tool serves a specific function, such as data retrieval (sync_gsc_data), insights (get_insights), and cleanup (prune_database), ensuring comprehensive coverage without bloat. The count aligns well with the domain's complexity.
The tool set provides complete coverage for the Google Search Console domain, including initial setup (setup), data syncing (sync_gsc_data, sync_all_properties), monitoring (check_sync_status, cancel_sync), analysis (get_insights, compare_periods, query_gsc_data), visualization (get_overview, get_dashboard), and maintenance (prune_database, list_properties). There are no obvious gaps, supporting full CRUD-like workflows from data ingestion to insights.
Query your SEO data in plain language: rankings, audits, backlinks, competitors and AI visibility.
SEO audits, Search Console, GA4, keyword and backlink data for Claude, ChatGPT and Cursor.
AI SEO agent on your Google Search Console data: audits, quick wins, content, WordPress publishing.
Search Console, Google Analytics and keyword data for your AI agent.
