If you're having trouble connecting or seeing data from Google Search Console (GSC) in RivalFlow, here are a few things to check.
1. ✅ Confirm You Have Access to the Correct Property
Make sure the Google account you're connecting has access to the exact GSC property for the site or subdomain you're tracking.
If your content lives on a subdomain (e.g.,
blog.example.com), you’ll need access to that specific property—not justwww.example.com.If you’re seeing no properties listed when connecting GSC, your Google account may not have access to any active GSC properties.
👉 To fix: Log into Google Search Console directly and confirm which properties are available under your account.
2. ✅ Verify the GSC Property Matches Your Content's URLs
Your GSC property should reflect the correct version of your site (e.g., http vs. https, or www vs. root domain). If the wrong version is connected, some or all pages may not show data.
👉 To fix: Try reconnecting GSC and selecting the correct property that matches the full URL of the content you're tracking. If you're unsure, check where most of your traffic is recorded in GSC.
3. ✅ No Properties Showing When Connecting GSC
If you go to connect Google Search Console to RivalFlow and no properties are available in the dropdown:
This usually means your Google account doesn’t have access to any GSC properties.
If you should have access, double-check that you’re logged into the correct Google account, or ask the GSC property owner to share access with your Gmail.
4. ✅ Managing Parent/Child Accounts
If you're using a shared or agency-style login structure (e.g., a parent account managing campaigns for multiple users):
Make sure the parent account has access to all relevant GSC properties. This is handled through Google Search Console permissions from the account's owner.
If a child user can't see the expected properties, confirm they’re shared with the parent account’s Gmail address.
5. ✅ Seeing Zero Clicks or Impressions?
A few reasons why you might see zeroes:
GSC simply doesn't have data for that URL yet. It can take a couple of weeks for impressions/clicks to appear—especially on new or low-traffic pages.
You might be tracking a URL that doesn't get indexed or isn't ranking (e.g., hidden behind navigation, no backlinks).
In rare cases, tracking might be affected by formatting issues in the URL (e.g., unusual parameters or old link tracking formats).
👉 To fix:
Double-check that the URL you're tracking exactly matches what's indexed in GSC.
Try searching for that page in Google using
site:yourdomain.com/page-slugto see if it's indexed.
6. ✅ Did Your Chart Lose Data after a Certain Date?
This looks like a normal GSC chart, but instead of the data continuing it just drops off a cliff. This isn't the same as poor performance with impressions that drop steeply. This is data coming to a standstill.
The most likely situation is that the tracked page's original URL was updated. This happens with title changes and redirects. Since Google Search Console is tracking the old URL, it drops off all data from when traffic was diverted to another URL.
👉 To fix:
An automatic fix to prevent this is in the works. In the meantime, if you want to continue to track that page in RivalFlow, your best workaround is to recreate the project with the new URL. Change the "complete" date to the one from the original URL, and track from there.
It won't have historic data since it's a new URL, but you will have that page's performance.
7. ✅ Known Tracking Issues (URL Formatting)
Some older projects created might include URLs with text highlights or tracking tags that block them from syncing properly with GSC.
👉 If your page isn’t tracking, and the URL looks unusual (e.g., contains #:~:text= or srsltid=), reach out to Support. We’re actively cleaning up these issues, and we can help make sure the affected URLs are corrected.
A Delay in Data
When you first connect GSC to RivalFlow, it takes a couple of days for the data to populate and be available. You might see this as "Collecting."
Google Search Console holds onto the data for today's date until it's done collecting. At that point, it send it over to us. During that time, you might see a small difference in data counts, but it will catch up where the two eventually match.
Other Challenges?
If none of these suggestions solve the issue, feel free to contact our Support Team and we’ll do our best to help.