What to automate and what to keep: the dispatcher rule
A scheduled rank check runs without anyone watching. A decision about which keywords go in it does not. How to split SEO work into what a schedule does, what an agent does, and what stays with a person.
Which SEO tasks should be automated?
The ones with a fixed input, a fixed output and no judgement in between. Everything else needs either an agent with a person reading its work, or a person.
That sounds obvious and it is where most SEO automation goes wrong, because the temptation is to automate the interesting part. A useful picture: the agent is a truck driver and you are the dispatcher. The driver sits high in the cab and moves fast, and it can drive over someone's lawn without noticing it did.
You are the dispatcher. The agent drives. You tell it where to go and you tell it when it went over the grass, and the second part is not optional, because the agent has a hard time noticing on its own.
Three layers, not two
Most advice splits work into "automate" and "do by hand". The useful split has three layers.
Schedules. Fixed input, fixed output, no model involved. A rank tracker checking a set of keywords every Monday. A Search Console property that syncs on its own. A monthly audit you start with one call. These run without an agent and without a person, and they are the cheapest thing in SEO. The only decision is what goes in, and that decision is made once.
Agents. Variable input, structured output, a person reads it. Summarise what moved in this week's tracker check. Bucket the audit's findings by cause. Draft the report from the numbers. The agent does in a minute what took an afternoon, and the person reads the result the way an editor reads a draft.
People. Deciding what to track, what to build, what to say to the client, what to ignore. Anything where being wrong costs more than being slow.
The first layer is the opposite of what the market is selling: a repeated task does not have to involve AI at all, and not everything should. The second layer starts with whatever takes too much of your time and keeps coming back. Turn that into a saved workflow and improve it each time you run it.
Take a weekly rank tracker as an example of the first layer: a fixed list of keywords, one device, checking the top 40 results, every Monday. The app estimates the cost before it runs, and nothing spends until you approve.
That is a schedule. Nobody prompts it. It runs on Monday and the results wait. The agent's job is Tuesday: read what changed and say so. The person's job was two weeks ago, choosing the keywords. Choosing them is that decision; reading the rank tracker and writing three sentences is the agent's Tuesday.
What not to automate
Two things, and they are the two most people try first.
A process that is not written down. If a business has no clear process, automating it only automates a sloppy process. If you cannot write the steps down for a new hire, you cannot hand them to an agent. The agent will do something, confidently, and you will not know which step it invented.
The decision itself. An AI agent is not a self-driving car; you cannot let it drive itself. Whether you call yourself the driver or the dispatcher, there is a person in the loop at the moment a choice is made, and the systems that skip that person produce work that is fast and wrong.
One more thing to know about the market: a lot of what is sold as an "SEO agent" is a schedule and a prompt in a wrapper. That is fine, as long as you know that is what you bought and a person still reads the output.
Putting the three layers on SEO Scaler
Map the product to the layers and the plan writes itself.
| Layer | In SEO Scaler | Who acts |
|---|---|---|
| Schedule | Rank tracker (daily, weekly, monthly), the connected Search Console property | Nobody. It runs. |
| Agent | The MCP tools: read the tracker, read Search Console, bucket audit issues, pull competitors, draft the report | The assistant, with a person reading |
| Person | Which keywords, which pages, which competitors, what to build, what to tell the client | You |
The schedule layer uses credits per check, and the app shows the cost before you commit. The agent layer uses nothing for reads (Search Console, tracker results, audit results) and credits for research, again shown before anything runs. The person layer costs the most, which is the reason to keep it small and to give it good inputs.
Run this with the SEO Scaler MCP
Connect the SEO Scaler MCP. This prompt sets up the schedule layer once and defines the agent's weekly job; the person's job is answering the questions in step 1.
Using the SEO Scaler MCP on project [name]:
1. Ask me three questions and wait: which 20 to 40 keywords to
track, which device, and what day of the week I read reports.
2. Call get_rank_tracker. If a tracker exists for my domain, add the
keywords to it; otherwise create one: weekly, the device I named,
depth 40. Call estimate_rank_tracker_cost first and show me the
cost before adding anything.
3. Call run_site_audit if the last audit is older than 30 days, and
tell me when it will finish.
4. Write down, as a saved prompt I can paste every week: pull the
tracker results, bucket the movement (entered top 3, entered page
1, left page 1, unchanged), pull Search Console clicks for the
tracked pages this week versus last, and write three sentences.
5. Tell me which of the things you just did will run again without
me, which need me to paste the weekly prompt, and which need me to
decide something.Step 5 is the three layers, said back to you by the agent. If it puts a decision in the "runs without me" list, that is the grass.
Automate the schedule, read the agent, keep the decision
The tracker runs. The audit runs when asked. The agent reads them and writes the draft. You choose the keywords, read the draft and decide. The work that used to fill the week now fills an hour, and the hour is the part that was always worth paying for. Human in the loop content applies the same split to writing.
SEO automation FAQ
What SEO tasks can be automated?
Anything with a fixed input and output and no judgement: scheduled rank checks, Search Console pulls, site audits started on a fixed day, data exports. An agent can add a second layer, summarising and drafting from that data, as long as a person reads the result. Choosing what to track, what to build and what to tell a client stays with a person.
What is the difference between SEO automation and an AI SEO agent?
Automation runs the same job on a schedule with no model involved, like a weekly rank check. An agent takes variable input and produces structured output using a language model, like reading the check and writing the summary. Many products sold as agents are a schedule plus a prompt; that is useful, but it still needs a reader.
Can I automate SEO reporting?
The data collection, yes: the tracker and Search Console pulls run on their own and use no credits to read. The draft, yes, with an agent and a saved prompt. The sentence that says what it means for the business should still be written or at least read by a person before it goes out.
How much does scheduled rank tracking cost in SEO Scaler?
It depends on the number of keywords, the device and how often the check runs. The agent shows the credit cost before it runs, and nothing spends until you approve.
Should I automate content production?
Not end to end. The strategy on human in the loop content covers the split that works: a person writes the brief, the agent drafts, a person edits. Automating the brief or the edit produces content that reads like every other automated site.
Run this strategy in SEO Scaler
Run the MCP prompt in this guide with SEO Scaler. SEO Scaler is free to try, and asks before every paid call.