SEO From Cursor, Backed by Your Real Search Data

Cursor's agent already edits your whole codebase. Install SEOmatic and it can also see what Google sees: your Search Console clicks and queries, a live audit of your site and Google's index status. So the SEO fixes it writes land on the pages where traffic is actually waiting.

One mcp.json entry, OAuth sign-in, no key
Search Console and live audits inside the Agent panel
Findings traced to the code that causes them

Connect Cursor free

Cursor

About SEOmatic for Cursor

SEOmatic is a hosted MCP server that Cursor connects to by URL in mcp.json, or from Customize > MCPs in the sidebar. Cursor's agent calls SEOmatic's tools while it works, so SEO checks sit next to the code instead of in another tab.

Last Updated

November 2026

Requirements

Cursor and a free SEOmatic account, which you can create during sign-in. Use OAuth, not an API key: because SEOmatic advertises OAuth, Cursor starts the sign-in before it sends any configured Authorization header.

Pricing

Free to connect. Search Console, audits and page checks have no limit; market data uses 5 free questions a month (plus a one-time 10 when you connect Search Console). Paid plans add agents that stage fixes for your approval. See pricing.

Full Docs

Endpoint, auth, every tool and what it costs: SEOmatic MCP server docs.

Cursor SEO With Your Own Search Console Data

What the SEOmatic MCP Server Does in Cursor

Metadata Fixes Across Routes

Find duplicated or missing titles and descriptions on the live site and fix the metadata code that generates them.

Pages Losing the Click

Search Console CTR outliers tell the agent which pages to work on first, and which queries they should match.

Crawl and Index Problems

Noindex leaks, stray canonicals, redirects and broken internal links, found on the live site and traced to the code.

Content Gaps From Real Queries

Queries your site gets impressions for without a page that answers them, ready to become new routes or sections.

Before and After Checks

Analyze a publicly reachable preview URL and production side by side to confirm a change did what you meant.

SEO Skills the Agent Follows

npx skills add brings 21 skills, like striking distance keywords and the SEO audit, so “find quick wins” runs the same tested flow every time.

Cursor is where front-end and full-stack developers live. SEOmatic makes it the place to settle SEO questions too, with data instead of a checklist, while the relevant files are already open.

Example: Ask Cursor About Your Site

An example on the Acme Plumbing demo site. You ask Cursor:

“Which pages get seen on Google but skipped, and is our metadata code the reason?”

Cursor calls SEOmatic:

gsc_insights: CTR outliers, Sep 12 to Oct 9 (28 days)
site_pages: crawl metadata for the 3 flagged URLs

Cursor answers:

Three pages earn far fewer clicks than their position should bring (Sep 12 to Oct 9, 28 days):

/water-heater-repair: position 8.9, 3,240 impressions, 1.2% CTR. The live title is the generic fallback from app/layout.tsx, because the page exports no metadata.
/drain-cleaning-cost: position 6.1, 1,870 impressions, 2.4% CTR. The description is cut at 70 characters by the truncate() helper in lib/seo.ts.
/emergency-plumber: position 7.3, 1,410 impressions, 1.9% CTR. Title and H1 both say "Services", the query people type is "emergency plumber near me".

I can add page-level metadata to all three and remove the truncation. You review the diff before anything ships.

Also try:

“Audit the live site and fix what our code causes”
“Which URLs has Google not indexed, and why?”
“Check the preview deploy against production”
“Which queries have no page that answers them?”

Cursor SEO Prompts That Use Your Real Data

Paste into Cursor's Agent chat once SEOmatic is installed:

“Audit our live site with SEOmatic and fix the issues that come from our code.”
“Which of our pages get impressions but few clicks? Update their titles in the codebase.”
“Find every page with a canonical pointing somewhere else and explain why.”
“What queries do we get impressions for without a matching page?”
“Compare the SEO of our preview deploy with production.”
“Run the striking-distance skill and tell me which three pages to work on this sprint.”

How It Works, Step by Step

You add one mcp.json entry and approve the browser sign-in once.
You ask Cursor's agent an SEO question while working in your repo.
The agent calls SEOmatic for audits, Search Console data or index status, and reads the results with the exact date range behind every number.
It edits the files responsible, and you review the diff as usual.
After you deploy, it re-checks the live page to confirm the fix landed.

If your site runs on a CMS that SEOmatic connects to instead of a repo, paid plans let SEOmatic's agents stage the same fixes there for your approval.

How to Connect SEOmatic to Cursor

Add one entry to mcp.json (snippet below): ~/.cursor/mcp.json for every project, or .cursor/mcp.json in one repo. Or add the same URL from Customize > MCPs in the sidebar.

