GSC Wizard (Preview)

Search Console performance, indexing and IndexNow for your sites.

This connector is available in the following products and regions:

GSC Wizard

Overview

GSC Wizard connects agents to your own Google Search Console data and to Bing's instant indexing pipeline. Ask about traffic trends, top queries and pages, keyword cannibalisation, decaying content, Core Web Vitals and index coverage in natural language, then act on the answer: submit changed URLs straight to IndexNow, the open protocol Bing, Yandex and Seznam use to pick up new and updated pages without waiting for a crawl.

The connector exposes a curated set of 24 tools, chosen from the wider GSC Wizard tool catalogue for the ones that fit conversational use. Twenty-two are read-only. Only two write: submit_indexnow_urls and update_indexnow_settings, both described in the IndexNow section below.

Publisher

GSC Wizard

Service / API

GSC Wizard MCP Server

• Host: mcp.gscwizard.com
• Base path: /
• Scheme: https
• Transport: MCP Streamable HTTP

Prerequisites

Before you can use this connector:

1. Create a GSC Wizard account at https://www.gscwizard.com and start a subscription. The sign-in step rejects accounts without an active subscription.
2. Connect at least one Google Search Console property. Sign in with the Google account that owns or has access to the property. Without a connected property, every tool returns an empty or not-found result.
3. For the IndexNow tools only: configure an IndexNow key for the property and publish the key file on your site. See IndexNow setup below. The read-only tools work without this step.

Authentication

This connector uses OAuth 2.0 with PKCE. You sign in with your GSC Wizard account and grant the connector access to the Search Console properties already connected to it. The connector never sees your Google credentials: GSC Wizard holds the Google authorisation and the connector is scoped to GSC Wizard itself.

Two scopes are requested:

• mcp:read for all Search Console, indexing and account data.
• mcp:write for the IndexNow tools.

Available tools

Getting oriented

• list_sites: List Search Console properties connected to the account. Start here; most other tools take a siteUrl from this list.
• get_account_info: Profile, connected Google accounts, and subscription state.
• get_site_summary: Last-N-days totals plus a prior-period comparison.

Search performance

• query_search_analytics: Ad-hoc Search Analytics query against a property. The most flexible read tool: pick your own dimensions, date range and filters.
• query_top_queries: Top search queries by clicks for a date range.
• query_top_pages: Top landing pages by clicks for a date range.
• get_query_performance: Daily metrics for a single query, optionally on one URL.
• get_page_performance: Daily clicks, impressions, CTR and position for a single URL.
• get_ranking_changes: New, lost, improved and declined queries (or pages) between two periods.

Opportunities and diagnostics

• score_opportunities: Impression-weighted opportunity score favouring high-impression queries near the top of page two.
• analyze_cannibalization: Queries where two or more pages compete, scored by impression-split entropy.
• find_decaying_content: Queries or pages losing clicks against a baseline period, bucketed severe, moderate or mild.
• audit_onpage_seo: Crawls pages and runs a technical on-page audit per URL (indexability, titles, canonical, links, structured data, issues).
• get_core_web_vitals: Chrome UX Report field data: weekly Core Web Vitals (LCP, INP, CLS) plus FCP and TTFB, with ratings and regressions.

Indexing and crawling

• inspect_url: Run the URL Inspection API for one URL and persist the result to history.
• list_url_inspections: Persisted URL inspection history, paginated.
• get_inspection_quota: Remaining URL inspections available today for a property. Worth checking before a run of inspections, since Google's daily quota is small.
• get_indexing_tracker: Indexing Tracker configuration and a status summary: indexed, not indexed, pending, errors and warnings.
• list_sitemaps: Sitemaps submitted to Search Console for a property.
• get_sitemap_performance: Fetches a sitemap, extracts its URLs, and joins each with Search Console clicks, impressions and position.

IndexNow: instant indexing for Bing

