Skip to content

/ SEO for Agencies

Every client's SEO data, in the AI you already use.

Agencies run on context-switching: a Search Console login here, a GA4 property there, a CSV export for the monthly report, repeated across every client. That SEO Agent connects all your client sites to Claude Code or Cursor. Ask about any client by name and your AI pulls that client's live data, drafts the report, and tracks the fixes. Every client site, every tool, one connection.

/ SEO for AgenciesEvery client siteShareable reportsPer-client tasksEvery tool
All
your client sites, with every tool unlocked on each. Nothing is gated and nothing is sold separately
That SEO Agent
0
CSV exports. The data arrives in the conversation, not in a spreadsheet you reformat every Monday
That SEO Agent
5
tool categories, from Search Console and GA4 reads to page-level and whole-site audits
That SEO Agent
1
connection covers every client. Switch clients by name, not by logging into another dashboard
That SEO Agent, MCP server

01

What agencies actually spend their time on

The work that makes an agency money is analysis and decisions: which client is slipping, which page is worth updating, what to tell them on the call. The work that fills the day is everything around it: logging into one client's Search Console, setting the date range, hitting the 1,000-row export cap, opening their GA4, cross-referencing by hand, then doing it all again for the next client.

That overhead scales with your roster. Each client is at least two Google logins, Search Console and GA4, behind separate interfaces with their own export limits. An agency running 30 clients is maintaining 60 separate data views before a single recommendation gets made. The monthly reporting cycle alone can eat days that bill for nothing.

Most tools answer this with a heavier platform: more dashboards, more tabs, seats and roles and a procurement process. That adds surface area, not speed. The analysis still happens in your head, and now there is more software to drive to get to it.

That SEO Agent takes the opposite path. It connects every client site to the AI you already work in, and the AI does the fetching and cross-referencing. You ask the question in plain language; it pulls the live data for that client and answers. The overhead collapses; the analysis is still yours.

2
Google logins per client before you see a single number: Search Console and GA4. Multiply by your whole roster
Google Search Console and GA4
An agency with 30 clients maintains 60 separate data views. That is the tax this removes, not the analysis.

Connect your whole client roster to one AI

02

The agency workflows that get faster

Same questions you answer every month, minus the logging-in, exporting, and reformatting. Ask across any connected client in one conversation.

New client audit
Before
Crawl tools, manual GSC and GA4 review, a deck built from scratch
With That SEO Agent
One prompt runs the full audit and answers in the conversation, per client
Monthly client reports
Before
Re-export GSC and GA4 per client, reformat, write the summary, every month
With That SEO Agent
Ask for the month's numbers per client, read from live data rather than an export
Triage across clients
Before
Open each client's Search Console to check who dropped
With That SEO Agent
Ask which clients lost the most clicks this week, answered across the roster
Quick wins per client
Before
Filter and pivot exports to find page-two queries, client by client
With That SEO Agent
Ask for striking-distance queries on any client; get them with impressions and position
Tracking the fixes
Before
A spreadsheet of to-dos per client that drifts out of date
With That SEO Agent
Audit a page before and after a change; the second run reports what moved
Answering the client call
Before
Scramble through tabs while they ask why traffic moved
With That SEO Agent
Ask the agent live, in the call, against their current data
3
Three Google sources, per client, on demand.
Search Console, GA4 and PageSpeed, read live for whichever client you asked about. You do not pick which of them a client gets, and you do not assemble them by hand: the agent fetches all three and cross-references them in the answer. Add a client and the same three are there.
That SEO Agent, MCP server

03

Built for the SEO doing the work, not the procurement around it

There is no white-label mode, no client logins, no seats, no roles, and no SSO. That is deliberate. Those features serve the buying process and the org chart, not the person actually analyzing a site and deciding what to fix.

What you get instead is the work surface: every client's live data in your AI, audits on demand, and a recorded history you can ask questions about next month. No portal to administer, and nothing for a client to log into.

This makes the tool a poor fit for an agency that needs a multi-seat platform with permission matrices and compliance audit trails. It makes it an excellent fit for the practitioner, solo or in a small team, who is responsible for client outcomes and wants the overhead gone.

The model does not change as your roster grows: what you connect is client sites, and what you get on each of them is the whole toolset. There is nothing to upgrade to, because there is no level that holds a tool back from you.

0
seats, roles, SSO, and permission matrices. The work surface, not the org chart
That SEO Agent, what we don't do
The procurement layer is not the product. The SEO doing the work is.

04

Get your roster connected in three steps

STEP 01
Connect your client sites
Create your own Google OAuth client and log the server in once. The Search Console and GA4 properties your Google account already has access to become readable, read-only. Most agencies are granted access to client properties in the normal course of work, so they show up ready to query.
STEP 02
Run the server
Clone the repository and start it: `git clone --depth 1 https://github.com/thatseoagent/mcp.git`, then `pnpm install && pnpm build && pnpm start`. Point your AI client at the loopback address it prints. One running server covers every client site you manage, and there is no key to issue.
STEP 03
Ask across clients
From Claude Code or Cursor, ask: "Which of my clients lost clicks this week?" or "Audit client.com and tell me what to fix first." Your AI works across the whole roster from one running server.
Sources and references
Official documentation
Search Console API usage limits — Google Developersdevelopers.google.com
Manage users and permissions in Search Console — Googlesupport.google.com
GA4 account and property access management — Googlesupport.google.com
Scope and limits
That SEO Agent — what we don't dothatseoagent.com/what-we-dont-do
Model Context Protocol — official documentationmodelcontextprotocol.io
/ FAQ

Common questions from agencies

How many client sites can I manage?

Every client site you connect, with every tool unlocked on each. You connect the Search Console and GA4 properties your own Google account already has access to, so adding a client is a matter of that access existing, not of buying another slot.

Is there a white-label mode or client-branded reports?

No. There is no white-label mode and no client logins. Reports are shareable URLs you can send to a client, not a branded portal you administer. This is a deliberate choice: the tool is built for the person doing the SEO work, not the reporting structure around it. If you need a fully branded multi-seat client platform, this is not the right fit.

Do you charge per seat, per user, or per client?

None of those, and right now nothing at all: there are no public plans and the hosted server is not on sale. What that means in practice is that there is no per-seat fee, no per-client setup cost, and no add-on to buy, and that every tool is unlocked on every site you connect.

Can my whole team use it?

The tool is built around a single operator running a single server, not team seats, roles, or permission matrices. A small team can share access to a machine, but there is no multi-seat user management, SSO, or audit trail. It is designed for the practitioner responsible for client outcomes, not for managing a large team's permissions.

Can I send reports to my clients?

Not as a link. The open-source server has no tool that publishes a report to a URL — that was a feature of the hosted service. The full report comes back in the conversation, and the history behind it stays in the server's own database, so you can ask what moved since last month. There is no public link to hand a client: paste the answer into whatever you already send them.

Does each client need to give me their own Google login?

No. You connect the Search Console and GA4 properties your own Google account already has access to. Agencies are typically granted delegated access to client properties in the normal course of work, so those properties appear automatically once you sign in. The agent only reads the data, it cannot change anything in the client's account.

/ SEO for Agencies

Run every client from one AI.

Every client site. Every tool. One connection.

Read the docs

Connect your client roster and ask your AI about any of them, from live Search Console and GA4 data.