Semrush shared access limits come from two layers: the total quota set by Semrush's official subscription for upstream accounts, and the final access rules set by RelayX for node users. Looking only at "Guru" or "Business" names, you cannot know how many queries a user can make per day, how many rows they can export, or which projects they can save.

This article provides item-by-item verification methods. For accurate RelayX entitlements, refer to the product page, checkout page, and post-login console on the day of purchase; this article does not write dynamic quotas as long-term commitments.

First, distinguish six types of "limits"​

Limit What it controls Common misinterpretation
Query frequency How many report requests can be initiated in a period Mistaken for report result row count
Report results Maximum rows returned in one table Mistaken for daily query count
Export quota Whether downloadable, format, single/daily row limits Assuming visible means fully downloadable
Project quota Number of Site Audit, Tracking, and other projects Assuming node projects are permanently private
Crawl/Track Monthly crawled pages and keywords Mixed up with Domain queries
Device/Session Device count, concurrency, node validity period Bypassing via Cookie copying

Use accurate terms from the table when submitting pre-sales questions to avoid receiving unverifiable answers like "quota is very high."

Official package quotas are the upstream total pool​

As of August 2026, Semrush's official knowledge base lists typical SEO Classic values including:

Official Plan Single report results Monthly crawled pages Tracked keywords Monitored websites
Pro 10,000 100,000 500 5
Guru 30,000 300,000 1,500 15
Business 50,000 1,000,000 5,000 40

Different modules also have daily reports, keyword lists, backlinks, audits, exports, and additional tool limits. Official numbers are subject to change; open the current knowledge base to confirm.

Node users do not automatically exclusively enjoy the upstream total pool. If multiple sessions share the same resources, RelayX may set lower daily frequency or disable high-risk features to maintain overall availability.

How query counts are consumed​

Opening Domain Overview once, switching country databases, modifying domain scope, or applying filters may each trigger report requests. A single frontend click may also request multiple components, so "click count" and backend metering are not necessarily the same.

Efficient usage methods:

  1. List domains, countries, and scope before entering;
  2. Query similar domains in batches to reduce back-and-forth switching;
  3. Check overview first, confirm it's worth diving deeper before opening sub-reports;
  4. Wait for the reset time indicated on the page after reaching limits, don't refresh repeatedly;
  5. Record error message originals to distinguish between node limits and Semrush official limits.

Do not use auto-refresh, script concurrency, or session copying to bypass frequency limits. This may rapidly consume upstream resources and trigger security controls.

Report results and exports​

A web display limit of 30,000 rows does not mean every node allows exporting 30,000 rows. Exports may also be controlled by format, module, user permissions, single-session row count, and daily frequency.

Before purchasing, verify at least one real deliverable:

  • Whether Organic Research can show the needed first N rows;
  • Whether Keyword Gap can be exported after filtering;
  • Whether Backlink Gap exports domain-level or link-level records;
  • Whether Site Audit can export issues and URLs;
  • Whether PDF, CSV, and XLSX are separately available.

If the task only requires 200 filtered keywords, don't waste time exporting tens of thousands of rows. First filter by intent, region, difficulty, and brand terms on the page, then download actionable results.

Projects, audits, and rank tracking​

Project-type features save domains, keywords, crawl rules, and history. Three boundaries exist in nodes:

  1. Upstream accounts have project limits and total crawl quotas;
  2. Other users may occupy resources;
  3. When nodes are replaced, reclaimed, or service ends, project continuity cannot be assumed.

Therefore, only create public, low-sensitivity, rebuildable temporary projects in nodes. When weekly continuous ranking, multi-region devices, team collaboration, GA4/GSC connections, or client audits are needed, use official standalone accounts or formal team seats.

Site Audit exports are suitable for one-time technical checks, but fix history and tickets should be saved in your own project system. Position Tracking's value lies in continuous time series; if the same project cannot be guaranteed long-term, short-term node benefits will diminish.

API & Automation ​

Web access to Business features does not mean users obtain API keys. API requires official authorization, interface scope, and call quotas, and involves credentials and automation rules. When RelayX node pages do not explicitly state API, do not include it in deliverables by default.

Bulk crawling, bot clicks, or bypassing page limits are not equivalent to API. When integrating Semrush data into warehouses or BI, verify official Business/API terms and purchase corresponding plans.

Devices, Browsers & Concurrency ​

Nodes are typically bound to certain devices or browser environments. Switching devices, frequently changing IPs, opening multiple nodes simultaneously, or copying cookies may cause session failures. The correct workflow is: enter via RelayX console, install extensions as instructed, operate within allowed device counts, and exit normally.

When two colleagues need to work simultaneously, do not have them share the same node session. Include official additional users or multiple compliant access solutions in your budget. Semrush official additional users have independent credentials but share subscription quotas.

Data & Privacy Boundaries ​

Suitable for node input: public domains, public keywords, public URLs, rebuildable filter conditions. Avoid: client site verification, Analytics/Search Console connections, private keyword plans, contact files, API keys, and payment information.

After export, place CSVs in your own controlled storage and delete unnecessary temporary projects. Do not write unpublished client or product information in project names.

Task Fit Table ​

Task Node Fit Recommendation
One-time check of 5 competitor domains High Unify country and scope first
Filter 200 content keywords High Filter on page before export
Quarterly backlink gap Medium to High Maintain list locally after export
Weekly tracking of 2,000 keywords Low Requires stable official project
Connect client GSC for audit Low Use client-authorized formal environment
API automated daily report Not Applicable Purchase explicit API entitlements

How to Judge When Limits Are Reached ​

  • Page clearly displays Semrush quota or upgrade prompt: record module and original text, likely upstream quota;
  • RelayX console shows today's count exhausted: wait according to node reset rules;
  • Only single browser fails: check extensions, related site data, and network;
  • All nodes inaccessible: check service status and contact support;
  • No data for a small site: likely database coverage, not quota failure.

Do not repeatedly reinstall extensions to mask quota prompts. Providing time, node, module, operation, error text, and desensitized screenshots makes diagnosis easier.

FAQ ​

Is the Business node limit 50,000 per day? ​

No. 50,000 is the single report result limit for Business in official documentation, not daily query counts for node users. Check RelayX real-time node rules.

Can nodes save Site Audit projects?​

Whether you can create depends on real-time permissions; even if possible, it's only for public, temporary, and rebuildable projects. Use official workspaces when historical continuity and client authorization are required.

Why can't I export if I can view the report?​

Viewing and exporting have different permissions and quotas. They may also be controlled separately by module, format, and node policy. Validate with a specific report before purchase.

How to use on multiple devices?​

Follow the device count shown on the product page and console. Do not copy Cookies or session files; for genuine multi-user concurrent needs, choose official additional users or explicitly supported independent access.

Further Reading and Next Steps​

Sources and Review Notes​

This article was reviewed by the RelayX Editorial Team on August 24, 2026 based on the following official sources. Product features, quotas and prices change; when making purchase decisions, please verify again on official pages and RelayX real-time product pages.