Key points
- Semrush published a guide to running SEO audits in Claude by connecting its MCP server to Site Audit, which checks for 140+ technical issues.
- Claude can read completed audits only. Starting new audits or changing settings still has to happen in the Semrush dashboard.
- Each Site Audit request through the MCP uses 100 to 10,000 API units; pulling a past audit costs 10,000. Eligible plans include 50,000 units.
- Claude can rank issues, suggest causes and fixes, and recommend whether SEO, content or development should own each one.
Why it matters for marketers: Marketers can turn Site Audit reports into prioritized, owner-assigned fix lists through plain-language prompts, but API unit costs and the read-only limit shape how often they can do it.
Semrush has published a step-by-step guide to running technical SEO audits inside Claude. The setup connects Semrush's Model Context Protocol server to a Claude account, so the assistant can read results from Site Audit, which scans a site for more than 140 technical issues, without anyone opening the Semrush dashboard.
The connection is read-only. Claude can list completed audits, summarize issue counts by severity, show affected pages and compare recent audits, but it cannot launch a new audit or change settings. Those steps stay in Semrush. Once data is in the chat, users can ask Claude to rank issues by impact and effort, explain likely causes, suggest fixes and say which team should own each one.
For content and SEO teams, the appeal is speed: a long audit report becomes a working to-do list with owners. Semrush also notes Claude can draft fixes such as missing meta descriptions, and can hand results to other connectors or skills, for example to build a Word report, post to Slack or email a team member through Gmail.
Cost is the main constraint. Each request uses API units, from 100 to 10,000 depending on type, and Semrush advises pulling past audits only when needed because each costs 10,000. Several plans include 50,000 units that reset at renewal, while others need an added API package.
Teams considering this workflow should check their plan's MCP access and unit balance first, make sure a recent audit exists, and decide which routine questions are worth the spend. A separate HubSpot guide compares Claude skills, plugins and MCP connectors, though its text was not available to us.
Sources
This brief is our own summary. Read the full reporting at the source.
