This article covers GSC data, GA4 analytics, OAuth connections, and date range issues.
⚠️ Error 1: GSC keyword data shows "No data available"
What's happening:
Your Google account may need to be reconnected, or the date range is out of bounds.
Steps to try:
- Go to Site Metrics → Site Explorer → Manage Sites (GSC Accounts page) → View X connected accounts (GSC) → Delete your account from the list → Refresh the page → + Connect New GSC Account → Select Your Account
- Go to OTTO SEO → All Sites (SEO Automation) → Manage Sites → Ensure your site is "Active".
- Make sure your date range doesn't exceed 16 months back — GSC data older than that is unavailable.
- Don't select future dates — the end date must be yesterday or earlier.
- If the connection is active and dates are valid, wait 5 minutes and refresh.
⚠️ Error 2: Google Analytics data shows "Data unavailable"
What's happening:
Google's Analytics API has daily request limits shared across all Search Atlas users. During peak hours, some requests are temporarily delayed.
Steps to try:
- Refresh during off-peak hours (early morning or late evening).
- Narrow your date range — 30 days loads faster than 90 days.
- Close and reopen the dashboard — analytics data is served from a cache that refreshes every few hours.
- Reconnect your Google account to force a fresh token: Site Metrics → Site Explorer → Manage Sites (GSC Accounts page) → View X connected accounts (GSC) → Delete your account from the list → Refresh the page → + Connect New GSC Account → Enter/Select Your Account.
- If no analytics data has appeared for 48+ hours, contact support with your GA4 property ID.
⚠️ Error 3: Only some GA4 tabs load — others show errors
What's happening:
Each report tab makes a separate API request. During high-demand periods, some succeed while others are throttled.
Steps to try:
- Click the failing tab again after 30 seconds.
- Try loading the tab during off-peak hours.
- Hard-refresh the page and navigate back to the failing tab.
- If one specific tab consistently fails (e.g., Conversions), contact support with the tab name and your date range.
⚠️ Error 4: My GSC property isn't showing up when I try to connect it
What's happening:
The Google account you're connecting doesn't have sufficient access to that property in GSC.
Steps to try:
- Log into Google Search Console directly and confirm your account has Owner or Full User access — Restricted access won't work.
- Disconnect and reconnect your Google account in Search Atlas to refresh the property list.
- If the property belongs to a different Google account, add that account: Left Sidebar → Site Metrics → Site Explorer → Manage Sites → Connect GSC Account.
- If the property was recently created in GSC, wait 24 hours — new properties aren't immediately available via API.
⚠️ Error 5: My Google account keeps disconnecting every few days
What's happening:
Google periodically requires re-authorization for third-party apps — this is a Google security policy, not a bug.
Steps to try:
- Reconnect via Site Metrics → Site Explorer → Manage Sites (GSC Accounts page) → View X connected accounts (GSC) → Delete your account from the list → Refresh the page → + Connect New GSC Account → Select Your Account.
- When prompted during the OAuth flow, ensure you grant all requested permissions and check "Allow offline access" if shown.
- If you recently changed your Google account password, all connected apps need to be re-authenticated.
- Check your Google Account security settings for any alerts requiring re-confirmation of third-party app access.
- Contact support if disconnections happen within 24 hours of reconnecting — this may indicate a token refresh issue on our end.
⚠️ Error 6: Data in Search Atlas doesn't match what I see directly in GSM
What's happening:
This is usually a filter or date range difference, not a data error.
Steps to try:
- Compare the exact same date range in both tools.
- Match the device filter — "All devices" vs. "Desktop only" produces very different numbers.
- Match the country filter.
- Note that GSC data has a 3-day processing lag — the last 3 days are provisional in both tools.
- Contact support only if the discrepancy is more than 10 positions across many keywords and persists for more than 1 week.
⚠️ Error 7: Date range selector resets or shows a validation error
What's happening:
An invalid date combination was entered.
Steps to try:
- Make sure the start date is before the end date.
- Don't select dates more than 16 months in the past.
- Don't select future dates — maximum end date is yesterday.
- Try typing dates manually instead of using the calendar picker.
- Hard-refresh and try setting the date range immediately after the page loads.
⚠️ Error 8: "Insufficient Data" appears in Core Web Vitals field data
What's happening:
Google's Chrome User Experience Report (CrUX) requires a minimum number of real Chrome users before it generates a report. This is a Google data availability limitation.
What to do:
- This is not an error — use the Lighthouse lab data scores as your benchmark instead.
- CrUX field data will appear automatically once your site accumulates enough Chrome user traffic.
- Very new sites, low-traffic sites, and sites with mostly non-Chrome audiences may never accumulate CrUX data.
- Focus on growing organic traffic to speed up CrUX data availability.
Most Google Search Console and Analytics issues are not platform errors—they are the result of API limits, access permissions, data processing delays, or differences in filters and configurations.
Google’s data ecosystem is not real-time and is subject to rate limits, latency, and strict access controls.