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 Trial for $1, Credited to Your First Payment. Cancel Anytime.
The SEOmatic Slack app puts your SEO agents in the channel your team already reads. Approve SEO changes in Slack, read and apply held work, undo anything, run your agents, and ask SEOmatic about your sites in a DM. Every fact below comes from the shipped app: exact buttons, commands, limits and messages.
The owner of your SEOmatic organization finishes the install. Included on every plan. See what data the app uses.
SEOmatic agents find SEO fixes for your sites and stage them. By default every change waits for a person's yes. The Slack app brings those decisions, and the rest of SEOmatic, into Slack:
| You can | How |
|---|---|
| Decide every change | Approve or dismiss (with a reason) each change your agents stage, and approve or dismiss whole campaign plans. Changes that can remove pages from Google search are decided here too, behind a confirm step, by an owner or admin. |
| Review and apply held work | Read the exact staged change page by page, then apply it. Confirm a paste your site would not take from us. |
| Undo | Undo a live change, revert one that measured worse, undo all of a plan's changes, or undo everything your agent changed on a site. |
| Run plans | Pause, resume or stop a running campaign plan from its card. |
| Control your agents | Turn agents on or off per site, pick Approval, Assisted or Auto, plan now, set the daily AI credit cap and safety floors, choose what always asks first, and manage trust facts. |
| Change Slack settings | Default channel, a channel per site, one card per decision or a digest, the weekly report and mentions, from the app's Home tab. |
| Ask SEOmatic anything | In a DM, by mentioning @seomatic in any channel, in Slack's AI app panel, or with /seomatic ask. The same SEO Copilot as in SEOmatic answers from your data, privately to the person who asked unless the owner made that channel public, and anything that changes your site waits for your click. |
Each card updates in place as the work runs and replies in its thread with the outcome. There is no activity feed: the app posts decisions, answers you asked for, and an optional weekly report.
Linking your Slack account once, a change too long to show in Slack, and a site connection setting that blocks a change also open SEOmatic, each from a button.
A matching email address does not prove who clicked. Sign in with Slack does: Slack confirms the person in this browser is exactly that Slack user in that workspace. Deciding, asking SEOmatic, the agent panel, test cards and channel routing all need that link. Answers are your private data, so asking needs it too. A confirmed Slack email that matches your SEOmatic account only lets you see what is waiting on the Home tab and in /seomatic, with the link prompt next to it.
/invite @seomatic). SEOmatic does not post in a channel it cannot see, because it cannot check that the channel is private to your company.Every card has a title, the site, the change type and target page, why the agent proposes it, and one line saying what the decision does. The buttons depend on what the item needs now:
| Card | What it says | Buttons |
|---|---|---|
| Approval | A change your agent staged. "Staged by your SEO agent. Nothing ships until someone approves." | Approve, See the exact change (some change types), Dismiss..., View in SEOmatic |
| Approval that can remove a page from Google | A noindex, redirect, canonical, page merge or page removal. The card says exactly what happens and how to undo it, and "An owner or admin of your SEOmatic account approves this one." | Approve (confirm dialog), Dismiss..., View in SEOmatic |
| Campaign plan | "Approving the plan releases N tasks to your agents." A plan with index changes also counts them, for example "2 redirects, 1 noindex". | Approve plan (confirm dialog when it holds index changes), Dismiss plan... (confirm dialog), View in SEOmatic |
| Held work | Finished but not published: a safety guard or the reviewer held it, or your CMS cannot publish that field. The card shows the start of the exact change. | Review and apply, a fix link when a setting blocks it, Dismiss..., View in SEOmatic |
| Credit-paused work | "Paused: the workspace ran out of AI credits. Apply it now if your credits are back." | Apply now, Dismiss..., View in SEOmatic |
| Pull request | The change was delivered as a pull request on GitHub. Nothing changes on your site until you merge it there. | Open the pull request, Refresh the pull request (confirm, uses credits), Reconnect GitHub (when access was lost), Dismiss..., View in SEOmatic |
| Nothing to apply | Finished but not published, and running it again would not change that. | Dismiss..., Open in SEOmatic |
| Paste | Your site is not connected, or it would not take part of the change (an SEO title, a description, internal links), so it is yours to paste in. | Show what to paste, View in SEOmatic |
| Regression | "This change is measuring worse than before. Revert it here, or look at it in SEOmatic." | Revert (confirm dialog), View in SEOmatic |
| Paused plan | A quality gate paused a running campaign; the card gives the gate's reason. | Resume plan (confirm dialog), Stop plan (confirm dialog), View in SEOmatic |
| Running plan | An approved or active campaign. | Pause, Stop plan (confirm dialog), Undo all changes (confirm, when changes are live), View in SEOmatic |
| Live change | A settled change of ours that is live on your site. | Undo (confirm dialog), View in SEOmatic |
Dismiss... is a menu that records why in the same click: Dismiss: Wrong page, Dismiss: Not a priority, Dismiss: Don't touch this topic, Dismiss: Felt too risky, and Dismiss, no reason. View in SEOmatic opens the item on your plan board.
Anything that can remove a page from Google search, stop a plan, undo work or spend credits asks first, in Slack's own confirm dialog. Slack sends nothing when you press Cancel. Examples, with your page and numbers filled in:
| Button | Confirm text |
|---|---|
| Approve a noindex | This asks Google to drop /page from search results: the agent checks the page, then sets it to noindex. Undo: revert it from this card or in SEOmatic. Google can take weeks to show the page again. |
| Approve a redirect | This redirects /page permanently (301) to /destination. The exact rule comes back for you to review before it goes live. Undo: remove the rule. Google can take weeks to show the old page again. |
| Approve a plan with index changes | It releases N tasks to your agents. N can remove pages from Google search or send their traffic elsewhere: 2 redirects, 1 noindex. Each one can be reverted in SEOmatic, but Google can take weeks to follow. |
| Dismiss plan | The campaign is abandoned and none of its tasks will run. |
| Stop plan | The campaign is stopped and its remaining tasks are dismissed. Changes already live stay live; undo them separately if you want them gone. |
| Undo or Revert | SEOmatic restores what the page had before the agent's edit. If someone edited the page since, nothing is overwritten and you are asked first. |
| Undo anyway | The page was edited after the agent's change. Undoing now puts back what it had before the agent's edit and loses that newer edit. |
| Undo all changes (plan) | SEOmatic restores what N pages had before this plan's edits, up to 25 at a time. Pages removed from Google search can take weeks to come back. |
| See the exact change | The agent writes the new text now so you can read it before you decide. This uses about X to Y AI credits. Nothing changes on your site, and approving publishes exactly this text. (No confirm when a draft from the last 24 hours exists.) |
Canonicals, page merges and page removals get the same kind of text. A redirect, a merge and a page removal always come back as held work for you to review before they go live. If a plan gains index changes after its card was posted, approving it is refused and the card is refreshed so you see them before you confirm.
Decide in Slack or in SEOmatic and the card is updated in place, its buttons changed to match. Its thread follows the change, for example:
Approved by @person in Slack. Queued for the agent.
Applied. Measuring the result against the baseline until <date>.
Verified: <the measured win>.
Measured: no clear improvement over the baseline.
Measured: not enough data to call it.
Dismissed by @person in Slack (Not a priority).
Rolled back by @person in Slack. The page has what it had before the agent's edit.
The run hit an error. The agent will retry it.
Marked as pasted. Measuring the result from now on.Measured results come from the stored evidence, never an estimate. Who can click which button is in Permissions and roles.
Held work is finished work that did not publish: a safety guard or the reviewer held it, your CMS cannot publish that field on its own, or a redirect or merge came back for review. Click Review and applyon its card to open the review view, a Slack window showing the exact staged change in full: every field it sets, before and after, links written as text with their address in brackets, images as [image: alt text (address)], any code it adds to the page (scripts, styles, embeds) verbatim under "Code added to the page", and any other field as name and value.
For a proposed change, See the exact change on some cards drafts the new text before you decide, and shows it with Approve and Dismiss. Approving then publishes exactly that text.
Ask anything about your sites. The same SEO Copilot as in SEOmatic answers, with the same tools, memory and data: Search Console clicks and rankings, analytics, keyword data, page checks, AI search visibility and what your agents are doing. It can also write articles, run scans and prepare changes. Four ways in:
| Where | How | Sites and conversation | Who sees the answer |
|---|---|---|---|
| DM the app | Open SEOmatic in Slack and write in its Messages tab. | Any of your sites. One running conversation per DM; replies inline, or in the thread you asked in. | Only you |
| @seomatic in a channel | Mention @seomatic in any channel inside your company. | Any of your sites; a site whose cards go to that channel is offered first. One conversation per thread, per person. | Only you, in your DM with the app (the channel sees one short note), unless the owner made the channel public |
| Slack's AI app panel | Open SEOmatic in Slack's AI app split view. Suggested prompts appear, and a status line shows while it works. | Any of your sites. One conversation per panel thread. | Only you |
| /seomatic ask <question> | Type the command in any channel or DM. | Any of your sites. One running conversation per person per channel. | Only you (a private reply) |
When you have several sites, SEOmatic asks Which site is this about?with a button per site, and the conversation stays on that site. Every refusal (not linked, wrong role, limits, billing) is shown only to you. While it works, the reply shows what it is doing ("Reading your Search Console data...", "Checking AI search visibility...") and streams the answer in.
Mention @seomatic in any channel inside your company and the answer comes to you alone, in your DM with the app. The DM thread starts with "You asked in #channel: ...", and follow-ups from the same channel conversation go to that same DM thread for 30 days. The channel thread gets one line: "@you I answered you privately in our DM." Confirm buttons, cards and follow-ups all work in the DM. Channels shared with another company (Slack Connect) get no answer at all.
The organization owner can make one channel answer publicly, from the Home tab (Answer publicly in...) or /seomatic settingstyped in that channel. It is off by default and asks to confirm first: "Everyone in the channel, including guests, will see SEOmatic's answers about your sites: Search Console clicks, rankings, traffic and what your agents plan." Answers are public there only for a site whose cards go to that channel, and a public answer never uses workspace memory or other people's conversation summaries. Make private switches it back.
What is waiting on me in SEOmatic?
How did my Search Console clicks change this month?
What are the top SEO fixes for my site right now?
How visible is my site in ChatGPT and Google AI Overviews?
/seomatic ask Which pages lost clicks since last month?Reading runs right away, and so does proposing work (new tasks or a campaign plan), because a proposal still waits on its own card for someone to approve it. Everything else, meaning anything that changes your site, spends, or changes a setting, is only prepared: a message under the reply names it, with the task, plan, tracked prompt or trust fact it acts on by name, and a button to do it. Any tool not on the read-only or proposal list is treated this way. The button:
Approving or dismissing a task, and approving, pausing, resuming or stopping a plan, is never a separate button: SEOmatic posts that item's own card under the reply, so there is one way to decide anything. The other prepared actions (each may use AI credits, and the reply says so) are:
| Button | What it does |
|---|---|
| Write these articles / Save this article | Writes or saves articles for the site. |
| Run this AI visibility scan | Runs an AI search visibility scan. |
| Track this prompt / Update this tracked prompt / Stop tracking this prompt | Changes the prompts your AI visibility tracking watches. |
| Change how often scans run / Change which AI engines are scanned | Changes your AI visibility scan settings. |
| Update this plan | Changes a campaign plan (other than approve, pause, resume or stop, which use the plan's card). |
| Take this task | Claims a task for you. |
| Save this trust fact | Adds a trust fact your agent may use. |
| Save this dataset / Import this file as a dataset | Saves data to your workspace. |
| Send this to SEOmatic support | Sends your message to our support team. |
| Do this: <action> | Any other action that changes, spends or sets something. |
Asking costs what it costs in SEOmatic. A free account uses its free questions; when they run out, the reply offers Upgrade, a question pack and Invite a friend for more. A paid plan uses AI credits, and an organization whose plan is inactive gets the Open billing button instead of an answer. If a question fails to start, nothing is charged. See pricing.
Limits: 8 questions a minute and 80 an hour per person, 4,000 characters per message, one answer at a time per conversation. The same Copilot also works in Claude, ChatGPT and other assistants through the SEO MCP server (see AI assistants).
Every /seomatic reply is visible only to you.
| Command | What you get |
|---|---|
/seomatic ask <question> | Asks the SEO Copilot. The answer is visible only to you. With no question, it tells you what you can ask. |
/seomatic status | Where cards go, one card per decision or digest mode, whether the weekly report is on, and how many decisions are waiting. |
/seomatic pending | The top 5 decisions per connected organization, with the same buttons as the cards. |
/seomatic agent | Opens the agent panel: straight on your site when you have one, else the list of your sites. agents, autonomy, plan, facts and trust open it too. |
/seomatic settings | The Slack settings, privately. The organization owner can change them there, including Answer publicly in this channel for the channel it was typed in. Anyone else is told that only the owner changes them and that @mentions are answered privately by default. |
/seomatic help | The command list. Anything the command does not recognize shows it too: decisions are buttons, never typed commands. |
/seomatic ask What should we fix next on the blog?
/seomatic pending
/seomatic agentThe app's Home tab (open SEOmatic in Slack, then Home) answers "is SEOmatic connected, and what is waiting on me?" for each of your connected organizations:
| Part | What it shows | Who sees it |
|---|---|---|
| Connection | "Connected to #channel", one card per decision or digest mode, and whether the weekly report is on. When cards to the default channel are paused, it says why and how to fix it. | Everyone |
| Decisions waiting | The count and the top 5 decisions, each with the same buttons as its card. | Everyone (buttons need a linked account) |
| Your agents | Each of your sites with "Agents on, Assisted" or "Agents off" and a Manage button that opens the agent panel (up to 8 here; /seomatic agent lists every site). | Everyone with a role on the site |
| Slack settings | Default channel for cards, Group cards into a digest or Send one card per decision, the weekly report on or off, mentions on or off, and Answers when someone mentions @seomatic: private everywhere by default, with a picker to answer publicly in a channel and a Make private button per public channel. | Organization owner |
| Reinstall | On an install from before asking was available: Reinstall to enable asking SEOmatic. | Organization owner |
| Channel per site | A channel picker for each site (up to 8). Channels shared with another company are left out. | Owner or admin |
| Buttons | Open SEOmatic, Slack settings, Send a test card (owner or admin), Refresh. | Everyone |
Manage on the Home tab, or /seomatic agent, opens a site's agent panel. Each control calls the same function as the dashboard, behind the same role:
| Mode | What it means |
|---|---|
| Approval | Your agent suggests changes. Nothing goes live until someone approves each one. |
| Assisted | Quick wins like titles, alt text and internal links ship on their own. Anything bigger asks first. |
| Auto | Your agent finds the work and ships it for you, with a daily spend cap and a receipt for every change. New articles and changes that can remove pages from Google search still ask first. |
| Budget and safety field | Allowed values |
|---|---|
| Daily AI credit cap | A whole number from 1 to 1,000,000, or empty for the default cap. Work approved after the cap is reached waits until tomorrow. |
| AI search score: hold a page below | 0 to 100. |
| AI search score: warn below | 0 to 100, at or above the hold score. |
| Content score: hold a page below | 0 to 100. |
| Competitor pages needed to compare against | 1 to 20. |
| Always ask me before | Any of: Title & description rewrites, Page-one pushes, Image descriptions, Internal links, Broken link repairs, Social sharing previews, Page details for Google, Fixes to broken page details, Heading structure, FAQ sections, Article tune-ups, Page speed attributes, Indexing requests. These wait for approval in every mode. |
Slack never widens what someone may do. Every click passes three checks, in order: the person is a member of the connected Slack workspace with a linked account; their SEOmatic role on that site allows the action (the same rule as the dashboard); and the organization's plan is active. Anyone else is told why, and nothing changes.
| Action | Minimum SEOmatic role |
|---|---|
| See App Home, /seomatic status and /seomatic pending | Anyone on your SEOmatic team (a confirmed matching email is enough to read) |
| Ask SEOmatic, confirm what it prepared | Member, on that site |
| Read a held change in the review view | Any role on the site, viewer included |
| Approve or dismiss a change or a plan; See the exact change; I pasted it | Member |
| Approve a change or plan that can remove pages from Google search | Admin |
| Apply a held change, Apply now, Refresh the pull request | Member (admin when the change can remove a page from Google search) |
| Revert, Undo, Undo anyway, Undo all changes of a plan | Member |
| Pause or stop a plan | Member |
| Resume a plan | Member (admin when it includes changes that can remove pages from Google search) |
| Plan now | Member |
| Agents on or off, mode, budget and safety, trust facts | Admin |
| Undo everything on a site | Admin |
| Send a test card or set a channel per site from Slack | Admin |
| Default channel, card mode, weekly report, mentions, public answers in a channel | Organization owner |
| Install, disconnect, remove teammates' account links | Organization owner |
Roles go viewer, member, admin, owner; each includes the ones before it. Each person can unlink their own Slack account in SEOmatic under Settings, then Account.
The app asks Slack for 13 bot permissions. None of them reads channel history.
| Scope | Why SEOmatic needs it |
|---|---|
chat:write | Post cards and update them in place. |
chat:write.public | Post in a public channel the app never joined (a channel per site, Grid installs). |
incoming-webhook | The channel picker on Slack's install screen. |
users:read | Check that whoever clicks or asks is a member of your Slack workspace, not a guest from elsewhere. |
users:read.email | Suggest which SEOmatic account is theirs, and find the site owner to mention on urgent cards. |
commands | The /seomatic command. |
links:read | Notice links to app.seomatic.ai so they can get a preview. |
links:write | Show that preview. |
channels:read | Channel names, and checking that a channel is not shared with another company. |
groups:read | The same for private channels the app was invited to. |
app_mentions:read | Receive messages that mention @seomatic, to answer them. |
im:history | Receive the messages you send in a DM with the app, to answer them. |
assistant:write | Slack's AI app panel: the status line while it works and the suggested prompts. |
Linking an account uses Sign in with Slack with one user permission, openid, in its own flow. It tells SEOmatic only your Slack user ID and workspace ID; the sign-in token is revoked right away.
/seomatic commands, Home tab visits, the AI app panel opening, links to app.seomatic.ai, channel renames, and uninstalls. Bot messages, edits and deletions are ignored.| What | Limit |
|---|---|
| Questions | 8 a minute and 80 an hour, per person |
| Question length | 4,000 characters (longer text is cut) |
| Answers | One at a time per conversation |
| Private DM thread for a channel conversation | Reused for 30 days |
| Confirm button | Works once, only for the person who asked, for 30 minutes |
| Which site? buttons | Up to 20 sites, for 30 minutes |
| Connect or checkout follow-up | The thread hears about it for 24 hours |
| Link your Slack account | The link works once, for 10 minutes |
| Direct Install | 60 minutes to sign in and connect it |
| Undo all changes / Undo everything | 25 pages per batch |
| Digest | One message per burst of decisions, up to 20 items |
| Mentions | Urgent cards only, at most once every 6 hours per person |
| Shared-channel check | Remembered for up to 1 hour per channel |
| Review view | Up to 12 pages; longer changes are read and applied in SEOmatic |
| App Home | Top 5 decisions, up to 3 organizations, up to 8 sites |
| /seomatic pending | Top 5 decisions per organization |
| Trust facts | 20 shown in Slack; a scan reserves up to 4,000 AI credits |
The messages below are what the app says, in Slack or in SEOmatic.
| Message or symptom | Cause | Fix |
|---|---|---|
| Link your Slack account to SEOmatic once to approve or dismiss from Slack. | Deciding, asking and the agent panel need a Slack account proven with Sign in with Slack. | Click Link your Slack account and finish Sign in with Slack. The link works once and expires in 10 minutes. |
| Looks like you're you@company.com in SEOmatic. Link your Slack account... | Your confirmed Slack email matches a SEOmatic account, which is enough to read but not to decide. | Link once, as above. |
| Only members of the Slack workspace connected to SEOmatic can decide from Slack. | You are in another company's workspace (for example in a shared channel). | Decide in SEOmatic, or from the connected workspace. |
| Slack guests can decide from Slack only after linking their SEOmatic account. | Guest accounts are never recognized by email. | Link the account. |
| Slack did not say which workspace you are in, so SEOmatic cannot link your account from here. | Slack sent no workspace for your click (possible on some Enterprise Grid installs). | Open SEOmatic in Slack from your own workspace and try again, or decide it in SEOmatic. |
| Your SEOmatic role cannot approve or dismiss work on this site. | Your role on that site does not allow it (also: cannot roll back changes, cannot run the agent, cannot use the SEO Copilot). | Ask an owner or admin to change your role, or to decide. See Permissions and roles. |
| Only an owner or admin of your SEOmatic account can approve "...", the same rule as in SEOmatic, because it can remove a page from Google search. | Changes that can remove pages from Google need an owner or admin. | The message names who can approve it, with an @mention when they linked their Slack account. |
| You are not a member of this site in SEOmatic. | Your SEOmatic account has no role on that site. | Ask the organization owner to add you. |
| Your SEOmatic plan is inactive (the trial ended or billing lapsed), so decisions from Slack are paused. | Deciding from Slack needs an active plan, as in the dashboard. | Click Open billing. The thread tells you when the plan is active. |
| Start your SEOmatic plan to decide from Slack. | The organization has not started its plan yet. | Click Open billing. |
| Already approved, nothing to do. / Already decided by someone else, nothing to do. | Someone decided first, in Slack or SEOmatic. The card is refreshed. | Nothing. The card shows where it stands. |
| This change was updated since it was shown to you, so nothing was applied. | The held change moved on after you opened the review view. | The view reloads with the current version: read it, then apply it. |
| Nothing is waiting on this one any more: it was applied, dismissed or changed since. | The held change was decided elsewhere. | Nothing. Its card shows where it stands. |
| The page was edited after the agent's change, so undoing it now would overwrite that newer edit. Nothing was changed. | Someone edited the page after the agent did. | Click Undo anyway only if you want the page back to what it had before the agent's edit. |
| Daily agent credit cap reached | Today's agent spend reached the site's daily cap. | Wait for the reset, or raise the cap in Budget and safety settings. |
| Only the person who asked can confirm this. | Confirm buttons belong to whoever asked. | Ask SEOmatic yourself to do the same. |
| This button already ran, was cancelled or expired. | Confirm buttons work once and expire after 30 minutes. | Ask again. |
| That is a lot of questions in a short time. Give it a minute, then ask again. | More than 8 questions a minute or 80 an hour. | Wait a minute. |
| I am still answering your last question here. Ask again when it is done. | One answer at a time per conversation. | Wait for the answer, or ask in a new thread. |
| SEOmatic is busy right now, so nothing was run or charged. Try again in a minute. | SEOmatic could not safely check its limits or lock the conversation, so it stopped before running or charging anything. | Try again in a minute. |
| I could not open a private conversation with you. Send me a DM (the Messages tab of the SEOmatic app) and ask there. | A private answer to a channel mention goes to your DM with the app, and Slack did not let SEOmatic open it. | Ask in the app's Messages tab. |
| This channel is shared with another organization, so SEOmatic will not answer here. | Slack Connect channels are refused. | Send a DM instead. |
| You've used all N free questions this month. / Insufficient AI credits | Free questions or AI credits ran out. | Use the Upgrade, Add credits or question pack buttons under the message. |
| SEOmatic cannot see that channel. For a private channel, invite @seomatic to it first. | The app is not in that private channel, so it cannot check it or post there. | Type /invite @seomatic in the channel, then pick it again. (Also: "That channel is archived." and the Slack Connect refusal.) |
| Cards to the default channel are paused | The channel was archived or deleted, posting there was restricted, it became shared with another company, or the app cannot see it. | Pick a new default channel on the Home tab or in Settings, then Integrations. No reinstall needed. |
| This Slack workspace is not connected to SEOmatic. | No live connection for this workspace (disconnected, uninstalled or never installed). | The organization owner connects it from Settings, then Integrations. |
| You can now ask SEOmatic anything in Slack... To turn it on, the owner reinstalls the app once. | The workspace installed SEOmatic before asking was available, so Slack never granted app_mentions:read, im:history and assistant:write. /seomatic ask says this, the owner sees it on the Home tab, and a one-time note mentioning the installer goes to the card channel. | The organization owner clicks Reinstall to enable asking SEOmatic and allows the 3 new permissions. |
| Only the organization owner can install Slack. | Install errors come back to Settings, then Integrations. | Sign in as the owner. Other install errors: "The Slack authorization was cancelled.", "That install link was already used. Start again.", "Slack rejected the authorization. Try again.", "Slack did not return a channel. Pick a channel and try again." |
| This Slack install was not started in this browser | Direct Install finishes only in the browser that started it, within 60 minutes. | Start again from Settings, then Integrations, or from Add to Slack. |
| This Slack account is already linked to another SEOmatic account. | One Slack account links to one SEOmatic account. | Unlink it there first (Settings, then Account), then link it again. |
After a disconnect nothing more is posted, and your agents keep staging work in SEOmatic as before. Settings and history stay with your organization, so reconnecting picks up where you left off. To delete your Slack-related data sooner, email contact@seomatic.ai.
Yes. Approve on a noindex, redirect, canonical, page merge or page removal opens a confirmation that names the page, says what happens to it and how to undo it. Only an owner or admin of your SEOmatic account can approve it, the same rule as in SEOmatic. Anyone else is told who can, with an @mention when that person linked their Slack account.
No. The app has no permission to read channel history. Slack sends it only the direct messages you send to the app, messages that mention @seomatic, clicks on its own buttons, /seomatic commands, visits to its Home tab, links to app.seomatic.ai, channel renames and uninstalls. When you mention it in a channel, only your own message is read, never the rest of the channel.
A member of the connected Slack workspace who linked their Slack account once with Sign in with Slack, and whose SEOmatic role allows it on that site: member or above for ordinary changes, owner or admin for changes that can remove pages from Google search. The organization's plan must be active, as in the dashboard.
Yes. DM the app, mention @seomatic in any channel, open it in Slack's AI app panel, or type /seomatic ask followed by your question. The same SEO Copilot as in SEOmatic answers with your Search Console, analytics and AI search data, and it can write articles, run scans and prepare changes.
Not by default. When you mention @seomatic in a channel, the answer comes to you privately in your DM with the app, and the channel thread only gets a short note saying so. The organization owner can make a specific channel answer publicly, after a warning that everyone there, guests included, sees the answers. Public answers never draw on workspace memory or other people's conversations.
No. Only reading and proposing run straight away, and a proposal still waits on its card. Anything else is only prepared: a Confirm button under the reply names what it acts on, and only the person who asked can click it, once, within 30 minutes. Decisions on a task or plan come as that item's own card, with the same confirm steps as everywhere else.
The same as the SEO Copilot in SEOmatic: a free account uses its free questions, and a paid plan uses AI credits. Actions that use credits say so before you confirm, and a question that fails to start is not charged.
The card is updated in place and its buttons change to match, so nobody decides twice. Its thread follows the change: who decided and where, when it was applied, and the measured result from the stored evidence. A click on a stale button is refused with a short note, and nothing changes.
Yes. Owners and admins pick a channel per site on the app's Home tab, and the organization owner can also do it in SEOmatic under Settings, then Integrations. Sites without their own channel use the default channel. For a private channel, invite @seomatic first. Channels shared with another company are refused.
Private channels work once you invite @seomatic. Channels shared with another company through Slack Connect are refused for cards and answers, and every post checks again first. Ask in a DM instead.
Every plan, at no extra cost. The organization owner installs it. Deciding from Slack needs an active plan, as in the dashboard, and asking on a free account uses its free questions.
Once, if your workspace installed SEOmatic before asking was available. Asking needs three permissions added then (app_mentions:read, im:history and assistant:write). The owner sees a Reinstall to enable asking SEOmatic button on the app's Home tab, and /seomatic ask explains it. Settings, channel routes and linked accounts stay.
Disconnect Slack in SEOmatic under Settings, then Integrations, or remove the app from your Slack workspace. Either way the stored access token is deleted and nothing more is posted. Email contact@seomatic.ai to delete the rest sooner.
Email contact@seomatic.ai or use the contact form. No account needed, and a real person replies within one business day. To use SEOmatic from Claude, ChatGPT or Cursor, see the SEO MCP server; for plans, see pricing.