the SEO lead
Numbers for a whole brief, in one call.
whyThe brief lists eighty keywords and no numbers.
asksGet volume, difficulty and intent for the brief's keywords.
instibrain / works with / semrush
Your AI reads Semrush on your seat, and knows what it models.
Semrush's own MCP server or web app, on a seat of the team's account. What each plan holds back is on this page.
team/tools/semrush/semrush.md plan, seat, projectasked · an exampleDid we lose the "invoice automation" ranking last week?
the AI, from the pageTracking shows 6 to 11. Search Console agrees: clicks are down by two. Real, and small.
who uses it, and why
Who asks Semrush, and what for.
Estimates and audits, checked against measured clicks.
the marketing lead
Where a competitor ranks above you.
whyA rival keeps taking the top spot.
asksWhich tracked keywords does our main competitor win?
a founder
Whether AI answers name you.
whyYou want to know if the AI tools mention you.
asksExport our AI visibility from the Semrush app.
what you can ask
Your AI reads positions and keyword data as far as your plan allows.
With API units, the MCP answers. Without them, the web app does the work.
Tracked positions
Positions, landing pages per keyword, and tracked competitors.
Keyword metrics in bulk
Volume, difficulty and intent, up to a hundred per call.
Site Audit and Position Tracking in the app
On every plan, with the seat's login.
Exports from the web app
CSV exports, and AI visibility, which the MCP lacks.
Free substitutes when it cannot answer
Trends, npm, PyPI, GitHub and Wikipedia, each with its caveat.
where the credential stays
OAuth on the seat's login.
Nothing of ours sits in between. No seat? Ask the account holder.
in Semrush
The official MCP server, signed in with OAuth, plus the web app. Without API units, only the final call fails. The browser tools still work.
in your brain
A page names the plan, seat, project and prompt set.
what instibrain never touches
Your AI checks a Semrush drop against Search Console first.
The seat is yours. Our server stores the plan and project page.
- A "lost" verdict on Semrush alone.
Search Console confirms a drop first.
- Placeholder data read as data.
Starter's cannibalization report is placeholders; Search Console answers instead.
- An absolute volume from Trends.
Trends is relative, checked against a control keyword.
the limits
Your AI cannot read every report on every Semrush plan.
What each plan gives, and what it holds back.
| Limit | What it means |
|---|---|
| API units are sold by plan | Without them, only the last call fails. |
| No AI-visibility reports over MCP | Read in the web app. |
| Cannibalization is Pro and up | Starter shows placeholders. |
| Keyword Analytics is not on Semrush One Starter | Every metric reads n/a; tracking and audits still work. |
before you connect it
Your AI signs in to Semrush with your own seat.
Does instibrain connect to Semrush?
No. Semrush's own MCP server signs in with OAuth on your seat.
Why check Search Console too?
Semrush models traffic. Search Console counts clicks.
What if the plan has no API units?
The web app's tracking, audits and exports still work.
Your AI keeps Semrush's estimates apart from measured clicks.
Name the plan, seat and project. Every AI knows which number is which.