Google Search Console¶
Google Search Console (GSC) brings keyword opportunity data, performance metrics, and decay detection signals into RankerBase.
What GSC provides¶
- Keyword opportunities — Discover keywords your site is ranking for but hasn't fully optimized yet
- Performance tracking — Monitor clicks, impressions, position, and CTR for your published content
- Decay detection — Spot content that's declining in performance so you can refresh it
Connecting GSC¶
- In RankerBase, go to Sites → Configure → GSC
- Click Connect GSC
- Sign in with the Google account that has access to your Search Console property
- Grant RankerBase permission to read your Search Console data
- Click Test GSC Connection to confirm everything is working
Tip
Use the same Google account that owns or has access to your Search Console property.
Using Hashnode?
If your blog is on Hashnode, you'll need to verify it in GSC first. Add your blog URL as a URL prefix property, choose the HTML tag verification method, then paste the meta tag into your Hashnode dashboard under Integrations → Meta tags. See Hashnode → Connecting Google Search Console for full steps.
Automatic data pulls¶
Once connected, RankerBase automatically pulls data from GSC on a weekly schedule:
- Keyword opportunities — New keywords your site is appearing for
- Performance metrics — Updated clicks, impressions, and ranking positions for published content
- Decay detection — Scans for content that's losing traffic or rankings
You don't need to do anything — the data appears in your dashboard automatically.
Disconnecting¶
To disconnect GSC, go to Sites → Configure → GSC and click Disconnect.
Troubleshooting¶
| Problem | Solution |
|---|---|
| Connection fails | Make sure you're signing in with a Google account that has access to your Search Console property |
| No data showing up | Check that the GSC property URL matches your site URL exactly (including https:// vs http://). GSC data also has a 2–3 day reporting delay, which is normal |
| Permission denied | Verify your Google account has at least read access to the Search Console property |
See also Troubleshooting → GSC / GA4 OAuth issues.