Use SEOmatic in Grok Build
Updated
Before you start
Grok Build (install with curl -fsSL https://x.ai/cli/install.sh | bash) and a free SEOmatic account. For CI, create an API key in Settings, AI Agents, API Keys.
Connect Grok Build#
- Install Grok Build if needed. Run curl -fsSL https://x.ai/cli/install.sh | bash and sign in to xAI.
- Add the SEOmatic marketplace. Run: grok plugin marketplace add Minh42/seomatic-mcp
- Install the plugin. Run: grok plugin install seomatic --trust. You can also open /marketplace inside Grok Build and install seomatic from there.
- Sign in. Start grok in your project and ask a question about your site. Sign in or create a free SEOmatic account in the browser window that opens, then pick your site. If no window opens, open /mcps and press i on seomatic.
- Ask your first question. Try “How did my site do on Google in the last 28 days?” and check the answer cites your real Search Console numbers.
Grok Build setup
# Plugin: the SEOmatic skills plus the hosted server
grok plugin marketplace add Minh42/seomatic-mcp
grok plugin install seomatic --trust
# start grok and ask a question; sign in when the browser opens
# Or the server only:
grok mcp add --transport http seomatic https://app.seomatic.ai/api/mcp
# Headless, SSH or CI: use an API key from the environment
grok mcp add --transport http seomatic https://app.seomatic.ai/api/mcp \
--header "Authorization: Bearer ${SEOMATIC_API_KEY}"Note
No browser over SSH or in CI? Create a key in SEOmatic under Settings, AI Agents, API Keys, export it as SEOMATIC_API_KEY, and add the server with the Bearer header form shown above.
Plugin, Grok Mcp Add or config.toml?
| Route | Best for | How |
|---|---|---|
| SEOmatic plugin | Most people. Adds the SEO skills and the server together | grok plugin marketplace add Minh42/seomatic-mcp, then grok plugin install seomatic --trust. Or open /marketplace in the TUI. |
| grok mcp add | Only the server, or machines without a browser | grok mcp add --transport http seomatic https://app.seomatic.ai/api/mcp. Without a browser, add --header "Authorization: Bearer ${SEOMATIC_API_KEY}". |
| config.toml | Teams that ship MCP config with the repo | In ~/.grok/config.toml or the project's .grok/config.toml, add [mcp_servers.seomatic] with url = "https://app.seomatic.ai/api/mcp". |
Pick the plugin. It connects the same SEOmatic server as the other two and adds SEOmatic's skills, so Grok Build already knows the audit, striking-distance and weekly-brief workflows.
Try Asking#
- “Which of my pages get seen on Google but rarely clicked? Fix their titles in the repo.”
- “Inspect my top 20 URLs and tell me which are not indexed and why.”
- “Audit the site before this release and list anything that blocks indexing.”
- “Find the queries where I rank on page 2 and draft what each page is missing.”
- “Check my sitemaps in Search Console and fix the generator if any have errors.”
- “Compare clicks for the last 28 days with the 28 days before and find the cause of any drop in the code.”
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. Grok Build itself is billed by its maker, not by SEOmatic: nothing on our side counts tokens.
Nothing Changes on Your Site Without Your Approval#
Grok Build edits your code; it never pushes changes to your live CMS on its own. 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. Code changes follow your normal review: nothing ships until you merge and deploy it.
- Grok Build 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 Grok Build, 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 Grok Build 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: Grok Build. See disconnect an assistant.
Was This Article Helpful?
Still need help?Email contact@seomatic.ai with your site address and a screenshot. A person replies, usually within one business day.


