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 card check, refunded. Cancel Anytime.
Wire SEOmatic into the apps you already use, no code. Triggers fire your Zaps on SEOmatic events, searches let a Zap or an AI agent ask SEOmatic anything, and actions let it act on your site.
On Zapier, an integration's searches and actions are the tools exposed to AI agents, so SEOmatic works as a full agent inside Zapier MCP, Zapier Agents, and AI Actions, not only as a set of webhooks. A Zap, or an agent driving Zapier, can query Search Console, compare periods, read backlinks, check indexing, and then propose fixes or whole campaigns, all in one workflow. The integration exposes 49 searches across every SEO data source and the agent's own state, and 8 actions, plus 5 event triggers.
Every step authenticates with your workspace API key, sent as a Bearer token, and hits the SEOmatic API directly. A trigger subscribes a Zap to an event; a search runs a read and returns mappable fields; an action performs a change, which SEOmatic keeps proposal-based and approval-gated. A typical Zap chains all three:
Trigger ai_visibility.scan_completed (a scan just finished) ↓ Search Get query-page matrix (find cannibalized queries) ↓ Action Create SEO tasks (propose fixes, approval-gated) ↓ Send to Slack / email / a sheet (any of Zapier's 8,000 apps)
Add SEOmatic in Zapier, paste a workspace API key, and you are connected. The key is tested against a Scale-gated endpoint, so a key on a lower plan fails at connect time with a clear message instead of building Zaps that error later.
| Setting | Value |
|---|---|
| Auth type | API key (Bearer token) |
| Key | smk_live_… (workspace API key) |
| Where to mint | Settings, AI Agents, API Keys |
| Tested against | GET /api/v1/zapier/me |
| Minimum plan to connect | Scale |
A trigger subscribes a Zap to a SEOmatic event as a REST-hook: when the event fires, your Zap runs. Each trigger reuses the same signed, retried delivery pipeline as first-class webhooks. Available on the Scale plan and above.
| Trigger | Event | Fires when |
|---|---|---|
| New published page | page.published | A page goes live on your site. |
| Page publish failed | page.publish_failed | A publish attempt fails, so a Zap can alert or retry. |
| Task completed | task.completed | An SEO agent task finishes. |
| Campaign completed | campaign.completed | A bulk-page or content campaign finishes. |
| Scan completed | ai_visibility.scan_completed | An AI-visibility scan finishes. |
A search looks something up in SEOmatic and returns fields you can map into any downstream step. There is a search for every SEO data source, so a Zap, or an AI agent, can pull exactly the numbers it needs mid-workflow. Searches over your data sources are read-only and available on the Scale plan and above.
| Category | Searches | Examples |
|---|---|---|
| Search Console | 8 | get_search_queries, get_top_pages, get_dimension_breakdown |
| Keywords | 6 | get_keyword_metrics, get_keyword_suggestions, compare_keywords |
| Backlinks | 4 | get_backlink_summary, get_backlink_anchors, get_backlink_velocity |
| SERP & competitors | 4 | get_serp_features, get_domain_rankings, get_domain_overview |
| Analytics & Ads | 7 | get_traffic_overview, get_traffic_sources, get_landing_pages |
| Local (Business Profile) | 3 | list_business_locations, get_local_visibility, get_business_reviews |
| Datasets & templates | 4 | list_datasets, get_dataset_rows, list_page_templates |
| Site & pages | 2 | analyze_page_seo, crawl_page |
A further 11searches read the agent's own state (SEO tasks, campaigns, strategy, signals, content scores). Those run on the Infrastructure plan, the same line as actions, because they read the agent's working memory rather than a raw data source.
An action lets a Zap do something in SEOmatic. Because actions change your site, they require the Infrastructure plan, and every action that touches your content is proposal-based and approval-gated: SEOmatic drafts the work, a human approves it. Nothing is applied silently.
| Action | What it does |
|---|---|
| Submit URL for indexing | Pings Google and IndexMeNow to recrawl a URL now. |
| Create SEO tasks | Stage up to 5 SEO tasks in the agent's plan as PROPOSALS. This NEVER executes anything: each staged task renders a card where the user approves and optionally runs it through the agent's gated pipeli… |
| Manage campaign | Pause, resume, update the brief of, or abandon one of the agent's campaigns ON THE USER'S BEHALF: never send the user to the dashboard for these. pause: holds execution, tasks keep their status. resu… |
| Propose page-scale campaign | Stage a landing-pages-AT-SCALE campaign (programmatic SEO: e.g. "a page for each of the 50 US states", "X vs Y comparison pages"): up to 500 pages generated from ONE agent-authored template + a datas… |
| Propose content sweep | Stage a CONTENT SWEEP as a managed CAMPAIGN: N DISTINCT blog articles on N different topics, tracked on the agent board with a planning phase. Up to 50 topics, batched into ONE run of the blog pipeli… |
| Create bulk-edit campaign | Stage ONE bulk sweep campaign that applies an instruction across MANY pages (e.g. "rewrite every meta title to include the current year", "add alt text to all images sitewide"): up to 500 pages, one… |
| Write blog articles | The DIRECT path for "write N blog articles": validates FIRST, then stages ONE approval card in this chat. Use this by DEFAULT when the user asks for multiple articles (2-50 topics): it is the fast, s… |
| Save blog article | Save an article you drafted IN this conversation so the user can publish it with one click. ONLY for inline drafting: when the user explicitly wants to read/iterate on the draft here in chat. For "wr… |
The Zapier boundary mirrors the rest of the platform: reading is broadly available, acting is the paid line.
| Capability | Requires |
|---|---|
| Triggers (fire a Zap on an event) | Scale |
| Searches over your SEO data sources | Scale |
| Searches over agent state (tasks, strategy, signals) | Infrastructure |
| Actions (act on your site) | Infrastructure |
