Troubleshooting
Docs
Troubleshooting
Fixing Google Connection Issues
Last Updated on
Read Time
4 min read
In short
What it does
RankFrame connects to Google via OAuth to enable Google indexing, including its Overview and Keywords tabs. When the connection breaks or uses the wrong account, these features stop working. This article covers every Google connection symptom and how to fix it.
Where
Google indexing > Setup
Cost
Free
Connection Symptoms and Fixes

Google indexing Shows “Not Connected” or Fails to Load Data
Symptom: Google indexing displays “Not Connected”, the panel spins indefinitely, or all data fields are blank.
Cause: Your OAuth token has expired or was revoked through Google Account security settings. This can happen after extended Framer sessions or a Google Account security event.
Fix: Open Google indexing, go to the Setup tab, click the red Disconnect link to clear the expired token, then click Connect Google Account and sign in again.
Wrong Google Account Connected
Symptom: The plugin shows a connected account, but the Overview tab shows zeros, keyword data is empty, and domain verification fails.
Cause: You signed in with a personal Gmail account instead of the Google account that owns the Search Console property for your domain.
Fix: Go to Google indexing > Setup tab, click Disconnect, then reconnect using the exact Google account that has Owner or Full User access to your domain in Search Console.
Domain Verification Shows Failed or Pending
Symptom: The Domain Verification step in the Setup tab shows a failed or pending status even after connecting a Google account.
Cause: The connected Google account does not have Search Console access to the domain RankFrame is trying to verify.
Fix: Go to Google Search Console, open your property, go to Settings > Users and permissions, and confirm your connected account is listed as Owner or Full User. Then return to RankFrame, disconnect, and reconnect that account.
Analytics Data Shows Zeros or “No Data”
Symptom: The Overview tab in Google indexing shows all zeros or a “No data available” message immediately after connecting.
Cause: A new OAuth connection needs 48 to 72 hours to pull historical data from Search Console. The property may also not have accumulated enough impressions or clicks yet.
Fix: Wait 48 to 72 hours after connecting, then reload the Overview tab. If data still does not appear after 72 hours, disconnect and reconnect, then wait again.
Indexing History Shows Errors on Every Submission
Symptom: Every URL in the Indexing History shows an error status, even URLs that were previously submitted successfully.
Cause: You have used all your recrawl requests for today (up to 10 pages a day per workspace). Batch-submitting a large sitemap at once is the most common way this happens.
Fix: Wait 24 hours for the daily quota to reset. When you resubmit, prioritize your most important or recently updated pages rather than submitting every URL at once.
Good to know:
Quota Tip RankFrame lets each workspace ask Google to recrawl up to 10 pages a day. If you have a large site, spread requests across multiple days and prioritize your most important or recently updated pages first.
Related features
Google indexing: Send your sitemap and ask Google to recrawl up to 10 pages a day.
Frequently asked questions
Why does my Google OAuth connection expire in RankFrame?
Google OAuth tokens expire after a period of inactivity or when access is revoked through Google Account security settings. When this happens, Google indexing loses its connection and must be reconnected.
How do I reconnect Google in RankFrame?
Which Google account should I connect to RankFrame?
Why is the Overview tab showing all zeros after I connected Google?
How many pages can I ask Google to recrawl each day?
Still stuck?
Try the troubleshooting guides, or send support the page link and a screenshot.