The examples below outline some potential error states a user may see with the Google Search Console Integration.
- An account/site is not integrated with Google Search Console
- An article was published <48 hours ago (and GSC does not yet have data for that article)
- An article has multiple URLs listed in GSC
- Generic Error
- Authorization Failed
Article Page Performance Metrics Errors
Error 1: An account/site is not integrated with Google Search Console
Explanation: If an account has not integrated with GSC or has not selected this site to be integrated, Chartbeat will not display performance metrics. We have two customized errors depending on whether the user is an Admin or a Member.
Error Message for an Admin:
Error Message for a Member:
Error 2 : An article was published <48 hours ago (and GSC does not yet have data for that article)
Explanation: If an article is less than 48 hours old, GSC will not have data available yet. The integration will only work for articles that are more than 48 hours old, with a time frame >48 hours ago.
Error 3 : An article has multiple URLs listed in GSC
Explanation: If an article has multiple paths in GSC, we cannot match GSC data with a Chartbeat article page path and will show the below error.
Error 4 : Generic Error
Explanation: There may be other issues on the backend that we have not yet identified. For these errors, we have a generic message, "Something went wrong". Feel free to reach out to Chartbeat Support to troubleshoot at support@chartbeat.com.
Integration Module Error States
Error 1 : Generic Error
Explanation: There may be other issues on the backend we have not yet identified. For these errors, we have a generic message, "Something went wrong". Feel free to reach out to Chartbeat Support to troubleshoot at support@chartbeat.com.
Error 2 : Authorization Failed
Explanation: Something in the authorization flow did not work (e.g, Chartbeat could not find any matching sites). Feel free to reach out to Chartbeat Support to troubleshoot at support@chartbeat.com.
Error 3 : No sites were selected / saved
Explanation: Something on the backend went wrong while trying to get the list of sites a user can manage
- Potential reason: If a user did not save any sites for data to be shown. In this instance, we suggest the user go to “Manage” sites and save relevant sites
- Other reasons: Unknown. This could require additional investigation depending on the issue.