AI SEO agents: what an SEO agent does alone and where you approve
An AI SEO agent is software that uses an AI model to do SEO tasks in a loop: it reads data, decides what to do, calls tools, and checks the result. In this article, "agent" means that loop. A good agent reads data and measures results on its own. It asks you before any step that changes your site or spends money. This article explains how an agent works, which tasks it can do alone, which need your approval, and how the rules of Google shape the limits.
What an AI SEO agent is
People use the word "agent" for three different things:
- A chat assistant that answers SEO questions. It does not touch your site.
- An SEO tool with an AI feature, such as a button that writes a meta description. You start every action.
- An agent, which decides the next step itself and uses tools to take it.
The test to tell them apart is simple. Ask who starts the next action. If you start it, it is a tool. If the software starts it, it is an agent.
"Agentic SEO" means SEO work that agents do. This article does not cite a standard definition of it. Treat a vendor claim about it as a product description, not a measured result.
How an AI SEO agent works
Every agent in this class runs the same loop. The names differ by product. The shape does not.
- Read data. The agent pulls rankings, Search Console data, crawl results or backlinks through an interface.
- Find issues. It compares the data with rules or with its own judgment. It lists what looks wrong or missing.
- Propose a fix. It drafts a change: a rewritten title, a new brief, a redirect, a pitch.
- Apply the fix. It publishes, edits or sends the change.
- Measure the result. It reads the data again and checks whether the change helped.
Steps 1, 2 and 5 only read. Step 3 produces a draft. Step 4 changes the world. That is why the approval point belongs between steps 3 and 4.
How the agent reaches your data
An agent needs a standard way to call tools. Model Context Protocol (MCP) provides it. The MCP documentation calls it an open-source standard for connecting AI applications to external systems. It compares MCP to a USB-C port: one standard plug for many devices.
An MCP server lists the tools an agent may call. Each tool has a name, inputs and a result. The agent picks a tool, fills the inputs and reads the result. If the server exposes only read tools, the agent cannot change anything. That is the first and strongest control you have.
Strategist ships an MCP server with 70 tools and a Claude Code plugin with 18 skills. Each tool has a scope: read, write or run-paid. You create the keys under Workspace settings, in the Agents tab. A tool that touches a site first checks that the caller may open that site.
What an agent can do alone
Give an agent the work where a wrong result costs little and you can spot it fast. These tasks are safe to run without a person in the loop:
- Read and report. Pull ranking, traffic and index data. Summarize what moved.
- Check status. Check whether URLs are indexed, whether links break, whether pages return errors.
- Score and sort. Rank a list of issues so the most useful one comes first.
- Monitor. Run on a schedule and raise a flag when a number moves.
- Measure outcomes. Compare data before and after a change.
None of these edits your site. A wrong run wastes a little compute and a little attention. A person reads the output and decides.
In Strategist, the SEO action engine scores findings from eight sources on one 0 to 100 scale.
Where you approve
An agent should propose these steps and wait for you:
| Task | Why you approve |
|---|---|
| Publish or rewrite an article | A page is public the moment it goes live. Facts and claims need a human check. |
| Change titles, redirects or canonical tags on many URLs | One wrong rule repeats across the site. |
| Send outreach pitches | A message goes out under your name. |
| Spend on paid data | A run can use a metered API. |
| Submit URLs in bulk to a search engine | Engines set rules and daily limits. |
Levels of autonomy
Think of autonomy as four levels. Pick one per task, not one per agent.
Level 3, apply after approval, suits most publishing and edit tasks. Level 4 suits a narrow set of reversible tasks. Do not move a task to level 4 until you have reviewed its output many times and found no errors you would object to.
How tools implement an approval step
Approval is not a new idea. Claude Code uses a tiered permission system. In manual mode, it asks before it runs shell commands, edits files, fetches web pages or searches the web. Reading files inside the working directory needs no approval. Read-only steps run without a prompt. Steps that change something ask. That is the same split this article recommends for SEO.
In Strategist, content refresh stages each rewrite for you to publish and roll back, and outreach drafts pitches that you send yourself.
What Google says about agent-written content
Google does not ban AI content. Its guidance on generative AI says the tools can be useful when you research a topic and to add structure to original content. It also sets two limits.
First, accuracy. Google explains that generative models predict likely word sequences. They do not retrieve facts. The guidance says that "it is critical to manually factcheck and review all AI-generated content for accuracy and trustworthiness before publishing." A review step is therefore the stated advice, not an extra.
Second, scale. The spam policies define scaled content abuse as many pages "generated for the primary purpose of manipulating search rankings." One listed example is using generative AI tools or similar tools to generate many pages without adding value for users. The policy covers the purpose and the value, not the tool. An agent that publishes hundreds of thin pages is a risk. An agent that drafts one well-researched page for each real question, and a person who checks it, is not what the policy describes.
Google also suggests that you explain how automatic content was created, including how automation was used. Consider a short note on pages where an agent did most of the work.
Do not use an API for a purpose it does not allow
An agent can call any API you give it, so you must set the limits. Google's Indexing API works only for pages with JobPosting or BroadcastEvent markup inside a VideoObject. Google also warns that abuse, such as using many accounts to exceed quotas, may lead to revoked access. An agent that submits ordinary blog posts to this API breaks the rule. Write the allowed uses into your agent's instructions, and keep the key for that API out of reach of any agent that does not need it.
How an agent differs from an SEO tool
| SEO tool | AI SEO agent | |
|---|---|---|
| Who starts an action | You | The software, on a schedule or a trigger |
| Scope of one run | One task | A sequence of tasks |
| Where it lives | A dashboard | A dashboard, an MCP client or a chat |
| Main risk | You forget to run it | It acts on a wrong assumption |
| Main control | Your attention | Scopes, approvals and logs |
The last row matters most. With a tool, your attention is the control. With an agent, you replace attention with rules, so you must write the rules.
How to start with an agent
Follow this order. It keeps the cost of a mistake low.
- Start read-only. Give the agent keys with read scope only. Ask it for a report on one site.
- Check its numbers. Compare three figures in the report against the source tool. If they differ, find out why before you go on.
- Add one proposal task. Let it draft one kind of change, such as a title rewrite. You apply the change.
- Add approval for one write. Let it apply that change after you approve it. Read the log.
- Set a budget. If the agent uses a paid model or paid data, cap the spend before you raise its level. Strategist has an AI and budget setting in each workspace for this.
- Review on a schedule. Read the log of what the agent did. Remove a task from automation if you cannot explain its output.
Work with your existing team
An agent does not replace the person who knows the business. The agent handles volume: checks, sorting, drafts. The person handles judgment: which topics to pursue, which claims are true, what the brand may say. Give the team one owner for approvals, so that a queue does not stall. The use case page Your agent runs your SEO shows how Strategist exposes this loop to agents.
Common failure modes
Plan for these before you turn an agent on:
- A wrong assumption repeats. If the agent misreads one rule, it applies the mistake to every page it touches. Limit each run to a small batch.
- A loop does not stop. An agent that retries a failed call can run many times. Set a cap on calls and on spend.
- Output drifts from the brand. Without a voice guide, drafts sound generic. Give the agent the guide and check the first drafts.
- Facts are wrong. A model can state a false fact in a confident tone. Google's guidance says to check facts before you publish.
- Credentials spread. An agent with a broad key can do more than you meant. Give it the narrowest scope that does the job.
None of these is a reason to avoid agents. Each is a reason to set limits first.
What to ask before you trust an agent
Ask each question of a vendor, or of your own setup:
- Which tools can the agent call? Which of them write?
- Does a person approve each write? Can you turn that off per task?
- Does the agent log every action with a time and an input?
- Can you undo a change? How?
- Who holds the API keys? Can the agent leak them?
- What stops a run from spending more than you set?
If a vendor cannot answer these, do not give the agent write access.
FAQ
Can an AI SEO agent run without human oversight?
It can run read-only tasks alone. For tasks that change your site, send messages or spend money, keep an approval step. Google advises that you fact-check and review AI-generated content before you publish it.
Will Google penalize content an AI agent wrote?
Google's spam policies target scaled content abuse: many pages made mainly to manipulate rankings, with no added value. The policy names generative AI as one way to do this. It does not ban AI content as such. Review each page for accuracy and value.
What is the difference between an AI SEO agent and an SEO tool?
You start every action in a tool. An agent starts actions itself. See the table above.
Next steps
- Read SEO automation: which tasks to automate, with an approval step to sort your own tasks into tiers.
- Read Claude for SEO to see what an MCP server lets an agent do with your data.
- Read SEO APIs to compare the data you can pull.
