Support Log in
Rank Forge Integrations — Works with Your WordPress Stack

Rank Forge + Google Search Console — Rank Tracking

Rank Forge connects to Google Search Console via OAuth 2.0 and pulls your rank data directly into the WordPress admin. See which keywords you rank for, where they sit in the results, which pages are gaining and losing clicks, and which pages are on the Content Decay list. All without leaving WordPress.


What you get by connecting GSC

Automatic rank sync

Once a day (WordPress cron), Rank Forge pulls the top 200 queries of the last 28 days from Google Search Console and stores that table in your WordPress database, in place of the table of the sync before. Keyword positions, clicks, impressions, and CTR are available on the Performance tab of Rank Forge > Analytics.

Keyword rankings

The Performance screen lists your top queries with position, clicks, impressions and CTR, and points out striking-distance keywords (positions 11 to 15), keyword cannibalization and top-3 keywords with a weak CTR.

Content Decay Detection

Rank Forge compares each page’s last 28 days of Search Console data with the 28 days before and lists the pages whose clicks fell by more than 30% or whose position got worse by more than 3 places. The list is on the Content Decay screen. Rank Forge sends no email and no notification.

Full Content Decay feature →

Site totals

The Performance tab of Rank Forge > Analytics shows total clicks, impressions, average CTR and average position for the last 28 days against the 28 days before, and the pages that won or lost the most clicks in the last 7 days against the 7 days before.


How to connect

Step 1: Click “Connect Google”

Open the Analytics & Traffic screen of the Analytics menu and click Connect Google. You’ll be redirected to Google’s OAuth consent screen.

Step 2: Authorize access

Google shows you what Rank Forge is requesting access to:

  • Read-only access to Search Console data
  • Other permissions that the one Avakode Google sign-in asks for in the same step: Google Analytics (read), the Indexing API, and Drive file and Calendar access used by other Avakode products

Approve and you’re redirected back to WordPress.

Step 3: Check your GSC property

When one of your verified properties matches the address of this WordPress site, Rank Forge picks it by itself, and the Google Search Console card in Rank Forge > Settings, tab Integrations shows it as the Active Property. When none matches, the card asks you to select your property: pick the one that is this site. To switch later, click Change property on that card. Rank Forge works with domain properties and with URL-prefix properties.

Step 4: First sync

As soon as the property is set, Rank Forge queues a first load in the background: the top 200 queries of the last 90 days. This is so when Rank Forge matched the property itself right after you connect, and when you pick it yourself. You can keep working while it runs: the Performance and Content Decay screens say that the data is loading. If the load fails, they say why and show a Try again button.

Step 5: Daily sync begins

After initial sync, daily updates happen automatically via WP Cron. No manual refresh needed.


Connection and access

The connection to Google goes through our API (api.avakode.com). See the Privacy Policy, sections 3.3 and 3.9, for what our API receives.

Rank Forge uses the access for Search Console data and for the Submit to Google Index button. It does not ask for access to your Gmail.

You can revoke access at any time from two places:

  1. Inside Rank Forge: click Disconnect Google on the Google Search Console card in Rank Forge > Settings, tab Integrations; this also removes the saved property, the keyword table and the Content Decay list from your WordPress database
  2. Inside your Google account — visit myaccount.google.com/permissions and revoke Rank Forge’s access

What GSC data Rank Forge shows

Keyword-level

  • Keyword text
  • Average position
  • Total clicks
  • Total impressions
  • CTR

Page-level

  • The landing page for striking-distance keywords and CTR anomalies
  • Pages that compete for the same query (keyword cannibalization)
  • Winners and Losers by clicks, last 7 days against the 7 days before
  • Pages on the Content Decay list, with the change in clicks and position

Site-level

  • Total clicks, impressions, average CTR and average position for the last 28 days
  • The change against the previous 28 days

Which GSC data is NOT available in Rank Forge

Google Search Console has some data Rank Forge doesn’t yet pull:

  • Search Appearance breakdown(rich results, AMP, etc.) — shown in GSC directly
  • International targeting reportsGSC only
  • Manual actionsGSC only
  • Security issuesGSC only
  • Removals toolGSC only
  • Core Web VitalsGSC only

For these, use the GSC web interface. Rank Forge reads Search Console for fixed periods (the last 28 days against the 28 days before, and the last 7 days against the 7 days before), builds its keyword table from up to 200 queries, and has no filter by country or device. An exception is the A/B test of a post: for the full weeks of the test it reads the clicks, impressions and average position of that one page by day. For a question that needs more than that, use the Performance report of Search Console.


Integration with other Rank Forge features

Content Decay Detection

Runs entirely on GSC 28-day comparisons.

SEO A/B Testing

With Rank Forge Pro, a connected Google account and a chosen property, the A/B Testing section of the Rank Forge box compares Variant A with Variant B by the clicks, impressions, CTR and average position that Search Console reports for that page, week against week. Without a connected account the section still counts the page views of each variant, but it has no Search Console numbers to compare. Full A/B testing feature →

Google index status in the editor

With Rank Forge Pro and a connected Google account, a published post has a Google index status panel in the Rank Forge box. Click Check status to see Google’s coverage state, the time of the last crawl, the mobile and rich results verdicts, and a warning when Google picked a different canonical URL than you declared.

AI Content Optimizer

Works from the post itself (title, focus keyword, headings and the start of the text) and does not read your Search Console data.


Multi-site / Multi-property support

For agencies managing multiple WordPress sites:

  • Each WordPress site connects to its own GSC property
  • Disconnecting one site doesn’t affect others
  • Agency plan supports unlimited GSC connections across managed sites

Troubleshooting GSC connection

“Property not verified”

The GSC property must be verified before Rank Forge can access it. Verify it in GSC first (via DNS or file upload), then reconnect.

“No data showing”

The first load starts in the background as soon as a property is chosen. While it runs, the Performance screen says that the data is loading; if it failed, the screen says why and shows a Try again button. If no property is chosen yet, the screen asks you to choose one. Refresh on the Performance screen loads the data again whenever you want. If the license does not cover Search Console data, whether or not Google is connected, the screen shows Search Console data is not being loaded, gives the reason and has an Open the licence page button, and it does not ask you to connect Google. In that case there is no Refresh button. On the licence page, Connect to Avakode (or Reconnect, when a license is already saved on the site) is how a bought license is activated. If the data is still empty, Google may not have search data for the property yet, for example when it is new. Check that the Active Property on the Google Search Console card in Rank Forge > Settings, tab Integrations is the property you use.

“OAuth error”

Click Disconnect Google on the Google Search Console card in Rank Forge > Settings, tab Integrations, then connect again with Connect Google on the Analytics & Traffic screen. Disconnecting also removes the saved property, the keyword table and the Content Decay list, so the property is matched or chosen again when you connect.

“Rate limit exceeded”

GSC API has daily quotas. If you’re running multiple Rank Forge instances on the same GSC property, you may hit limits. Contact support for mitigation.


Ready to connect GSC?

See pricing →

Google Search Console integration is included in every paid plan.

Forge AI Assistant Online

Hi! I'm the Rank Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs