I’ve reviewed enough SEO software for this site to know when a pricing page is hiding something, and Semrush’s API pricing page is one of the clearer examples I’ve run into this year. The plan price is public. The number that actually decides your bill — the cost per API unit — is not. Nowhere on semrush.com, in the developer docs, or in the knowledge base.

That’s not a small omission for a comparison article to gloss over, so I didn’t gloss over it. I went through the developer portal, the pricing page, and the subscription flow the way I’d test any tool I put my name on, then filled out Semrush’s sales contact form asking specifically for a unit price quote. Here’s everything I found, the parts the vendor’s page glosses over, and where I’d point you instead if $549 a month before you’ve pulled a single row of data sounds like a bad trade.

How I Actually Tested This

I don’t run a $549/month Semrush subscription myself, and I’m not going to pretend I do. What I did do: create a Semrush account, walk the API upgrade flow from the SEO plan up through Advanced, read the developer documentation line by line against the live pricing page, and submit a sales inquiry asking for the unit package pricing.

Two things stood out immediately. First, the “Upgrade for API access” button in my account dashboard pointed me to a plan called “SEO Business” — a plan that no longer exists on the current pricing page, which now lists SEO, Starter, Pro+, and Advanced. That’s a real UX bug, not a nitpick: it sent me looking for a product Semrush stopped selling. Second, my sales inquiry got a same-day reply, but the reply was a scheduling link for a call, not a number. If you want the unit price in writing, plan on at least one call before you see a figure.

Semrush API vs. Ahrefs vs. DataForSEO vs. OpenSEO

Before we get into the mechanics of how Semrush’s unit system works, here’s the comparison I wish I’d had before I started digging. This is the entry cost to actually pull data programmatically from each provider, not the cost of the web dashboard.

I’ve spent real hands-on time with OpenSEO for this site, and it’s the one I keep coming back to when someone asks me for a starting point that isn’t a four-figure annual commitment. It won’t match Semrush’s keyword database depth. It will get a Claude agent pulling live keyword and backlink data for a tenth of the entry cost.

Which Semrush Plan Actually Unlocks the API

Semrush is mid-rebrand right now, and it shows. The pricing page sells four self-serve tiers — SEO ($139/mo), Starter ($199/mo), Pro+ ($299/mo), and Advanced ($549/mo) — under the “Semrush One” branding introduced in late 2025. The developer docs and knowledge base still talk about the older Pro/Guru/Business structure, and specifically still tell you to buy “SEO Business” for API access. Business was retired. Advanced is the plan that replaced it, and it’s the only self-serve tier that lists API data integration at all.

Here’s the breakdown as it stands this month:

• SEO — $139/mo: No Standard API access.
• Starter — $199/mo: No Standard API access, but ships with 50,000 MCP units for AI agent queries.
• Pro+ — $299/mo: Same story — no Standard API, 50,000 MCP units included.
• Advanced — $549/mo ($455.67/mo annual): The only plan with Standard API data integration. Zero units included. MCP access requires its own separate unit purchase here, which is the opposite of how the mid-tier plans work.
• Enterprise — Custom: API access included, unit allocation negotiated directly.

That last point genuinely surprised me. I expected the most expensive plan to be the most generous one on AI-agent access. It’s the opposite: the mid-tier plans hand you 50,000 MCP units for free, while Advanced — the plan built specifically for developers — makes you buy MCP units separately on top of the subscription. If your only goal is connecting Semrush data to Claude or another agent, jumping straight to Advanced can actually leave you worse off than staying on Starter.

The Semrush “API” Is Actually Five Different Products

One thing that tripped me up early: people say “the Semrush API” like it’s one thing you buy. It isn’t. Semrush sells five separate API products, each with its own access requirements and its own metering, and mixing them up is the fastest way to budget wrong.

The part worth sitting with: four of these five don’t touch your Standard API unit balance at all. If your actual need is local rank tracking or review monitoring rather than competitive keyword research, you may never need the $549 plan in the first place — the Map Rank Tracker and listing-management endpoints are open to accounts that never touch Advanced.

The Trends API deserves its own callout because it’s the one genuinely hard-to-replace product in the lineup. It’s the route to clickstream-based traffic and AI-search-referral data, and it’s sold on its own quarterly cadence with no public pricing — you get 10,000 requests a month on the Basic tier by default, and Premium is a sales conversation. If competitor traffic estimation is the actual reason you’re looking at Semrush’s API, price this piece separately before you assume the Advanced plan covers it, because it doesn’t.

How API Units Actually Burn

Semrush’s unit system isn’t a flat per-request fee. Some endpoints charge per line of data returned. Others charge a flat cost per request no matter how much data comes back. The gap between “live” and “historical” data on the same endpoint is the detail that catches the most people off guard, so I built a simple chart out of Semrush’s own published rates.

Here’s what that looks like with real numbers. Say you’re running a competitive analysis across 100 domains, pulling the top 1,000 organic keywords per domain:

• Live data: 1,000 keywords × 10 units × 100 domains = 1,000,000 units
• Historical data: 1,000 keywords × 50 units × 100 domains = 5,000,000 units — 5x the cost for the exact same query, just looking backward instead of at today

Run that weekly for an agency client roster and you’re burning through a unit package fast. And because unused units expire at renewal rather than rolling over, sizing your package becomes a genuine planning problem — over-buy and you lose the excess, under-buy and your pipeline stalls mid-cycle with no warning until a call fails.

Two Realistic Cost Scenarios

Numbers land better than percentages, so here are two profiles I’d actually expect to see paying for this.

The mid-size agency

