Each local area page used to take us half a day to create and optimize.
With SEOmatic, we can create hundreds of pages in the same time, which helps our clients make the best use of their budget.
It's transformed how we deliver scalable SEO solutions.
Will Hawkins
Marketing Director, Digi-Business UK
Agents read your Search Console data, do the work, and prove what actually moved. You decide what ships.
14-Day Free Trial. $1 today, credited to your first payment.
An agent holding a workspace key can read Search Console data, ask for insights, and (on paid plans) stage SEO changes. What runs without a person approving it is the workspace owner's choice, set with one of three autonomy modes.
| Scope | Lane | What it grants |
|---|---|---|
read:gsc | Free | Direct Search Console reads over REST. |
chat:ask | Free | Insight tools. Ask questions of your data. |
agents:act | Paid | Tools that stage changes. MCP acting: any paid plan. REST acting: Infrastructure. |
Every change an agent stages is prepared and queued first. The workspace's autonomy mode decides which of those changes need a person to approve them before anything is written to the CMS or site.
| Mode | What runs without an approval |
|---|---|
| Approval | Nothing runs until a person approves it. This is the default when no mode is set. |
| Assisted | Indexing checks and small reversible fixes run on their own: alt text, internal links, broken links, headings, FAQ blocks, social tags, schema markup, page speed attributes, and click-through fixes on pages already ranking. Campaigns and everything else wait for approval. |
| Auto | Everything Assisted runs, plus a campaign made only of those low-risk fixes can be approved automatically. |
Some work is never automatic in any mode: writing new content, merging pages, redirects, canonicals, noindex, robots.txt changes and content pruning always wait for a person. The per-change review and the protected-page rules apply in every mode, and an optional daily credit cap bounds unattended spend. Turning the agents off stops unattended work, including a campaign that is mid-run.
An automation that calls an approve step (decide_seo_task, n8n SEO Task > Approve) is that approval, so keep a person in that step.
Reads and insights are free on any plan. Acting (an agents:act tool) is paid, and the threshold depends on the surface: MCP acting works on any paid plan, while REST acting, including Zapier, n8n and Make, requires the Infrastructure plan. The same key can do both; the boundary is the surface the call arrives through.
The surface also decides how an AI visibility scan is paid for. Over REST, including Zapier, n8n and Make, a scan runs on the workspace's AI credits only: when they run short the call is refused with INSUFFICIENT_CREDITS (HTTP 402) and never spends a prepaid scan. An MCP agent, or the SEOmatic app itself, can fall back to a prepaid scan.
