Google Search Console

@google-search-console show me search analytics for the last 28 days — which queries are driving the most impressions but have low CTR?

Based on your Search Console data for the past 28 days, here are queries with high impressions but CTR below 2%: 'react component library' (12,400 impressions, 1.3% CTR, avg position 8.2), 'typescript best practices 2024' (8,900 impressions, 1.1% CTR, avg position 11.5), and 'nextjs deployment guide' (7,200 impressions, 0.9% CTR, avg position 14.3). These queries suggest your pages are visible but titles or descriptions may not be compelling enough to earn clicks at their current ranking positions.

This example demonstrates the Search Analytics Query tool, which surfaces performance metrics by query, page, country, or device. Requires OAuth scope for read-only Search Console access. Data reflects your actual property's performance — results vary by site traffic and indexing status. Rate limits apply for high-frequency queries.

@google-search-console inspect the URL https://docs.example.com/api/v2/authentication to see if Google has indexed it yet

URL inspection complete for https://docs.example.com/api/v2/authentication: Status is 'URL is on Google' with last crawl on January 10, 2025. The page is mobile-friendly and has no indexing issues detected. Coverage state shows 'Valid' with no AMP errors. The canonical URL matches your submitted version. Note that the page was discovered via your sitemap submitted on January 8, and took approximately 48 hours to index after submission.

The Inspect URL tool provides real-time indexing status and crawl diagnostics for individual pages. Useful for debugging why a page isn't appearing in search results or validating fixes after a crawl error. Requires the URL to belong to a verified property in your Search Console account. Inspection quota is limited to a few hundred requests per day.

@google-search-console I just deployed a new sitemap at https://blog.example.com/sitemap-2025.xml — submit it so Google starts crawling those posts

Sitemap submitted successfully to Google Search Console. The sitemap at https://blog.example.com/sitemap-2025.xml has been queued for processing. Initial status shows 'Pending' with 47 URLs discovered. Google will begin crawling these URLs over the next few days based on your site's crawl budget and priority signals. You can monitor processing status and any errors (like unreachable URLs or invalid XML) by checking the Sitemaps report in your Search Console dashboard.

This example uses the Submit Sitemap tool to notify Google of new or updated content. Submission doesn't guarantee immediate indexing — crawl speed depends on your site's authority and crawl budget allocation. Side-effect: the sitemap is permanently added to your property unless manually removed. Ensure the sitemap URL is accessible and contains valid XML before submitting to avoid error states.

When this MCP wins for tracking organic performance

A 5-person content team runs a weekly standup to review which articles are gaining or losing traffic. The Search Analytics Query tool pulls clicks, impressions, CTR, and position for the last 7 days, filtered by page or query. One person shares the Switchy workspace with the MCP connected, everyone sees the same data without logging into GSC separately. This works well if your site has under 100k pages and you're reviewing aggregated metrics, not drilling into individual keyword clusters. The MCP doesn't replace a full SEO platform—it's for quick checks and shared visibility. If your team needs historical trend analysis beyond 16 months or advanced filtering, you'll still open the GSC web UI. For weekly triage and content prioritization calls, this MCP keeps the conversation in one place.

When this MCP wins for verifying new pages go live

A 3-person engineering team ships a new product landing page and wants to confirm Google indexed it within 24 hours. The Inspect URL tool checks indexing status and surfaces any crawl errors or mobile usability issues. The team shares the Switchy workspace during the deploy retrospective, runs the inspection, and sees the result without context-switching to GSC. This is the right call if you're verifying a handful of URLs per week and your team already uses OAuth for other Google services. If you're auditing hundreds of URLs at once or need programmatic monitoring, a dedicated crawler or CI integration is faster. The MCP shines for ad-hoc checks during standups or post-deploy reviews, not bulk validation. For small teams shipping iteratively, it closes the loop between deploy and search visibility in the same workspace.

When this MCP wins for onboarding new sites

A 2-person agency onboards a new client site and needs to submit the sitemap, verify it's processing, and document the setup in a shared workspace. The List Sites tool confirms the client granted GSC access, Submit Sitemap pushes the XML file, and Get Sitemap checks the submission status. The agency shares the Switchy workspace with the client for transparency, so both sides see the same steps without email screenshots. This works if you're onboarding 1-3 sites per month and the client is comfortable with OAuth delegation. If you're managing 20+ client sites or need white-label reporting, a dedicated SEO dashboard is cleaner. The MCP is ideal for small agencies or freelancers who want to keep onboarding tasks in a single shared context, not scattered across GSC logins and Slack threads.