Understanding SEOmonitor Errors in Hurree

If you're experiencing issues with your SEOmonitor widgets, this guide explains the most common errors and how to resolve them. Each error below matches the message you'll see in Hurree.

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

Explanation: SEOmonitor uses an API token to verify your identity, and if the token is missing, has expired, or has been regenerated or revoked, your widgets will stop retrieving data.

How to solve: Reconnect your SEOmonitor account via Hurree to restore access. Reconnecting re-establishes the connection with a valid API token, and your widgets should begin retrieving data again. If the issue continues after reconnecting, please contact our support team for assistance.

Explanation: Your SEOmonitor account requires a valid payment method before this request can be completed. SEOmonitor restricts API access when an account has outstanding billing issues.

How to solve: Update your billing details in your SEOmonitor account settings and try again, or contact your SEOmonitor administrator to confirm your account is in good standing. If the error persists once billing is up to date, please contact our support team.

Explanation: Your account does not have the permissions required to access this SEOmonitor resource. This can occur if your user role has changed, access has been revoked, or the relevant campaign does not have a Google Search Console profile connected within SEOmonitor.

How to solve: Check that your SEOmonitor account has the necessary access rights, and verify that the relevant campaign has a Google Search Console profile connected within the SEOmonitor app. If access is still denied, contact your account administrator to review your permissions, then refresh your connection and try retrieving the data again.

Explanation: The requested SEOmonitor resource could not be located. This may occur if a campaign, keyword group, or other resource has been deleted or moved within SEOmonitor, or if the reference is incorrect.

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

Explanation: The SEOmonitor resource you're trying to access has been permanently deleted and is no longer available.

How to solve: Deleted resources cannot be restored through the connection. To continue reporting on SEOmonitor data, update your widget settings to use a different resource within your account.

Explanation: One or more values submitted with this request did not pass validation, meaning SEOmonitor 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: SEOmonitor restricts the number of requests allowed within a given time window, and if your connected widgets are pulling data at a high frequency, this limit may occasionally be reached.

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 SEOmonitor's servers. This is not caused by any action on your part, and as the issue originates within SEOmonitor'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: SEOmonitor is currently unavailable due to a temporary service disruption or maintenance on their platform.

How to solve: Wait a few minutes before trying again. Temporary outages are usually resolved automatically by SEOmonitor. If the issue persists for an extended period, please contact our support team.

Explanation: You may occasionally see one of the following less common errors: 400: Bad Request, 405: Method Not Supported, 412: Precondition Failed, 413: Request Too Large, 417: Expectation Failed, or 428: Precondition Required. These indicate that something about the request sent to SEOmonitor was invalid, incorrectly formatted, or could not be processed; 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 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 SEOmonitor widgets, our support team is here to help. Share the error message you're seeing along with any relevant details, and we'll work with you to identify and resolve the issue as quickly as possible.