Semrush, without opening Semrush.
Backlinks, authority, and who you are actually up against.
- Free to start
- No card
- Reads only, nothing to approve
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Semrush details, and Ray takes it from there.
@Ray who links to our biggest competitor but not to us?
@Ray which of our pages bring in the most organic traffic?
@Ray what ad copy is our competitor running?
@Ray how does our authority score compare with theirs?
What Ray can and cannot do in Semrush
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
16 reads wired, and nothing that writes.
Runs on its own
What Ray reads in Semrush
- Backlinks, referring domains, anchors, and authority score
- Organic and paid competitors, and two domains compared head to head
- Which pages earn the traffic, the ad copy running, and how it moved over time
Reading changes nothing, so Ray never stops to ask whether it may look something up.
No send, no spend
What Ray answers with
Ray reads Semrush and answers from it in the thread. Writing to Semrush is not switched on yet, so there is nothing here to approve.
How Ray works with Semrush
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Semrush
Semrush has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Ray answers where you asked
Ray only reads Semrush, so there is nothing here to approve. It looks up what it needs and replies in the thread.
Priya
@Ray the checkout bug is back. Take a look in Semrush, and tell Dana it is being looked at.
Ray
Checked Semrush. The spec was last edited on Tuesday and the open question about refunds is still unanswered.
Ray uses Semrush together with the rest of your tools.
One ask can read Semrush, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Semrush to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Semrush and it can do the Semrush part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Semrush has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Semrush. Every write still stops for approval first.
Security and permissions
- You paste the Semrush key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Semrush in a message. Uninstall Ray and every connection it held is revoked.
Semrush and Ray, answered
The questions teams ask before they connect Semrush. Every answer is how this integration is built rather than a promise about it.
More marketing & ads integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Semrush.
Free to start, no credit card, and it asks before it acts.
By adding Ray, you accept the Terms and Privacy Policy.