You can now ask the AI agent you already code in — Claude Code, Cursor, Codex CLI, Copilot, Windsurf, Cline, or any other MCP-capable agent — whether ChatGPT, Gemini, Claude and Perplexity cite your WordPress site, and get the answer from your own site’s data rather than a guess. It needs the free AEO Ultimate plugin, a free skill file, and about ten minutes of setup. There is no account to create and nothing to subscribe to.
That is the whole of it. The rest of this page is how, and what to ask once it works.
Read the transcript
0:00 Ask your agent if AI engines cite you
Your AI coding agent can read your site's own answer engine data. Which AI engines cite you, which crawlers read your pages, what Google has not indexed. It is free, it works in any agent that speaks MCP, and there is no account to create.
0:19 Why rank tracking does not answer this
A rank tracker gives you a position in a list of links. An AI answer has no position one. Each time someone asks, the engine either cites your page, names you without a link, or leaves you out and cites somebody else.
0:34 Turn the connector on
It starts in WordPress. Install the free AEO Ultimate plugin, open Settings, then MCPs, and turn the connector on.
0:43 Create a connection password
Create a connection password. It is a WordPress application password tied to your account. It works only for apps like this, never for logging in, and you can revoke it whenever you like. Copy it now, because it is shown only once.
0:58 Add it to your agent
The screen fills in the rest. Claude Code is one command; other agents take the same URL and header in their own config file. Paste it, then restart the agent — nearly all of them load their tools when the window opens.
1:13 Ask it a question
Now ask in plain language. Which AI engines cite us, and who gets cited instead? The agent starts with the site overview and goes deeper on its own.
1:24 Real data, not a guess
This is your own data: citation runs on your own API keys, crawler visits to your own pages, your own indexing and page scores. Nothing is estimated.
1:35 Read-only until you say otherwise
Changes are off until you turn them on. Even then, every change takes two steps. The agent shows you exactly what it would write, and writes it only after you say yes. One page at a time.
1:49 The skill
The connector works on its own. There is also a free skill file that teaches an agent which tools to reach for and how to read what comes back — six worked analyses instead of a list of tools. It is listed on the Agensi skill marketplace.
2:04 Where to get it
Install the plugin free from WordPress dot org, and read the written guide at aeoultimate dot com slash docs slash claude.
The video walks through the same setup on a live site, and ends with an agent answering the question from that site’s own data.
Rank tracking does not answer this question
A rank tracker tells you where you sit in a list of blue links. It says nothing about whether an engine named you when someone asked a question in plain language — and that is now how a large share of buying research starts.
There is no position one in an AI answer. Each time someone asks, the engine either cites your page as a source, names you without a link, or leaves you out and cites somebody else. Three outcomes, not ten positions. We wrote about why that scoreboard is different in SEO vs answer engine optimization.
You can check it by hand — open each assistant, ask the questions your buyers ask, write down what happened. That works, and it is worth doing once. It is also slow, and the answers move with the wording, the day and who is asking, so one afternoon of checking proves very little.
The plugin has recorded this for a while: AI Visibility asks eight engines the questions your buyers ask, on your own API keys, and stores which of the three outcomes happened and who was cited in your place. What is new is that your agent can now read all of it, along with your crawler logs, indexing status and page scores, and reason about it with you.
What the skill actually is
A skill is a markdown instruction file an AI agent reads when the subject comes up. This one teaches an agent how to drive the MCP server that is already built into the AEO Ultimate plugin — 39 tools, 25 that read and 14 that write.
The skill itself contains no code, makes no network calls of its own, and holds no credentials. It is instructions. The data never leaves your site except to go to the agent you are already talking to.
You do not need it to use the plugin, and you do not need it to use the connector. Everything below works with the connector alone. What the skill adds is knowing which of the 39 tools to reach for, in what order, and how to read the result — six worked analyses instead of a tool list.
What you can ask it
Plain questions. Some of the ones the skill is built around:
“Am I showing up in AI answers, and why not?” — pulls every AI Visibility run, works out the citation rate per engine and per question, and finds the questions no engine cites you for. The part a dashboard cannot give you is the trend: a 40% citation rate that was 25% last month is a success story; the same number falling from 60% is an emergency.
“Do AI systems read my site, and does it send me anyone?” — visits per bot per day, which pages each bot reads, whether they ever fetch your llms.txt and the Markdown versions of your pages, and which pages AI answers actually send people to.
“Audit my site.” — the full health report: AEO score and trend, how readiness is spread across pages rather than averaged, what Google has not indexed or has not re-crawled in 90 days, missing trust signals, schema conflicts.
“What’s the fastest thing I can fix?” — up to ten changes ranked by impact for the effort, each with the exact text it would write.
“Who gets cited instead of me?” — the competing domains, grouped by theme, and for each one whether the fix is new content, a better page, or making an answer you have already written easier for an engine to find. That third case is the one people miss.
“What’s wrong with this page?” — a single URL, end to end, including what a bot actually receives when it fetches the page. That last check finds the problems nobody expected: a firewall serving crawlers a challenge page, or content that only exists after JavaScript runs.
Setting it up
Most of this is copy and paste — the plugin writes the configuration for you. You need an administrator account and a site on HTTPS, because WordPress refuses to issue application passwords over plain HTTP.
- Install the free AEO Ultimate plugin. It appears in the WordPress menu as TWT AEO — that is the name wordpress.org requires, same plugin.
- Open TWT AEO → Settings → MCPs. Under 1. Turn on the connector, switch it on.
- Under 2. Create a connection password, click the button. That makes a WordPress application password tied to your account: it works only for apps like this one, never for logging in, and you can revoke it at any time. It is shown once.
- Under 3. Connect Claude, the rest is already filled in, credential included — take whichever block matches your agent.
Claude Code
One command, ready to run:
claude mcp add --transport http --scope user aeo-ultimate-your-site-com https://your-site.com/wp-json/aeo/v1/owner-mcp --header "Authorization: Basic …" --header "X-AEO-Authorization: Basic …"
Claude Desktop, and Claude on the web
Claude Desktop takes a claude_desktop_config.json block that bridges through mcp-remote; it needs Node installed. Claude on the web and mobile uses the hosted OAuth route instead, where you sign in in the browser rather than pasting a credential — the first site is free, and it is documented at aeoultimate.com/docs/claude.
Any other MCP client
Cursor, VS Code, Windsurf, Cline and the rest want the same two things in their own config file. Copy the Basic … value straight out of the Claude Code command above; that is your header.
{
"mcpServers": {
"aeo-ultimate-your-site-com": {
"type": "http",
"url": "https://your-site.com/wp-json/aeo/v1/owner-mcp",
"headers": {
"Authorization": "Basic BASE64_HERE",
"X-AEO-Authorization": "Basic BASE64_HERE"
}
}
}
}
Key names vary — mcpServers or servers, type or transport — so check your client’s own docs for the wrapper. The three things it needs never change: HTTP transport, the URL, the headers.
Then restart the client. Almost every agent binds its MCP servers when the window opens, so a server you add mid-conversation will not appear in that conversation no matter how correct the file is. Reload, start a new chat, and ask for a site overview.
Why the header is there twice: some hosts — anything running PHP as CGI, which is common on cPanel — strip Authorization before PHP ever sees it, so the plugin accepts X-AEO-Authorization with the identical value as a fallback. The copy boxes set both from the start, which saves a confusing 401 later.
Several sites means several entries. There is no per-site limit and nothing to pay for connecting directly.
Building the header yourself
If you would rather not use the generated command — say your client keeps credentials somewhere else — the value is just your WordPress username and the application password, base64-encoded. On macOS or Linux:
printf 'USERNAME:APPLICATION PASSWORD' | base64
On Windows, in PowerShell, where printf and base64 do not exist:
[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('USERNAME:APPLICATION PASSWORD'))
It is read-only until you say otherwise
This is the question everyone asks, so: the connector ships read-only. Write tools do not exist in your agent’s tool list until you switch them on in that same settings screen.
When you do switch them on, every write is two steps. The agent calls the tool without a confirmation token: nothing changes, and it gets back a preview of exactly what would be written. You read the preview. Only if you approve does it call again with the token, which is bound to those exact arguments and expires in about fifteen minutes. An agent cannot mint one, reuse one, or approve its own change.
An audit-only setup — writes left off — is a perfectly good way to run this, and it is the default for a reason.
Which agents this works in
Any agent that speaks MCP. The listing shows it working with Claude Code, Cursor, Codex CLI, Gemini CLI, Copilot, Windsurf, Cline, VS Code, Zed, Kiro, Aider, Grok, Manus, Muse, Dots and others — around two dozen.
Agents that can only launch local processes rather than call a URL need a bridge (mcp-remote); the skill’s own setup notes cover it.
Where to get it
The skill is free and listed here: AEO Ultimate for WordPress on Agensi.
That is an affiliate link: if you later buy something from that marketplace, we may earn a commission. The skill itself is free, and so is the plugin.
You can also just install the plugin, switch the connector on, and ask your agent questions without the skill at all. The skill makes it better at knowing where to look.
Frequently asked questions
Do I need the skill to use the AEO Ultimate connector?
No. The connector works on its own. The skill teaches an agent which tools to use for a given question and how to interpret what comes back.
Does this send my site’s data to a third party?
Only to the agent you are already using. The connector runs inside your WordPress site; the skill is a markdown file with no network access of its own. AI Visibility checks run on your own API keys, direct to the provider.
Will this make ChatGPT start citing my site?
Nothing can promise that. What this gives you is the measurement — which engines cite you today, which questions you lose and to whom — so the work you do next is aimed at something real instead of a guess.
Is it safe to let an agent change my site?
Writes are off by default. When enabled, every change previews first and applies only after you approve that specific preview. Leaving writes off and using it purely as an auditor is a sensible way to start.
Does it cost anything?
The plugin is free on wordpress.org, and the skill is free. AI Visibility runs use your own AI provider keys, so you pay that provider’s rate for the questions you ask and nothing on top.
What if I run several sites?
Add one entry per site. No limit, nothing to pay for the direct connection.
Owner of Tampa Web Technologies Inc. and Creator of AEO Ultimate
David Chamberlain is an SEO, AEO, and GEO specialist with 17 years of experience in digital optimization. He holds a professional certification in AI Fluency: Framework & Foundations, issued by Anthropic Education, an educational division of Anthropic. Chamberlain currently owns his own business focused on search and optimization services.