Understanding Semrush Errors in Hurree

If you're experiencing issues with your Semrush widgets, this guide explains the most common errors and how to resolve them.

If you encounter an error that isn't covered below, please contact our support team for assistance.

Explanation: If your Semrush Connector is connected in Hurree but your Dashboards are showing no data, check that your account has API access and enough API units for the reports being requested. A successful connection does not guarantee access to every report. Standard API access requires an eligible Business subscription and separately purchased API units; traffic and audience reports may require separate Trends API access. Missing access or insufficient units can produce an error, an empty result, or partial report data, depending on the endpoint. No data can also mean that there are no results for the selected query or date range.

How to solve: Log in to your Semrush account and confirm that your plan is Business tier or above, and that you have an active Standard API unit allocation with remaining units for the current billing cycle. If Trends data points specifically are empty, check that you have an active Trends API subscription. If your Semrush account has the correct access in place and the data is still not appearing, please contact our support team and include the Dashboard name and the data points affected.

Explanation: The credentials used to connect your Semrush account could not be verified. This can happen when the API key is incorrect, has been changed, or is no longer valid.

How to solve: Check the current API key in your Semrush account's Subscription info, then reconnect through Hurree using the valid key with no extra spaces. If the issue continues after reconnecting, please contact our support team.

Explanation: You don't have permission to access this Semrush resource. This can occur if your user role has changed, access has been revoked, or your subscription does not include the report or database you're trying to access - some Semrush data is only available on higher-tier plans or as a paid add-on.

How to solve: Check your API access, report entitlement, and remaining API units in Semrush, or ask your administrator to review them. Some Semrush endpoints also return 403 when API units are insufficient. If the unit balance is exhausted, replenish it or confirm the renewal terms with Semrush; reconnecting alone will not add units. Once access and units are available, try again.

Explanation: The requested Semrush resource could not be found. This may occur if a project, tracked domain, or keyword campaign has been deleted or moved within Semrush, or if the reference is incorrect.

How to solve: Review the relevant Semrush account and verify that the resource still exists. If it has been removed, you may need to update your widget settings or select an alternative data source.

Explanation: The request could not be completed because it conflicts with the current state of the resource in Semrush - for example, if a project is being updated by another process at the same time.

How to solve: Review the relevant data in your Semrush account and try again. If the conflict continues, please contact our support team for assistance.

Explanation: The Semrush resource you're trying to access has been permanently deleted and is no longer available. Unlike a 404, this confirms the item existed previously but cannot be recovered.

How to solve: Update your widget settings to point to an active project or data source. If you believe the resource was deleted in error, check your Semrush account or contact your administrator.

Explanation: Some of the data provided with this request failed validation, meaning Semrush could not process it as expected.

How to solve: Check that all fields in your integration settings are correctly filled in and try again. If the issue persists, please contact our support team.

Explanation: Semrush has temporarily limited the request rate because too many requests were made within the permitted time window. This is different from exhausting your API unit balance: insufficient units may instead return ERROR 132 or 403, depending on the endpoint.

How to solve: Wait a moment before trying again; your access will resume automatically once the rate limit window resets. If you are consistently hitting this limit, please contact our support team so we can review your connector configuration.

Explanation: An unexpected error occurred on Semrush's servers. This is not caused by any action on your part, and as the issue originates within Semrush's infrastructure, it is outside of our control.

How to solve: Internal server errors are typically temporary and often resolve automatically. Wait a moment and try again, or check your widget after the next scheduled sync period. If the error persists after multiple sync attempts, please contact our support team for assistance.

Explanation: Semrush is currently undergoing maintenance or is under heavy load, so it is temporarily unable to process your request.

How to solve: Wait a few minutes before trying again. Your widgets will update automatically once Semrush is available again. If the issue persists for an extended period, please contact our support team.

Explanation: Semrush's servers did not respond quickly enough to complete the request. Like internal server errors, this originates on Semrush's side and is outside of our control.

How to solve: Wait a moment and try again. These errors are typically temporary and resolve automatically. If the error persists after multiple sync attempts, please contact our support team.

Explanation: Hurree's product error-message list includes 550: Server Error and 551: Method Not Supported for this connector. 550 indicates a server-processing problem; 551 indicates an unsupported request type. These labels should not be interpreted as a complete list of Semrush's native API error codes, which vary by API.

How to solve: For 550, wait a moment and try again. For 551, contact our support team so we can review the unsupported request; repeated retries may not resolve it. If either message persists, include the exact error and affected widget so we can investigate.

Explanation: You may occasionally see one of the following less common errors: 400: Bad Request, 412: Precondition Failed, 413: Request Too Large, 417: Expectation Failed, or 428: Precondition Required. These indicate that something about the request sent to Semrush was invalid, incorrectly formatted, too large, or missing a required condition; they are typically handled automatically and are rarely caused by anything on your side.

How to solve: Review your integration settings for any incorrect entries and try again. If you see 413 specifically, try narrowing the date range or scope of your widget to reduce the volume of data being requested. If any of these errors persist, please contact our support team with the error name you're seeing, and we'll investigate.

If you've completed the troubleshooting steps above and are still experiencing issues with your Semrush widgets, our support team is here to help.