MCP server

Lists every site in SITES with the sources connected for it (GSC, Bing, Cloudflare AI crawlers, Web Analytics) and, for each dataset, the first and last date stored in D1. Start here.

No parameters.

Try “Which sites are connected, and how far back does each one’s data go?”

The general-purpose search analytics query. Groups GSC or Bing data by up to three dimensions and filters by query, page, country or device. It reads the history stored in D1, so ranges older than 16 months work once you have kept them. country and device cannot be combined with query/page dimensions, their filters or a brand split, because Search Console stores them separately; Bing has no country or device data and reports queries and pages separately.

Try “Top non-brand queries for /pricing over the last 90 days, by week.”

Compares a period with the equal-length period right before it, or with a custom comparison period, and returns totals for both, the change in clicks and impressions, and the queries or pages that gained and lost the most clicks, with impression and position deltas.

Try “What dropped the most this month compared to the same month last year?”

Finds queries with an average position between minPosition and maxPosition and enough impressions to matter, together with the page that ranks for each (GSC), ranked by the extra clicks available if they reached position 3 at a benchmark CTR. These are usually the cheapest traffic to win.

Finds queries for which two or more of your pages each get a meaningful share of the impressions, with each page’s impressions, clicks, position and share, so you can consolidate or differentiate them. Search Console only, because it needs query × page data.

Compares each query’s CTR with the median CTR of your own queries at the same rounded position (a benchmark curve when there are fewer than 8 samples) and returns the queries below expected × threshold, ranked by lost clicks. Only positions up to 20 count. Typical causes: a weak title or description, a rich result taking the click, or a mismatch with search intent.

Compares each page’s last 4 weeks of clicks with its best earlier 4-week window and returns the pages that fell by at least minDecline and are still trending down (not a single bad week), with peak and recent weekly clicks and the full weekly series.

Joins, for each page, AI crawler requests (Cloudflare), citations in AI answers (imported from Bing AI Performance CSV exports), visits referred by AI assistants (Web Analytics) and search clicks and impressions (GSC plus Bing). Returns totals, the pages, and the most-crawled pages that were never cited (once citation data exists). Notes say which step has no data and why.

Try “Which pages do AI crawlers hit but never get cited?”

Summarises requests from known AI crawlers and assistants (GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and others) recorded by Cloudflare, classified by operator and purpose (training, search, user). Includes HTTP status, so blocked or failing fetches stand out. Without dates, the window ends at the latest day of crawler data.

Try “Are any AI crawlers getting 4xx or 5xx responses from us?”

Calls the Search Console URL Inspection API in real time: verdict, coverage and indexing state, robots.txt and fetch state, last crawl time, the canonical chosen by Google and the one you declared, mobile usability and rich results verdicts, and a link to the full report. Google allows about 2,000 inspections per property per day.

Lists the sitemaps Search Console knows for the property, with last submitted and downloaded times, pending state, errors, warnings and submitted vs indexed counts. By default it reads the snapshot the sync takes once a day.

The only tool that writes to an external system. It is not registered unless ENABLE_WRITES is true, and it needs the service account to have Full (not Restricted) permission on the GSC property. It is annotated as a write so MCP clients ask before running it.

Reports the readiness state with one line per check: the Access checks, configuration errors, which secrets are present (never their values), live probes of the Cloudflare token, Search Console and Bing, and the most recent sync. It also returns each site’s connected sources, the date range stored per dataset and recent sync runs. Agents call it to verify a deployment. Like every tool it is served only once the deployment is ready; before that, /mcp returns a JSON-RPC error naming the state, and the dashboard’s status page (/api/status) shows the readiness checks.

Try “Run setup_status and tell me what is still missing.”