Query Google Search Console performance data. Supports all dimensions (query, page, country, device, searchAppearance, date), all search types (web, discover, googleNews, news, image, video), regex filters, hourly data, and up to 25K rows per request. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Compare search performance between two date ranges. Returns delta calculations for clicks, impressions, CTR, and position. Useful for tracking impact of SEO changes, algorithm updates, or seasonal trends. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Automatically identify SEO opportunities: quick wins (position 5-20 with high impressions but low CTR), declining content (pages losing traffic), and emerging queries (new or rapidly growing). Compares recent 7-day window to 28 days prior. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Inspect a single URL in Google Search Console. Returns index status, mobile usability, rich results, AMP status, canonical information, and last crawl time. Daily quota: 2,000 inspections. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Inspect multiple URLs at once. Returns a summary of index status across all URLs with issues highlighted. Rate-limited to respect the 2,000/day quota. Max 100 URLs per call. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

List all sitemaps submitted for a site in Search Console. Shows status, submission date, error/warning counts, and content type details (URLs submitted vs indexed). IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Submit a new sitemap to Google Search Console. The sitemap URL must be accessible and return valid XML.

Remove a sitemap from Search Console tracking. This does not prevent Google from crawling URLs discovered from this sitemap.

List all Google Search Console properties accessible to the authenticated account. Shows property type (domain vs URL prefix) and permission level.

Submit a URL update or deletion notification to Google via the Indexing API. Note: Officially supported only for pages with JobPosting or BroadcastEvent structured data. Daily quota: 200 notifications.

Check the status of Indexing API notifications for a URL. Shows the most recent update and removal notifications.

Self-check a claim about search performance data before presenting it. Re-queries the Google Search Console API to verify that a specific metric matches the expected value. Use this tool to confirm numbers before stating them in your analysis, especially for claims from earlier in the conversation. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Find pages that lost traffic and diagnose why. Categorizes each drop as: ranking loss (position got worse), CTR collapse (position held but CTR dropped — possible SERP feature changes), or demand decline (search impressions dropped — seasonality or trend shift). Compares recent 7-day window to 28 days prior. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Detect keyword cannibalization — queries where multiple pages from the same site compete against each other, splitting ranking potential. Shows which pages rank for the same keywords so you can consolidate or differentiate. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Detect content decay — pages with 3 or more consecutive months of traffic decline. One bad month is noise; sustained decline is a pattern that needs attention. Surfaces pages that should be refreshed before they disappear from search results. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Compare your actual click-through rates against industry-average benchmarks by position. Identifies pages or queries with CTR below expected levels — candidates for title tag and meta description optimization. Benchmarks are aggregated from multiple studies and should be used as directional guidance. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.

Analyze performance of all pages under a URL path prefix (e.g., "/blog/", "/docs/seo/", "/products/"). Shows aggregate and per-page metrics plus the top queries driving traffic to the cluster. Useful for understanding how entire content sections perform. IMPORTANT: Base your analysis only on the data returned by this tool. Report exact numbers from the response. Do not speculate about causes the data does not support. If the data is insufficient to answer, say so rather than guessing.