Similarweb "not working" has at least five different scenarios: identity login failure, RelayX node session failure, page script loading failure, target website lacking stable data, or report/export not in current permissions. They may all appear as blank screens or unavailable buttons, but require different handling.

First save the error text and timestamp, use a well-known major site as a control, then troubleshoot in the order below. Do not clear all browser data first.

First determine which category it belongs to

Phenomenon Type First Check
Email/SSO/verification code error Official Identity Login method, account recovery, organization SSO
Returns to login page after entering from RelayX Node Session Service validity, extension, device and entry point
Page frame appears but charts keep spinning Loading/Network Conflicting extensions, VPN, related site data
Only a specific small site shows empty values Data Coverage Global scope, longer window, well-known site comparison
Download button missing or prompts upgrade Permissions/Quota Product package, reports, node export rules

Categorization prevents treating "no data" as a malfunction, or "no permission" as a cache issue.

Path A: Similarweb Official Identity Login

Confirm using the registered email, Google login, or organization SSO. If the organization administrator manages seats, check if the invitation is still valid and if the email belongs to the correct team. Only initiate password recovery from Similarweb official domains.

When the login page loads but verification fails:

  1. Check system time and time zone;
  2. Confirm email and login method;
  3. Pause extensions that modify scripts, cookies, or network;
  4. Close conflicting VPN/proxy and retry;
  5. Only delete Similarweb site data;
  6. Test with a clean browser profile;
  7. If still failing, submit identity issues through the official support center.

Do not send passwords, email verification codes, recovery links, or session cookies to third parties.

Path B: RelayX Node Session

Verify Service and Node

Enter the RelayX user console, confirm Similarweb service is activated, not expired, device limit not exceeded, and currently has available nodes. Open from the console entry point, do not restore previous session directly from old bookmarks.

Verify Extension

On the Chrome extensions management page, confirm the RelayX extension is enabled, up to date, and allowed to access domains required by RelayX and Similarweb. If new permission prompts appear after update, read the description first before deciding.

Release Old Session

Close old Similarweb tabs, properly exit RelayX session, stop the same node on other devices or browsers, then re-enter from the console. Do not copy cookies or node files provided by others.

Distinguish Node from Local Machine

Test with a clean Chrome profile, same device and same network. If clean profile works, the original profile likely has extension or site data conflicts; if multiple users fail simultaneously, check service status and provide node and timestamp to RelayX support.

Path C: Blank Page, Spinning Charts, or Script Errors

In order of minimal disruption:

  1. Force refresh the page;
  2. Open Similarweb public homepage to confirm domain is reachable;
  3. Pause ad blocking, privacy, script, and other proxy extensions;
  4. Close VPN or switch to stable network;
  5. Only delete similarweb.com and relayx.net site data;
  6. Update Chrome and restart browser;
  7. Test with a clean profile;
  8. Record console page errors and network failures (for technical staff if needed).

Enterprise networks may block scripts, cookies, or CDN domains. Using a mobile hotspot for comparison can help isolate the issue, but do not bypass organizational security policies long-term; have IT verify necessary domains instead.

Path D: Target website has no data

Similarweb's official methodology states that estimates rely on multiple observable sources and modeling. Small sites, new sites, specific countries, or closed-access environments may not have stable results.

Verification steps:

  • Enter a known large public website;
  • Switch from a specified country back to global;
  • Select a longer available time range;
  • Confirm the input is a root domain without protocol, path, or incorrect subdomain;
  • Check if the page indicates insufficient sample;
  • Supplement with evidence such as search visibility, indexed pages, ad libraries, and social media.

If large sites report normally while a small site has no data, this is usually not a login failure. Do not fill empty values with 0, nor promise clients that data will definitely appear after payment.

Path E: Export fails or no button

Export depends on Similarweb product package, report type, user role, quota, and RelayX node policy. Webpage visibility does not prove that any table can be downloaded.

Symptom Action
Explicitly shows upgrade required Current product or role does not include this capability
Shows quota reached Record reset time and report, wait or adjust plan
Download starts then fails Reduce row count, check download permissions and disk space
File is empty Verify filters, time, country, and whether report has data
No export instructions on node page Check with RelayX, do not assume

First perform a small export with 10–100 rows of public data to confirm format and fields, then run large tasks. For automated bulk data, verify Similarweb official API; browser export and API have different authorizations.

Common page issues quick reference table

Issue Quick check Escalation condition
Login loop Correct entry point, extension, device, relevant cookies Reproducible across multiple configurations/users
403/Access denied Network, VPN, device, and security controls Persistent despite compliant usage
Charts not rendering Conflicting extensions, scripts/CDN, browser version Fails with clean configuration
Single report locked Package, node permissions, and quota Product promise inconsistent with actual
Single domain empty value Data coverage and scope Large sites also have no data
Excel unavailable Report, role, node export rules Still fails when explicitly included

How to submit a high-quality support request

Provide: order/service ID, node, occurrence time, device, OS, Chrome version, entry point, target report, exact error message, whether reproducible on well-known large sites, steps already taken, and redacted screenshots.

Do not provide: passwords, verification codes, recovery codes, full cookies/tokens, client lists, undisclosed projects, and analytics backend authorizations.

Example: "2026-08-24 14:10, Beijing time; macOS Chrome current version; RelayX Similarweb service active, all large site reports continuously loading after opening from console entry; disabled other extensions, closed VPN, cleared data for only two relevant domains, and reproduced with clean configuration."

Preventive settings

  • Use dedicated browser profiles for marketing tools;
  • Install only necessary extensions and limit site scope;
  • Do not reuse upstream passwords, do not copy session materials;
  • Perform small queries and exports before task deadlines;
  • Save definitions and research outputs to your own system;
  • Use official formal workspaces for long-term projects and client data;
  • Record node rules, validity period, and support entry points.

FAQ

Similarweb has no data for only one website, is this an account restriction?

Not necessarily. First compare with large websites, global scope, and longer time periods. If other reports are normal, the target site is more likely to have insufficient sample size rather than login or permission issues.

Can clearing all Cookies solve this the fastest

Not recommended as the first step. It will log you out of many unrelated sites. First clear only site data for Similarweb and RelayX, and save any unfinished work.

Why can't I export if the page is viewable

Viewing and exporting are controlled by different permissions and quotas, and nodes may have additional rules. Check real-time entitlements against the specific report and row count.

Can I send Cookies to customer service

No. Cookies may represent login sessions. Only provide errors, timestamps, versions, and redacted screenshots, using official support channels.

Further Reading and Next Steps

Sources and Verification Notes

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