Most audience dashboards are saturated with figures that trigger no decision. Google Analytics 4 and Search Console are nonetheless enough to steer an editorial site, provided you know what each one measures and discard the rest. Here is the set of metrics that actually leads to action, and the ones worth removing.
Two tools, two distinct questions
The most frequent analytical mistake is assuming GA4 and Search Console measure the same thing. They answer two different questions, and that is what makes them complementary:
- Search Console describes what happens before the click: the queries a page appears for, average position, click-through rate. This is the organic acquisition view.
- GA4 describes what happens after the click: time on page, engagement, return visits, conversion. This is the traffic quality view.
An article can pile up impressions and collapse on engagement. The reverse also happens. Without both views, diagnosis is impossible.
A figure that changes no decision during the week is noise. It has no place on a dashboard.
The metrics that trigger action
| Metric | Tool | Associated action |
|---|---|---|
| Impressions and average position | Search Console | Spot pages stuck between positions 5 and 15: work on the title and content moves them onto page one. |
| Click-through rate by query | Search Console | Many impressions and few clicks point to a title or meta description to rewrite. This is the SEO lever with the best effort-to-result ratio. |
| Emerging queries (hourly data) | Search Console | On a news site, detect within hours that a topic is taking off and publish a follow-up. |
| Engagement rate | GA4 | Below roughly 50%, suspect a content or speed problem; compare by source to isolate the cause. |
| Key events | GA4 | The real success measure: affiliate click, form submission, full read. The rest is secondary. |
| Landing pages × source | GA4 | Cross the page with the traffic origin to decide what to rewrite first. |
Two recent changes that alter the routine
Hourly data in Search Console (the 24-hour view, now also available through the API with the HOUR dimension) cuts the detection delay for a query spike from two days to a few hours. On a news publication, that is a change in the nature of editorial responsiveness.
Engagement rate has become GA4’s central metric, replacing the bounce rate inherited from Universal Analytics. In GA4, bounce is merely the inverse of engagement, computed differently — a point Google’s official documentation makes explicit, and one that prevents a good deal of panic when reading the first reports.
The metrics to remove from the dashboard
- Real-time users: gratifying on a spike day, with no bearing on any decision.
- Average session duration on its own: too noisy, distorted by tabs left open. Engagement rate is more reliable.
- Old-style bounce rate: in GA4 it no longer means what most readers assume.
- Unclean conversions: until key events specific to the site are defined, default figures say nothing about the business.
A weekly ritual in three steps
- Search Console, last 28 days: sort by impressions, spot pages in positions 5 to 15 and weak click-through rates. The week’s rewrite list comes from there.
- GA4, same pages: check engagement rate and key events. A well-positioned but poorly engaging page moves up the priority list.
- Cross the two: strong organic demand plus weak conversion signals content that does not deliver on its promise. That is where rewriting pays.
The reasoning is independent of the technology: whether the site runs on WordPress, PrestaShop or Drupal, the question asked stays the same.
What to take away
Steering an editorial site needs no more than six metrics. Value comes not from their number but from crossing what precedes the click with what follows it — the rest clutters the view and delays the decision.
This is the dashboard I open every Monday across about ten sites, at roughly a quarter of an hour per site. The discipline that cost me most to hold: removing the flattering metrics. Real-time is the hardest to give up, and the most useless. — Simon Janvier
