An AI SEO agent that works in your own AI assistant and asks before it changes your site

XeoRank is an AI SEO agent that works through the AI assistant you already use, such as Claude, ChatGPT, Codex, Cursor or VS Code. You ask in plain language, the assistant calls XeoRank's tools to audit your site, research keywords and check rankings and AI answers, and when it changes your pages, your AI assistant asks before each tool call.

The SEO agent runs in your own AI assistant. XeoRank's side is an MCP server at https://mcp.xeorank.com/mcp, listed in the official MCP Registry as com.xeorank/xeorank, with more than 200 tools. Your assistant decides which tools to call. XeoRank does the work and returns the data.

What you can ask the agent

Type requests like these, with your own domain and pages:

• "Crawl example.com and list the pages with missing titles, broken links, redirect chains or errors in their structured data. Link each issue to our organic traffic goal."
• "Compare this month's Search Console clicks and impressions with last month. Which queries moved, and how much of the traffic was branded?"
• "Find keywords with real monthly search volume around 'bookkeeping for dentists', cluster them by intent, and show me the bottom-of-funnel ones."
• "Which of our tracked buyer questions does Perplexity answer without naming us? Show the ChatGPT and Gemini answers separately."
• "Write a content brief for the bookkeeping cluster, then review my draft and flag every claim that has no source."
• "Rewrite the title and meta description on /pricing in Rank Math, add FAQPage schema for the questions already on the page, and show me the new title and meta description before you write them."

You do not need to know any tool names. The assistant picks them and chains them, so one request can run a crawl, read Search Console data and prepare a fix.

How the AI SEO agent fits your SEO workflow

1. Connect XeoRank to your assistant once. Setup is further down this page.
2. Add your site. Connect Google Search Console and GA4 for traffic data, and install the XeoRank Connector plugin if the site runs on WordPress.
3. Ask for something. The assistant calls the tools, XeoRank runs the crawl, the keyword research or the rank check, and the results come back into your chat.
4. If the answer needs a change to the site, the assistant makes it with a write tool and asks you before each tool call. WordPress writes stay off for a site until you turn them on.

XeoRank also stores the results of AI visibility scans, rank checks and backlink refreshes (the last two on Pro and Growth), so history builds up between sessions, as listed on the pricing page. When you next open the chat, the agent reads that history instead of starting from nothing.

Approve before apply

An AI with write access to a live website needs limits. These are on by default:

1. Writes are off for each WordPress site until you turn them on for that site, and you can turn them off again.
2. New pages, such as a new landing page, and page clones are saved as drafts. Edits to an existing page change that page directly.
3. Every change to a page's content is snapshotted first, up to 20 per page, and any snapshot can be restored. SEO meta, menus and custom code are not snapshotted.
4. The assistant can send you a preview link for a draft, so you see it before visitors do.
5. Your AI assistant asks before each tool call, so a change runs only when you allow it.

On WordPress the agent edits existing pages and posts, including Elementor layouts written as native containers and widgets, and Elementor 4 atomic elements. It writes titles and meta descriptions to Yoast, Rank Math or All in One SEO, adds schema, uploads images, and manages menus and templates. Framer projects and code sites deployed through GitHub and Vercel go through the same assistant prompts, but have no write switch or snapshots: Framer changes stay staged until you publish, and a code-site commit deploys when it is made.

XeoRank compared with autopilot SEO tools

Some SEO tools are sold as autopilot: you connect the site and they publish changes or new pages without a review step. That saves your time when every change is right. When one is wrong, it is already live. XeoRank takes the opposite approach.

If you want SEO changes published with nobody checking them, XeoRank is the wrong tool. If you want the work done for you while you keep the final say, it fits. If you would rather have people do the work, AI SEO services from an agency are the closer match.

Comparing specific tools? See Alli AI alternatives and Surfer SEO alternatives.

Is it autonomous SEO?

Partly. The agent can run a whole audit, research or tracking session from one request, and your plan keeps tracking history between sessions. The changes to your site are different. XeoRank is not fully autonomous by design. Every change is a tool call your AI assistant asks a person to allow first, because a mistake on a live site is in front of every visitor until someone notices it.

The agent can also re-measure the goals on your goals roadmap when you ask, and link open site issues in the fix queue to the goal they affect, so you can see which fixes are meant to move which number.

What the agent does not do

• It does not work without an AI assistant. You need your own Claude, ChatGPT, Cursor or other MCP client, and that subscription is a separate cost from XeoRank.
• It does not publish on its own. Every site change is a tool call your AI assistant asks you to allow first.
• It tracks fewer AI engines than AthenaHQ or Profound. XeoRank asks ChatGPT, Gemini (grounded in Google Search) and Perplexity your buyer questions; see pricing for what each plan includes.
• It does not estimate prompt volume, so it cannot tell you how many people ask a given question in ChatGPT.

Set it up

For Claude Code, run:

claude mcp add xeorank --transport http https://mcp.xeorank.com/mcp

For Claude.ai, Claude Desktop, ChatGPT, Cursor or VS Code, add a custom connector or MCP server with the URL https://mcp.xeorank.com/mcp and sign in when asked. The MCP setup guide has the steps for each client, including Codex, and the SEO MCP server page covers what the tools do in more detail. If you build sites with a coding agent, Vibe coding meets SEO shows how to give Claude Code or Codex the same SEO context.

What it costs

MCP and API access come with every plan, according to the pricing page. Starter is $19 a month for one site, with a 14-day free trial and no card. Pro is $49 per site a month and adds more AI visibility prompts, live rank checks and the Writing Agent. Growth is $109 per site a month, with more prompts and 2-year history and rollbacks. AI site edits on WordPress, Framer and code sites are unlimited on every plan. Other actions draw from your plan's credits, and each one shows its cost before it runs. To see what the agent would find first, run a free site analysis.