New: the hosted MCP server is live. Connect your agent in one command.Read the docs →
StackResolve logoStackResolve

Compare

Ahrefs vs Semrush

Ahrefs scores higher on the AgentReady, 83/100 against 46/100. They differ on 13 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Ahrefs. Ahrefs is an AI marketing platform built on a proprietary index of the web that provides tools and data to grow brand traffic, visibility, and revenue in search, AI, and beyond.

Semrush. The leading platform to grow and measure brand visibility across every digital channel.

Where Ahrefs is ahead

Ahrefs passes public docs discoverable, and Semrush does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented and limits / constraints documented. Semrush misses those.

And on adopt, no mandatory sales call, programmatic credential creation and official python sdk. Semrush misses those.

Finally, on operate, structured, predictable output, machine-readable errors and observable execution. Semrush misses those.

What neither does

Both fail llms-full.txt / full agent docs, authentication documented, fast time to first request, copyable quickstart, cli available, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. Ahrefs leads 93 to 80. Ahrefs misses llms-full.txt / full agent docs; Semrush misses public docs discoverable, llms-full.txt / full agent docs.

Understand is whether an agent can read the docs and work out how the API behaves before calling it. Ahrefs leads 92 to 23. Ahrefs misses authentication documented; Semrush misses structured api reference, openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Ahrefs leads 85 to 55. Ahrefs misses fast time to first request, copyable quickstart, cli available; Semrush misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official python sdk, cli available.

Operate. Ahrefs leads 61 to 24. Ahrefs misses retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Semrush misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.

Pricing

Ahrefs does not publish a machine-readable starting price and has a free tier. Semrush does not publish one with no free tier.

Signal by signal

SignalAhrefsSemrush
AgentReady8346
Discovery9380
Understanding9223
Adoption8555
Operability6124
Public APIYesYes
MCP serverYesYes
OpenAPI specYesUnknown
CLIUnknownUnknown
llms.txtYesYes
Self-serve signupYesYes
Free tierYesNo

Which to pick

Ahrefs clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Ahrefs and Semrush. Alternatives to each: Ahrefs, Semrush.

An agent can fetch this as data: POST /v1/compare {"slugs": ["ahrefs", "semrush"]}