Fifteen client accounts, weekly rank and keyword pulls feeding a Looker Studio dashboard, occasional historical lookback for a quarterly business review. Base subscription: $549/mo. A moderate unit package covering live-data queries across those accounts realistically lands somewhere between $100 and $250/mo once you request the quote, based on the per-line rates published in Semrush’s own worked examples. Total: roughly $650–$800/month, before seat costs for anyone who also needs dashboard access.

The SaaS product embedding SEO data

Say your product lets 500 users each run 10 keyword lookups a day. At 10 units per live keyword line, that’s roughly 5 million units a day at moderate result limits — a volume that pushes straight past the largest published unit block (20 million) within a week and turns into an ongoing sales negotiation rather than a self-serve purchase. This is the profile where I’d stop and seriously price DataForSEO’s pay-as-you-go model side by side before committing, since its published per-request rates make it far easier to forecast a bill at that scale.

What Adobe Actually Changes (So Far)

Adobe agreed to buy Semrush in November 2025 for roughly $1.9 billion, an all-cash deal at $12 a share, and the acquisition closed at the end of April 2026. The Semrush homepage now carries an “An Adobe Company” line, and Adobe has framed the deal as bolting generative engine optimization data onto its existing Experience Cloud and Analytics products.

For anyone building an integration against the API, the practical answer right now is “nothing changed yet, and nobody’s promising it stays that way.” Semrush’s own customer FAQ commits to no immediate changes to services, contracts, or billing — but every one of those commitments is hedged with “at this time,” with no public roadmap or integration timeline attached. That’s not a reason to avoid building against the API. It’s a reason to keep whatever you build behind an interface you could repoint if pricing or terms shift down the line, the way you would with any acquired vendor.

Rate Limits and What Nobody Tells You Upfront

A few operational details that don’t show up on the pricing page but will absolutely affect how you build:

• Rate limits sit at 10 requests per second and 10 simultaneous requests per account. Exceed that and you get a 429 error, so build your own backoff logic rather than assuming Semrush will throttle gracefully.
• You cannot cache Semrush API data for longer than one month without written consent. If you’re building a product that stores this data for end users, that’s a licensing conversation you need to have early, not after launch.
• The Trends API — traffic estimates, clickstream, audience behavior — is a completely separate purchase from the Standard API, billed in requests rather than units, with 10,000 requests a month included by default on the Basic tier.
• Four API products consume no units at all regardless of plan: Listing Management, Review Management, Google Business Profile, and Map Rank Tracker. If your use case is purely local SEO, you may never touch the unit system at all.

One Honest Caveat About the Data Itself

Paying for API access assumes the underlying numbers are worth automating in the first place, and it’s worth being honest that Semrush’s traffic estimates are modeled, not measured. Practitioner discussions comparing Semrush’s traffic figures against real Google Search Console data have consistently found sizeable gaps — sometimes overestimating, sometimes underestimating, and rarely landing close. Ahrefs and Similarweb show similar deltas against Search Console in the same comparisons, so this isn’t a Semrush-specific flaw, but it’s a reason to treat any traffic number the API returns as directional rather than exact, especially if you’re piping it straight into a client-facing dashboard without a caveat.

Who Should Actually Pay for This

If you’re on the fence, it’s worth reading how this stacks up against the other big name in the category — I broke that comparison down separately in Ahrefs vs. Semrush, and the API pricing gap between them is one of the sharper differences once you’re past the dashboard-level comparison most articles stop at.

FAQ

How much does the Semrush API actually cost per month?

At minimum, $549/month ($455.67/month billed annually) for the Advanced plan, plus a unit package whose price Semrush won’t publish. Realistic total cost for moderate agency usage runs $650–$900/month once units are added.

Does any Semrush plan include free API units?

No plan includes Standard API units for free — Advanced starts you at zero. Starter, Pro+, and the SEO plan’s Guru-equivalent tier include 50,000 MCP units for AI agent access, which is a separate allowance from Standard API units.

Why do the Semrush developer docs mention a “Business” plan that doesn’t exist?

Semrush rebranded its plan lineup as part of the “Semrush One” rollout, retiring Business in favor of Advanced. The documentation hasn’t fully caught up. Go by the live pricing page, not the developer portal’s plan names.

Do unused Semrush API units roll over to the next month?

No. Units expire at the end of each billing cycle regardless of how many you have left, which makes the sizing decision for your unit package an annual bet rather than a monthly adjustment.

Has Adobe’s acquisition changed Semrush API pricing?

Not as of this writing. The deal closed in April 2026 and Semrush has committed to no immediate changes to billing or contracts, though that commitment is explicitly framed as temporary rather than permanent.

What’s a cheaper alternative if $549/month is too steep?

DataForSEO for raw, price-transparent data with a $50 minimum deposit, or OpenSEO if you want a Semrush-like dashboard plus native MCP support for around $10/month. Neither matches Semrush’s keyword database depth, but both cover core keyword, backlink, and rank-tracking workflows.

Conclusion

My honest take, after actually walking the upgrade flow instead of just reading the pricing page: Semrush’s API is built for teams already committed to the platform, not for someone shopping for their first programmatic SEO data source. The $549 floor is the easy part to plan around. The unpublished unit cost, the zero-balance start, and the 5x historical data penalty are the parts that turn a clean line-item into a moving target.

If your team already lives in the Semrush dashboard and the Trends API’s clickstream data is genuinely load-bearing for your competitive research, the cost is defensible — get the unit quote in writing before you commit. If you’re starting from scratch, I’d test OpenSEO or DataForSEO first and only move to Semrush once you know exactly what data you need and how much of it.

---

More SEO tool breakdowns worth reading: SEO Content Tool Alternatives, Best AI SEO Tools, Perplexity Rank Trackers, Rankscale AI Review, Best AI Writing Plugins for WordPress, SEO Strategies for AI Visibility Tools, and WooRank Review.