Add the mcp.json entry. Add a seomatic server with only the URL https://app.seomatic.ai/api/mcp to ~/.cursor/mcp.json or .cursor/mcp.json, as in the snippet below, or open Customize in the sidebar and add it under MCPs. If you edited the file and seomatic does not appear, save it and restart Cursor.
Approve the browser sign-in. Cursor starts the OAuth flow in your browser. Sign in or create a free SEOmatic account, approve access and pick your site. If the prompt does not open, go to Customize > MCPs, find seomatic and start the sign-in from its entry. In the Cursor CLI, run agent mcp login seomatic, then agent mcp list-tools seomatic to see the tools.
Connect Search Console. If your workspace has no Search Console yet, SEOmatic hands you a one-click connect link. There is no Google Cloud project to set up.
Ask the agent. Try “Audit our live site with SEOmatic and list the issues our code causes.” Cursor asks before each SEOmatic tool by default. To skip that, allow the tools in Cursor Settings > Agents > Approvals & Execution, or add "seomatic:*" to mcpAllowlist in ~/.cursor/permissions.json.

Cursor setup

// ~/.cursor/mcp.json (or .cursor/mcp.json in one repo),
// or Customize > MCPs in the sidebar
{
  "mcpServers": {
    "seomatic": { "url": "https://app.seomatic.ai/api/mcp" }
  }
}
# one click: cursor://anysphere.cursor-deeplink/mcp/install?name=seomatic&config=eyJ1cmwiOiJodHRwczovL2FwcC5zZW9tYXRpYy5haS9hcGkvbWNwIn0=
# Cursor CLI: agent mcp login seomatic
#             agent mcp list-tools seomatic

Do not paste an API key into Cursor's config: because SEOmatic advertises OAuth, Cursor starts the sign-in before it sends any configured Authorization header, so a key there is not used. Approve the browser prompt instead. If seomatic is connected but the agent never calls it, turn seomatic off and on in Customize > MCPs and start a new Agent chat. Errors show in the Output panel under MCP Logs. Cloud Agents do not read your mcp.json: add SEOmatic from the MCP menu at cursor.com/agents, or a team admin adds it under Dashboard > Plugins & MCPs.

mcp.json, One-Click Link or Skills Only?

Route	Best for	How
mcp.json	Everyone, today. One global config, or committed to the repo for the team	Add `"seomatic": { "url": "https://app.seomatic.ai/api/mcp" }` under `mcpServers` in `~/.cursor/mcp.json` or `.cursor/mcp.json`, then approve the sign-in Cursor opens. In the Cursor CLI, `agent mcp login seomatic` runs the same sign-in.
One-click install link	No file editing. Cursor asks you to confirm the server	Open `cursor://anysphere.cursor-deeplink/mcp/install?name=seomatic&config=eyJ1cmwiOiJodHRwczovL2FwcC5zZW9tYXRpYy5haS9hcGkvbWNwIn0=` in your browser. Cursor prompts you to install the server, then opens the sign-in.
Skills only	Repos where other agents read the same skills folder, or terminal-driven work	`npx skills add Minh42/seomatic-mcp --full-depth -a cursor`. Installs SEOmatic's 21 SEO skills: the CLI skill signs in once with `npx -y seomatic login`, the other 20 use the MCP server above. All of them: SEO skills.

Start with mcp.json. It works in every Cursor today and takes one entry. Want the 21 SEO skills too (an SEO audit, striking distance keywords, traffic drops, AI visibility, client reports and more)? Add them with npx skills add Minh42/seomatic-mcp --full-depth -a cursor; Cursor loads skills from .agents/skills and ~/.cursor/skills on its own. Cloud Agents do not read your mcp.json: add SEOmatic from the MCP menu at cursor.com/agents, or a team admin adds it under Dashboard > Plugins & MCPs.

Fix SEO on Your CMS From Cursor

Cursor reads Google Search Console through SEOmatic, and the fixes you approve go live in your CMS. Pick your platform for the exact steps:

Cursor or Grok Bot: Which One Is This?

This page is about Cursor, the AI code editor you run on your own machine and prompt while you work.

Grok Bot is the always-on agent from xAI. It runs routines on a cloud computer, with no editor open: Grok Bot SEO.
Claude Code and Codex are terminal-first coding agents. If that is where you work, see Claude Code SEO or Codex SEO.

All of them connect to the same SEOmatic server, so your workspace, your free questions and your approvals carry across.

What Is Free and What Is Paid

Connecting is free, and so is the SEOmatic account behind it: no card. Free covers the diagnosis with no limit: Search Console reports and insights, site audits of up to 30 pages, live page analysis, and your AI visibility results.

Live market data, like keyword volumes, backlink profiles and competitor domains, uses free questions: 5 a month, plus a one-time 10 bonus questions when you connect Google Search Console. One question covers up to 5 lookups.

Paid plans remove the question limit and add the treatment: agents stage fixes on your site (titles, descriptions, content updates, technical fixes, internal links) and run campaigns and fresh AI visibility scans. Every paid plan starts with a 14-Day Trial for $1, credited to your first payment. See pricing.

If you fix things in code yourself, the free lane covers the diagnosis. Paid plans are for when you also want SEOmatic's agents to make changes in a connected CMS.

Nothing Changes on Your Site Without Your Approval

