detect_quick_wins
Automatically detect SEO quick wins and optimization opportunities
LABSCO SUMMARY
Search Console questions get answered at 25,000 rows instead of at export size.
enhanced_search_analytics is the reason to install this over using the interface: a single call wide enough to ask cross-sectional questions rather than page-by-page ones, with regex filters doing the segmenting. detect_quick_wins encodes the usual heuristic — high impressions, low CTR, positions inside a band you choose — and attaches conversionRate and estimatedClickValue so the result is ordered by value. Everything is bounded by what the service account has been granted in Search Console, which is a permissions question to settle before the first call rather than after.
What it is
A server over the Google Search Console API — search analytics, URL inspection and sitemap management — for the properties one service account can see.
What you get
- search_analytics with the API's own controls: dimensions, date range, search type and aggregation, plus query, page, country and device filters
- enhanced_search_analytics for the larger pull — up to 25,000 rows, regex filtering, and quick-wins detection switched on inline
- detect_quick_wins as a standalone scan with thresholds you set: an impressions floor, a CTR ceiling and a position band
- Value attached to the scan through conversionRate and estimatedClickValue, so the output ranks by what the opportunity is worth rather than by position alone
- URL-level index status from index_inspect, including whether a page can be indexed and in which language context
- Sitemaps listed, fetched by feedpath and submitted for a property
Requirements
GOOGLE_APPLICATION_CREDENTIALS pointing at a Google service account credentials file, and that service account granted access to the Search Console properties you intend to read — list_sites returns what it can reach. submit_sitemap is the only tool that changes anything on Google's side; the rest read.
Setup effort
One command plus credentials — npm install mcp-server-gsc, then supply credentials
USE CASES
01
Finding pages one position away from traffic
Run the quick-wins scan with your own impression floor, CTR ceiling and position band, then pull the wider query set with regex filters to see which terms are behind each page.
02
Checking whether Google can index a URL
Confirm the property is one the account can reach, then inspect the URL itself for its index status and whether it could be indexed at all.
03
Comparing query performance across devices or countries
Pull the same date range twice with different dimensions and filters, and let the aggregation type decide whether you are counting by page or by property.
04
Getting a new sitemap picked up
See which sitemaps the property already knows about, read the one being replaced, and submit the new feed path.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
enhanced_search_analytics
Enhanced search analytics with up to 25,000 rows, regex filters, and quick wins detection
get_sitemap
Get a sitemap for a site in Google Search Console
index_inspect
Inspect a URL to see if it is indexed or can be indexed
list_sitemaps
List sitemaps for a site in Google Search Console
list_sites
List all sites in Google Search Console
search_analytics
Get search performance data from Google Search Console
submit_sitemap
Submit a sitemap for a site in Google Search Console
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected. Only search_analytics has detailed documentation; the other seven have no parameter docs. submit_sitemap writes to Google, so the service account needs administrator rather than read access.
Requires
- npx on PATH
- Node.js 18 or later
- GOOGLE_APPLICATION_CREDENTIALS in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install mcp-server-gscMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"gsc": {
"command": "npx",
"args": [
"-y",
"mcp-server-gsc"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "<YOUR_GOOGLE_APPLICATION_CREDENTIALS>"
}
}
}
}
