Use SEOmatic in GitHub Copilot

Connect GitHub Copilot#

1. 1Create .mcp.json. At the root of your repo, add a seomatic server of type http with the URL https://app.seomatic.ai/api/mcp under mcpServers, as in the snippet below. Or run Chat: Open Customizations, then MCP Servers, Add Server, HTTP, and paste the URL.
2. 2Sign in. Start the server from the code lens in the file if VS Code has not started it already, confirm the trust prompt, and sign in or create a free SEOmatic account in the browser that opens.
3. 3Tick the tools. In the chat input, open Configure Tools and tick the SEOmatic tools.
4. 4Ask your first question. Try “Audit our live site with SEOmatic and list the issues our code causes.”

// .mcp.json at the repo root (VS Code and Copilot CLI both read it)
{
  "mcpServers": {
    "seomatic": {
      "type": "http",
      "url": "https://app.seomatic.ai/api/mcp"
    }
  }
}
// Older VS Code-only form: .vscode/mcp.json with "servers" instead of "mcpServers"

# GitHub Copilot CLI, in your shell:
copilot mcp add --transport http seomatic https://app.seomatic.ai/api/mcp
# or inside a copilot session: /mcp add
# or the same entry in ~/.copilot/mcp-config.json
# then sign in to SEOmatic when the browser opens (OAuth)

Workspace .mcp.json, Copilot CLI, the MCP Registry or Skills?

Pick the workspace .mcp.json. It lives in the repo next to the code it fixes, reviews like any other file, Copilot CLI reads it too, and it never shares anyone's data: each person signs in to their own SEOmatic account.

Try Asking#

• “Audit our live site with SEOmatic and group the issues by the component that causes them.”
• “Which of our pages lost the most clicks in the last 28 days?”
• “Check the preview deploy of this branch for SEO regressions against production.”
• “Find broken internal links on the live site and fix them in the code.”
• “Why are these URLs not indexed by Google?”
• “We relaunch next week. Which pages earn our clicks, and do the new routes keep them?”

What It Costs#

Connecting is free. Reading your own data never uses credits: Search Console performance and insights, index status, rankings, site audits, AI citations, traffic and your tasks. Only live market lookups (keyword metrics, search results, backlinks), AI visibility scans and the fixes you approve use AI credits; every tool is labelled free or billed. On the Free plan, market lookups count against 5 free questions a month. The workspace Owner sees every credit spent, by feature, in Settings > Usage. GitHub Copilot itself is billed by its maker, not by SEOmatic: nothing on our side counts tokens.

Nothing Changes on Your Site Without Your Approval#

Copilot's code edits go through your review and your pull requests. Anything SEOmatic would change on a live site through a connected CMS is staged, never pushed. A staged change is a proposal: it says what will change and why, and 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.

GitHub Copilot says SEOmatic is connected but answers without my data.

Start a new chat and check that SEOmatic is enabled for that conversation in the tools menu. This is the step most people miss.

The SEOmatic page says "This connection request expired".

Start the connection again from GitHub Copilot, or paste the setup prompt again.

The Authorize page shows the wrong email or no workspace.

Click Switch account on that page and sign in with the SEOmatic account that owns the site.

Why does GitHub Copilot say it cannot change my site?

Fixes need a live paid plan or trial. On the Free plan, or when billing is paused or failed, your assistant can read and answer only.

How do I disconnect?

Open Settings > AI Agents, scroll to API Keys and delete the row named OAuth: GitHub Copilot. See disconnect an assistant.