Run your SEO from your AI assistant.
Your AI assistant reads your WordPress SEO, proposes the fix, and applies it only after your approval. Dry-run first. Approve every change. Roll back eligible changes.
- Open-source MCP library (MIT)
- EU-hosted
- Hosted MCP · up to 10 sites per connection
You already live in Claude. Your SEO doesn't.
Today
- Log into wp-admin, site by site
- Hunt down missing meta titles
- Paste redirects by hand
- Cross-check 404s in another screen
- Repeat for every client
With TamRank
- Ask in the chat you already have open
- The agent finds what is wrong
- It proposes the fix, you approve
- Every change logged, rollback available
- Works on the website you connected
Your SEO work shouldn't need a separate tab.
Watch one change go all the way round
Ask, diagnose, dry run, approve, execute, roll back. The same six steps every time, on an invented site so nothing here is a real customer.
- Ask
- Diagnose
- Dry run
- Approve
- Execute
- Roll back
get_work_queue6 pages missing titlesget_page · metadatatitle 58 chars · description emptyrollback_change_setrestore title to: Road bike maintenance | Northfield Cyclesexecute_change_setapproved restoration appliedTwo kinds of "AI for WordPress", and the gap between them
Generic write-connectors
Let an agent change your site: raw CRUD, no preview, no rollback, and no idea what SEO is.
TamRank
Reads your situation. Sets the priority. Executes safely.
Built for agents, not adapted from a generic CMS bridge.
SEO data-feeders
Feed your agent data and reports, but cannot safely touch your site.
We don't compete on tool count. The question is whether you get the right fix, and whether you can take it back.
What stops it going wrong
Dry-run by default
The assistant prepares an exact proposal with the pages, old and new values, and warnings. Preparing that proposal changes nothing on your site.
Approval gate
You approve the proposal in the chat. The assistant executes that exact set; different values need a new proposal and approval.
Scoped connections
Each connection can reach up to 10 sites you ticked, with the permissions you approved. Your assistant names the site on every call. You can see and revoke assistant connections in your TamRank MCP account.
Change history
Changes retain their proposal and execution history. The assistant can read the status of a change set created through its own connection.
Bounded rollback
Eligible changes can be restored as a whole set or a selection. Rollback creates a new proposal for your approval and protects newer changes from being overwritten.
A read can never become a write.
What the agent can call
The assistant starts with get_capabilities to check the connected website and its permissions. These are examples of the core hosted workflow.
Reads
get_capabilitiesAccessget_site_contextContextget_work_queuePrioritiesget_signalsSignalssearch_pagesPagesget_pagePage detaildiagnose_pageDiagnosisget_changesChange history
Changes and task updates
plan_changesProposeexecute_change_setApply approved setrollback_change_setPropose rollbackupdate_work_itemTask administration
SEO meta, social fields and image alt text use proposal, approval and execution. Redirect actions depend on the website capabilities and approved connection permissions. Marking a task complete does not approve a change or prove the issue is fixed.
Set it up in three steps
Start in your assistant, then approve access to the sites you choose.
-
1
Add the hosted connector
In claude.ai, add a custom connector with the URL https://mcp.tamrank.com/mcp. Other clients need support for remote MCP and its OAuth sign-in flow.
https://mcp.tamrank.com/mcp -
2
Sign in and choose your sites
Sign in with your TamRank account, review the requested permissions and tick up to 10 sites that are already connected to TamRank. A new site goes through the WordPress approval step first. Each site needs an active TamRank PRO license.
-
3
Ask your first question
Ask what the top SEO issues on your site are. The agent reads the site and answers; nothing is written until you approve a change.
"What are the top SEO issues on my site?"
Where it runs
- claude.ai
Connect from claude.ai in your browser. Other assistants need compatible remote MCP and OAuth support. Each connection reaches up to 10 sites that are already connected to TamRank; there are no changes across all sites at once and no central agency dashboard.
-
EU-hosted
Our API, our error monitoring and our email all run on EU infrastructure.
-
No visitor tracking, no data resale
The plugin adds no scripts, pixels or analytics to your frontend, and we never sell personal data.
-
Your assistant account
Use your own AI assistant account. The hosted connection gives it only the website access you approve.
Inspect the MCP library
The MCP library used by the hosted service is open source under the MIT license. You can inspect its workflow and safeguards.
TamRank/mcp-server
Agent access is part of every TamRank PRO plan, from €99/year.
Questions people actually ask
Can it break my client's site?
The assistant first checks what your site and connection allow. Supported changes include SEO titles and descriptions, social fields and image alt text. Page content and WordPress settings are outside this workflow. You see the exact proposed changes before approving execution, and eligible changes can be rolled back after a new proposal and approval.
Which websites can a connection access?
The sites you tick when you connect, up to 10, with only the permissions you approved. Each site must already be connected to TamRank in WordPress. Your assistant names the site on every call; there are no changes across all sites at once and no central agency dashboard. You can review and revoke assistant connections in your TamRank MCP account.
What happens when my license expires?
The agent loses access: the server refuses the site without an active PRO license and tells you why. Your site keeps running, your data stays in your own WordPress database and nothing is deleted. Reading over the free REST API stays available, so anything you script yourself keeps working.
Does it work from claude.ai in the browser?
Yes. Add https://mcp.tamrank.com/mcp as a custom connector in claude.ai, sign in with your TamRank account and follow the approval flow to choose up to 10 of your sites with an active PRO license.
Do I give the assistant my WordPress password?
No. You sign in to TamRank and approve the website connection in WordPress. The hosted MCP service then accesses the site through that authorized connection. Your assistant does not receive your WordPress password.
Can I use this on a free TamRank license?
Agent access is PRO. The REST reads are free for anyone who would rather script it themselves.
Is this AI search optimization?
No, that is a different axis. This is about an assistant doing your SEO work for you, not about optimizing your pages to be quoted by AI search engines.
