Connect Google Search Console to Cursor

Windsor.ai gives Cursor access to 50+ Google Search Console fields. These are some of the groups; the Google Search Console field reference lists all of them:

• Performance: Clicks, Impressions, CTR, Position.
• Queries and pages: Search Query, Page, Page Path, Words in Query, Branded vs Non-Branded.
• Segments: Device, Country Name, Search type, Search Appearance.
• Sitemaps: Path, Submitted, Errors, Warnings, Last downloaded.
• Time: Date.

Cursor works best when you ask it to build something with a clear output. Each of these names the fields to use and the file or canvas you want back:

• Pull Search Query, Page, Clicks, Impressions, CTR, and Position for the last 90 days. List queries with at least 300 Impressions, an average Position between 8 and 20, and a CTR below the site average for that position band. Group them by Page, and for each page write the title and heading changes I should test first.

• Pull Search Query, Page, Clicks, and Impressions for the last 90 days. Find queries where two or more Page values received Impressions, show how Clicks split between them, and write a cannibalization report that names the page I should keep as the main one and what to do with the others.

• Build a canvas of Clicks, Impressions, and CTR split by Branded vs Non-Branded for the last 6 months by month. Add a short read on whether growth is coming from discovery or from brand demand, and mark any month where the split changed by more than 10 points.

• Pull Search Query, Device, Clicks, CTR, and Position for the last 60 days. Write a script that finds queries whose Position is similar on desktop and mobile but whose CTR is much lower on mobile, and save mobile_ctr_gap.csv with the pages involved.

• Pull Page Path, Clicks, and Impressions for the last 28 days and for the 28 days before. Flag pages that lost more than 30% of Clicks, then show the Search Query values that drove most of the loss so I can see whether it is a ranking drop or lower demand.

• Pull Path, Submitted, Errors, Warnings, and Last downloaded for all sitemaps. Write a short check that lists sitemaps with errors or warnings or a stale Last downloaded date, and what to inspect first for each.

Yes. Cursor can render a dashboard, analysis, or report as a canvas next to the chat, and it saves the canvas so you can reopen and rerun it later with fresh data. On paid Cursor plans you can publish a canvas to a read-only share link for teammates. See the Cursor canvas documentation for the current plan requirements.

No. With this setup Cursor reads your Google Search Console data through Windsor MCP. It can write scripts, files, and reports in your project, but it does not modify, update, or affect your connected accounts.

Yes. Windsor.ai supports 350+ data sources, so you can connect Google Search Console alongside tools such as GA4, Google Ads, or HubSpot and ask Cursor to work with them together. For example, ask Cursor to join Search Console Page Path with GA4 Landing page, Key events, and Total revenue, then write a report of pages that earn many Clicks but produce no key events.

Open Settings in Cursor Desktop, go to Tools & Integrations → New MCP Server, and add Windsor to mcp.json:

{
  "mcpServers": {
    "windsor": {
      "url": "https://mcp.windsor.ai/"
    }
  }
}

Save the file, click Authenticate next to Windsor in your MCP list, and sign in to Windsor.ai in the browser.

No. The connection takes no code: connect Google Search Console in Windsor.ai, add Windsor to Cursor’s MCP settings, and sign in. After that you describe what you want in plain language, and Cursor writes and runs the code. You can read and edit everything it produces.

The free forever plan covers 1 data source, so connecting Google Search Console on its own costs nothing and needs no credit card. Combining Google Search Console with other sources, such as GA4 or Google Ads, needs a paid plan: $19/month for 3 sources or $99/month for 7. Cursor is billed separately by Cursor. See the pricing page.

Yes, we have helpful resources to help you get started. You can explore our official documentation for Google Search Console to Cursor integration with Windsor.ai:

• Google Search Console Field Reference
• Cursor Integration Documentation
• Windsor.ai connectors for Cursor