Make.com SEO Automation: Run SEO Tools in Scenarios

The SEOmatic app for Make has four modules. It calls the SEOmatic REST API with your API key, so every tool your key can use is available in a scenario.

• A SEOmatic workspace on the Infrastructure plan (Enterprise includes it too), for every module.
• A SEOmatic API key. Read-only by default; tools that make changes need a key created with Allow this key to make changes.
• A Make account.
• For Search Console tools (like the first scenario below): Google Search Console connected in SEOmatic.

The app is published by invite link, not listed in Make's app directory. Open the link while signed in to Make and install it in your organization:

https://www.make.com/en/hq/app-invitation/55fd46a2daac3c6a9c33c73637a8351e

Open the SEOmatic app in Make

1. Sign in at app.seomatic.ai and open Settings > AI Agents > API Keys.
2. Name the key (for example Make) and click Create key.
3. Copy it right away. It starts with smk_ and is shown once.

New keys are read-only: they read your data and run analysis tools. Tick Allow this key to make changes only if the scenario needs tools that change your site. That option needs a live subscription or trial, and edits made this way are staged in SEOmatic for your approval.

1. Add any SEOmatic module to a scenario and click Create a connection.
2. Paste the API key and click Save.
3. Make checks the key against GET /v1/me. A wrong key or a workspace that is not on Infrastructure fails here, with the reason.

The connection list shows your workspace name followed by (read-only) or (can make changes), so you can tell keys apart. Every request the app sends carries:

Authorization: Bearer smk_...
X-Seomatic-Client: make

Pull your top Search Console queries into Make:

1. Add SEOmatic > Run a tool and pick your connection.
2. Fill in the two fields below.
3. Click Run once.

Tool        get_search_queries
Arguments   {"days": 28, "limit": 10}

The module outputs three fields. Resultis the tool's output parsed into fields; numbers below are examples:

Tool         get_search_queries
Result       {
               "siteUrl": "sc-domain:example.com",
               "period": "Last 28 days",
               "totalResults": 10,
               "queries": [
                 { "query": "seo agent for wordpress", "clicks": 42,
                   "impressions": 1310, "ctr": "3.2%", "position": "7.4" }
               ]
             }
Raw result   the same output as JSON text

Next, add an Iterator on Result: queries and send each row to Google Sheets or Slack. Search Console tools need Search Console connected in SEOmatic.

Run a tool

List tools

Returns one bundle per tool, up to Limit(default 200). Use it to find a tool's name and its arguments.

Make an API call

Calls any endpoint in the REST API reference. Enter the path after https://app.seomatic.ai/api; the connection adds authorization for you. Put query parameters in Query string, not in the URL.

URL      /v1/me
Method   GET

The output has the response Body, Headers and Status code.

Watch Events

1. Add SEOmatic > Watch Events as the first module of a scenario.
2. Click Create a webhook, pick the connection and one Event. Saving subscribes it in SEOmatic; deleting the webhook unsubscribes it. Add one Watch Events webhook per event you want to listen to.
3. Each event arrives as one bundle: Event, Event ID (the same on a retried delivery, so you can skip repeats), Workspace ID, Created At, Cursor and Data, with the fields of the event you picked.

The connection's API key needs the admin role in the workspace, because a subscription is a webhook. It needs the Infrastructure plan, and a workspace holds up to 25 webhooks and triggers in total.

Copy a tool name into Tool and the JSON into Arguments. The REST API reference lists every tool and argument.

• The Make app needs the Infrastructure plan (or Enterprise), like the Zapier and n8n integrations: Launch, Scale and trials do not include it. That covers read tools, tools that make changes and Watch Events.
• Tools that make changes also need a key created with Allow this key to make changes. A read-only key never sees them in the list.
• Scenarios never spend prepaid scans.If the workspace's AI credits cannot cover a new AI visibility scan, no scan starts and the call is refused with INSUFFICIENT_CREDITS (HTTP 402).
• Rate limits are per key: 60 tool runs per minute and 1,000 per hour, and 500 requests per minute for other endpoints. See rate limits.
• A tool answers within 60 seconds. A slower one returns 504 TOOL_TIMEOUT and keeps running (see Errors and fixes).

Plans and prices: pricing.

Error messages show SEOmatic's error text and code, never your key.

insufficient_credits is not an error. When the workspace's AI credits cannot cover run_ai_visibility_scan, no scan starts and the module outputs a normal bundle with Result: status = insufficient_credits. Check status before using the result, for example with a filter. Add credits, or run the scan from the SEOmatic app; get_ai_visibility still reads the last scan for free.

• The API key is stored in a password field: masked when you type it, hidden when you edit the connection.
• The Authorization header is removed from Make's logs.
• Every request goes over HTTPS to app.seomatic.ai. Make an API call only accepts paths like /v1/..., so it cannot send your key to another host.
• If an AI agent or AI module picks the tool or its arguments, use a read-only key. An AI agent can be steered by text it reads (prompt injection). With a read-only key it can read your SEO data but never approve or apply a change.
• Revoke a key any time in Settings > AI Agents > API Keys.

• Zapier and n8n SEO automation: the same workspace in other automation platforms, with event triggers.
• SEO MCP server: the same tools inside Claude, ChatGPT and Cursor.
• SEO API: every endpoint and tool the app can call.
• Webhooks: signed events for your own endpoints.
• Quickstart: your first API call with curl.