Google Console

The Google Console plugin puts Search Console, Analytics and AdSense behind a single Google connection and a single set of tabs, and it also manages the tracking IDs that your theme prints in the page head. It is not active after install. Enable it under Admin → Plugins, and it appears in the sidebar under Growth.

The Google Console plugin's Settings tab, offering one-click connect
One-click connect uses the jekcms Google app, so you need no Cloud Console project and no client ID.

Two points to know first. The reports are read-only: the plugin asks Google only for three read scopes, so nothing you do here can change a Search Console property or a GA4 configuration. The Insights tab is built from history that the plugin collects itself, so it stays empty until cron is running.

Connecting

Open Google Console → Settings. The connection card starts with a one-click button that uses the jekcms Google app, so you do not need to create a Cloud project. Under it, an Advanced section lets you connect with a Google Cloud app of your own.

One-click connect has two requirements that the button cannot check in advance. Your admin must be reachable over HTTPS (a local or plain-HTTP install cannot use it), and your domain must have an active license. If the service is unavailable, the plugin shows a message and points you to Advanced.

Connecting with your own Cloud app

In Google Cloud Console, create a project and enable five APIs under APIs & Services → Library: Google Search Console API, Web Search Indexing API, Google Analytics Data API, Google Analytics Admin API and AdSense Management API. The Admin API is the one most often forgotten. Without it, the plugin cannot list your GA4 properties and you have to type the numeric property id by hand.

Configure the OAuth consent screen as External, and add the Gmail address you use in Google Cloud under Audience → Test users. This fixes the Error 403: access_denied screen.

Then create an OAuth client ID (Web application) and add this authorized redirect URI exactly:

https://YOURSITE/admin/plugins/jek-google/oauth-callback.php

Paste the client ID and secret into the Advanced section and press Connect.

Publish the app when you finish. While the consent screen is in Testing, Google revokes the grant every seven days and the plugin starts showing a reconnect banner. To fix this, choose OAuth consent screen → PUBLISH APP → In production; the banner shows the same instruction.

Credentials are stored encrypted. If encryption is not available on the server, the plugin does not store the secret in plain text; it refuses to save it and shows the reason.

Picking your properties

Once connected, the Settings tab offers dropdowns populated from your own account: the Search Console site, the GA4 property and the AdSense account. Pick from the lists instead of typing. The Search Console value has to be in Google's exact form, and the picker writes it correctly (sc-domain: for domain properties, a trailing slash for URL properties).

The Diagnostics card below prints one line per service - Search Console, AdSense, Analytics - with either working or the exact error that Google returned. When something is misconfigured, this error text tells you more than a status icon would.

The report tabs

All the dated reports offer a 7, 28 or 90 day window, and every window ends yesterday instead of today. Search Console and GA4 complete a day's data at different times, so both reports end on yesterday to cover the same period.

Overview is a summary of four numbers: Search Console clicks and impressions with trend arrows and sparklines, GA4 users, and AdSense earnings for yesterday with the month to date underneath.

Search Console is the most detailed tab. Clicks, impressions, average CTR and average position across the top, then charts for performance, CTR and position. Below that: your top queries and top pages, rising and declining queries compared against the previous period, devices and countries. Two cards are especially useful. Opportunity queries lists queries with a fair number of impressions, a position between fourth and twentieth and a click-through rate under three percent: pages that rank but get few clicks. Pages losing traffic lists pages that used to get clicks and no longer do.

Insights does not call Google at all; it reads the history the plugin stores. Once a day, cron fetches your Search Console data and keeps it, backfilling ninety days on the first run. The report then shows a 180-day trend and four lists that a live query cannot show: pages declining sharply against their own past, striking-distance keywords sitting between position eight and twenty with real impressions, keyword cannibalization where several of your pages compete for one query, and pages rising. Each page row links straight into the editor when it matches a post.

Without cron this tab stays empty. A Fetch now button fetches the data at once, but the tab is most useful once history has built up. Cron Setup covers the install.

Analytics shows users, sessions, page views and bounce rate, a daily traffic chart, your top pages by path and your traffic channels.