Code changes in Cursor go through your normal review. Changes to a live site through a CMS connected to SEOmatic are staged, never pushed. A staged change is a proposal: it says what will change and why, and in Approval mode nothing touches your site until you approve it. The assistant records your decision, and it is told never to approve anything on its own judgment. Approved fixes start within seconds, the page's previous state is stored, and any applied change can be rolled back. Changes that could take a page out of Google, like a noindex, need an extra explicit confirmation.

Keep Exploring

Other coding agents: Claude Code, Codex, GitHub Copilot and Cline. Always-on instead of in the editor? See Grok Bot. Explore the site audit, technical SEO fixes and the Google Search Console integration. Terminal first? The SEOmatic CLI runs the same tools. All assistants: AI assistants. Full reference: MCP docs.

Using another agent? See Claude Code, Codex, Grok Bot, or every AI agent.

Frequently Asked Questions

How do I connect SEOmatic to Cursor?

Add a seomatic entry with the URL https://app.seomatic.ai/api/mcp under mcpServers in ~/.cursor/mcp.json (or .cursor/mcp.json in one repo), or add the same URL from Customize > MCPs in the sidebar. Then approve the SEOmatic sign-in in your browser and pick your site.

Can Cursor do SEO?

Cursor can edit the code that controls your SEO, but on its own it cannot see your rankings or how Google reads your pages. With SEOmatic installed, it audits your live site, reads your Search Console data and fixes the code behind each issue.

Is there a one-click install for Cursor?

Yes. Open cursor://anysphere.cursor-deeplink/mcp/install?name=seomatic&config=eyJ1cmwiOiJodHRwczovL2FwcC5zZW9tYXRpYy5haS9hcGkvbWNwIn0= in your browser. Cursor prompts you to install the seomatic server, then opens the sign-in. The config is the same one-line mcp.json entry, base64-encoded.

Why doesn't my API key work in Cursor?

SEOmatic advertises OAuth, and Cursor starts that sign-in before it sends any configured Authorization header, so a key in the config is not used. Remove it and approve the browser prompt instead. If the prompt does not open, find seomatic in Customize > MCPs and start the sign-in from its entry, or run agent mcp login seomatic in the Cursor CLI.

Is SEOmatic for Cursor free?

Yes. The account is free with no card. Search Console reports, site audits and page checks are free with no limit. Live market data (keyword volumes, competitors, backlinks) uses free questions: 5 a month, plus a one-time 10 when you connect Search Console. Paid plans remove the limit and add agents that stage changes in your CMS.

Where do the numbers come from?

From your own Google Search Console property, read through SEOmatic. Every answer names the exact date range and number of days behind it, so you can check any figure against Search Console yourself.

Do I need a Google Cloud project or service account?

No. You connect Search Console to SEOmatic with one Google sign-in, which takes about a minute. There are no credentials files or API keys to manage in your repo.

Can it change my site without asking?

No. By default every change SEOmatic proposes waits for your approval before it touches your site, and your assistant is told never to approve on its own. Approved changes are stored with the page's previous state, so any edit to an existing page can be rolled back. If you later want low-risk fixes to go ahead on their own, you can turn that on in your autonomy settings; changes to your URLs or indexing, and new content, still wait for you.

Does it only work for sites built in code?

No. If your site lives in a repo, Cursor fixes the code and you review the diff. If it runs on a CMS such as WordPress, Webflow or Shopify, paid plans let SEOmatic stage the fix there, and it goes live in your CMS once you approve it.

Will SEOmatic push Cursor over its tool limit?

It can if you run many MCP servers at once. SEOmatic lists its SEO tools by default: grouped tools that each cover several actions, such as rank tracking or your Business Profile, plus single-purpose tools like the site audit and article writer. To load fewer, use https://app.seomatic.ai/api/mcp?tools=essentials as the server URL, or disable the servers you do not need from Customize > MCPs.

Cursor shows SEOmatic as connected but never uses it. What now?

Cursor has a known bug where a connected server's tools do not reach the agent. Open Customize > MCPs, turn seomatic off and on again, then start a new Agent chat and name SEOmatic in your request. Check the Output panel (MCP Logs) for errors. In the Cursor CLI, start with agent --approve-mcps and type /mcp to check that seomatic is ready with its tools.

Is Cursor the same as Grok Bot?

No. Cursor is the code editor on your machine. Grok Bot is xAI's always-on agent that runs routines in the cloud. Both connect to the same SEOmatic server and reach the same SEOmatic workspace.

SEOmatic in other AI agents

Same server, same tools, same approval rules. Pick the agent that fits the job.

Claude Code

One command connects your Search Console to the terminal, so Claude Code fixes SEO in the code.

Codex

Two commands give Codex your Search Console data, so it fixes SEO where the bug lives: in your code.

Grok Build

Two commands give Grok Build your real Search Console data, so it can find what costs you clicks and fix it in the code.

Kimi K3

Kimi K3 in Kimi Code CLI, reading your real Search Console and fixing what it finds in your repo.

DeepSeek

DeepSeek, working from your real Search Console data through the SEOmatic plugin for DeepSeek Harness.

GitHub Copilot

Add SEOmatic to .mcp.json and Copilot works from your real SEO data.

View All Integrations