IndexNow lets you tell participating search engines that a URL has changed, instead of waiting for the next crawl. Bing is its primary consumer; Yandex and Seznam also participate.

• get_indexnow_settings: Reports whether an IndexNow key is configured for a property (masked to its last four characters, never returned in full) and whether the key file is actually reachable on your site.
• update_indexnow_settings: Set, rotate or clear the IndexNow key for a property.
• submit_indexnow_urls: Submit up to 100 URLs to IndexNow for the property.
• list_indexnow_submissions: IndexNow submission history for a property.

IndexNow setup

IndexNow requires proof that you control the site, in the form of a key file served from the site itself. Both steps are required:

1. Set a key for the property with update_indexnow_settings, or in the GSC Wizard web app under IndexNow settings.
2. Publish that key as a plain text file at https://<your-domain>/<key>.txt, containing the key and nothing else.

get_indexnow_settings reports the state of both steps, so an agent can tell you which one is missing and give you the exact URL the file has to live at. Submissions made before the key file is reachable are rejected up front rather than accepted and silently dropped.

Getting started

1. Call list_sites to see which Search Console properties are available and get their siteUrl values.
2. Call get_site_summary for a quick read on how a property is doing.
3. Call query_search_analytics, query_top_queries or query_top_pages for detail, or score_opportunities and analyze_cannibalization for ranked next actions.
4. Call inspect_url or get_indexing_tracker to check whether Google has indexed the pages you care about.
5. After publishing or updating pages, call submit_indexnow_urls so Bing picks them up without waiting for a crawl.

Common use cases

• Weekly search reporting. "How did organic search do last week compared to the week before, and which pages moved most?"
• Finding quick wins. "Which queries are sitting just off page one with high impressions?"
• Diagnosing a drop. "Traffic to this page fell. Is it a ranking change, an indexing problem, or a Core Web Vitals regression?"
• Fixing self-competition. "Which of my pages are competing for the same queries?"
• Publishing workflow. "I just updated these ten pages. Audit them, then submit them to IndexNow so Bing recrawls them."
• Index coverage checks. "Are the URLs in my sitemap actually indexed, and which are not?"

Known limitations

• Read-only, except two IndexNow tools. Twenty-two of the 24 tools only read. Nothing changes your Search Console configuration or your site. The two that write are update_indexnow_settings, which stores an IndexNow key for your property, and submit_indexnow_urls, which transmits URLs to the public IndexNow network. The other two IndexNow tools, get_indexnow_settings and list_indexnow_submissions, only read.
• IndexNow 202 does not mean indexed. IndexNow returns HTTP 202 for "accepted, key validation pending". Engines then fetch your key file and discard the batch if it is not reachable. Treat 202 as submitted, never as indexed.
• IndexNow submission caps. Up to 100 URLs per call. Submissions also count against the per-connection tool-call limits above.
• URL Inspection quota. Google caps URL inspections per property per day. Check get_inspection_quota before bulk work.
• Search Console data lag. Search Console data is typically two to three days behind, and the most recent day or two can still change. Do not read the final day of a range as final.
• Oversized responses are refused, not truncated. A result over 100,000 characters comes back as a short notice saying how large it was and what it contained, rather than a partial answer that could be misread as complete. Narrow the date range, lower the row limit, or ask for fewer dimensions.
• Some properties return nothing. A property with little traffic, or one connected very recently, legitimately returns empty results.
• Property access follows GSC Wizard. You can only reach properties connected to, or shared with, your GSC Wizard account.

Throttling limits

Not every tool costs one call against those windows. audit_onpage_seo crawls pages and costs 5, so the practical ceiling is about 12 audits per minute rather than 60. Everything else in this connector costs 1.

Support

• Website: https://www.gscwizard.com
• Documentation: https://mcp.gscwizard.com
• Privacy policy: https://www.gscwizard.com/privacy.html
• Support: support@gscwizard.com

Actions

GSC Wizard