AdSense shows estimated earnings for today, yesterday, month to date, the last seven days and the last thirty, in your account's currency. The tab shows earnings only. The plugin does not request impressions, clicks or RPM, so the tab shows how much you earned but not why.

PageSpeed needs no Google connection. It runs PageSpeed Insights against your own site for mobile and desktop in parallel and stores the four category scores along with the lab metrics (FCP, LCP, TBT, CLS, Speed Index) and, where Google has enough real-world data, the field values from CrUX. You can add a PageSpeed API key in Settings if you hit the anonymous rate limit; note that this key is stored as plain configuration rather than in the encrypted secret store, so use a key restricted to the PageSpeed API. The tool measures only your own hostname.

Indexing coverage

The Search Console tab carries an Indexing Coverage scan that sends your published URLs (the homepage and up to two thousand posts and pages, newest first) through Google's URL Inspection API and classifies each one as indexed, not indexed, an error, or not yet checked.

It runs in rounds of five URLs with a short pause between them, because the API is slow and shared hosts have execution limits. Leave the page open and it works through the list; each result is cached for twenty-four hours, so a second run does not use quota for URLs already checked. The limit of two thousand matches Google's daily inspection quota per property.

There is also a Submit for Indexing action, which has limits you should know. Google offers the Indexing API only for job posting and live stream pages, so jekcms ships it switched off, and the OAuth connection does not request the indexing scope at all. Turning the checkbox on is therefore not enough to make it work: Google will refuse the calls. Use the coverage scan, and get ordinary pages indexed through your sitemap, which jekcms rebuilds automatically.

The tracking snippets

The Frontend Snippet Injection card takes three IDs: a GA4 measurement id (G-…), a Tag Manager container id (GTM-…) and an AdSense publisher id (ca-pub-…). This part needs no Google connection: tick the box, paste the ID and save.

The plugin checks each ID against its expected format and copies it into the core site settings; the theme's header then prints the tags. This has two results. An ID in the wrong format is discarded without a message and is not printed into your pages. Unticking a box clears the core setting, so this card turns tracking on or off for the whole site, not only for this plugin.

If you set a Tag Manager container, the GA4 gtag snippet is not printed. Configure GA4 inside GTM so that it does not load twice. jekcms also emits a preconnect for whichever tag hosts you are using.

When the site's cookie consent banner is enabled, Google Consent Mode v2 is emitted ahead of the tags with every storage type denied by default, and updated to granted once the visitor accepts. The scripts still load; only storage waits for consent. If the consent banner is off, nothing waits for consent.

The snippets are printed for every visitor, including you while you are logged into the admin. Exclude your own traffic with an internal-traffic filter or IP exclusion in GA4; the site does not do this for you.

The weekly email

Settings has a Weekly Email Summary switch. With it on, a connected site emails a performance digest roughly once a week to the address you enter, or to the site admin address if you leave it blank.

The digest carries Search Console clicks and impressions with week-over-week arrows, GA4 users and page views, AdSense earnings for the last seven days and month to date, and the five queries that earned the most clicks, in the site's language. It compares the last seven days against the seven before that.

It is sent every 6.5 days instead of exactly every seven, so a cron run that starts a little later does not skip a week. Like Insights, it depends on cron: the delivery is attempted from a scheduled run, not from page traffic.

Caching, and the refresh button

Every Google call is cached, both to keep the panel fast and to stay inside API quotas. Search Console and Analytics responses hold for thirty minutes, AdSense for an hour, the Settings diagnostics for five minutes, and coverage and PageSpeed results for twenty-four hours. An error response is cached for only two minutes, so a temporary failure disappears quickly.

The refresh control on Overview clears the whole cache. Use it after changing a property. Using it every time a number looks old mostly uses up quota.

Not in this plugin: Google Preferred Source

The "Prefer us on Google" block, which readers use to mark your site as a preferred source in Search, is a core feature and not part of this plugin. It is configured in the Theme Customizer under the post settings. You choose whether it appears, whether it renders as Google's official button or a plain link, and where on the post it sits. When cookie consent is enabled, Google's script loads only after the visitor has accepted, and a plain link is shown until then.

Be the first to know

New features, release notes and CMS guides. We send a couple of emails a month.