Publishing more content is not the same as content working. A blog post has a job: bring in a sale, a lead, an enquiry, or enough trust that the next visit converts. Google Analytics 4 tells you which pages are doing that job and which are just adding to the page count.
One housekeeping note first. Universal Analytics stopped processing data in 2023 and its reports are gone. Any guide that sends you to Behaviour, Site Content or Goals is describing a product that no longer exists. The five reports below are GA4 only, with the exact menu path for each, what to look for, and what to do about it.
Set up before you report
GA4 reports are only as good as the configuration behind them. Four things to check before you trust a single number:
- Key events. GA4 calls conversions “key events”. Mark the actions that matter as key events: form submissions, phone clicks, purchases, quote requests, guide downloads. If nothing is marked, every report below will show zeros in the column that matters most. Admin, Events, toggle “Mark as key event”.
- Enhanced measurement. Turn it on in Admin, Data streams, Enhanced measurement. It tracks scroll depth, outbound clicks, site search, file downloads and video engagement without extra tagging. The site search and scroll events are the ones content teams use most.
- Search Console link. Admin, Product links, Search Console links. This adds a Search Console section to Reports and is the only way to see which queries bring people to each post inside GA4.
- Data retention. The default retention for event-level data is short. Set it to the maximum in Admin, Data settings, Data retention, or your year-on-year comparisons in Explorations will have no data to compare. Google’s data retention help page covers the options.
Also drop the habit of quoting bounce rate. GA4 measures engaged sessions instead. A session counts as engaged if it lasts at least ten seconds, triggers a key event, or includes two or more page views (Google’s definition). Bounce rate still exists in GA4 but it is simply the inverse of engagement rate, and it is not comparable with the old Universal Analytics number. Compare GA4 to GA4 only.
Report 1: Landing pages (which content brings people in)
Path: Reports, Engagement, Landing page.
This is the first report we open on any content account. It lists the pages people arrived on, with sessions, engagement rate, average engagement time and key events for each. Add a filter for page path contains /blog/ and sort by sessions.
What to look for:
- Posts with high sessions and no key events. The traffic is real but the page is a dead end. Add a relevant call to action, link to the service page it should feed, or accept that it is an awareness piece and measure it on engagement instead.
- Posts with modest sessions and a high key event rate. These are your best converting pages. Promote them, link to them from higher-traffic posts, and write more on the same topic.
- Posts that have slid. Change the date range comparison to the previous period and sort by the change in sessions. A post that lost a third of its traffic usually needs a refresh, not a replacement.
Add a secondary dimension of session default channel group to split organic search from social, email and referral. A post that only works when you email it is a different asset from one that ranks.
Our routine: once a quarter, export the top landing pages and tag each one keep, refresh or redirect. That list is the content plan for the next quarter.
Report 2: Pages and screens (what people actually read)
Path: Reports, Engagement, Pages and screens.
Landing page tells you where people arrive. Pages and screens tells you everything they read after that, which is where internal linking and related posts earn their keep. The metric that matters here is average engagement time. Unlike the old time on page, it only counts while the tab is in the foreground, so it is a fair measure of attention.
Set a benchmark per content type. A long guide with an average engagement time that would barely cover the introduction is being skimmed or abandoned. Check the page on a phone, look at how far down the first useful answer sits, and move it up.
For scroll depth, enhanced measurement fires a scroll event when a reader reaches ninety per cent of the page. Build a free-form Exploration with event name as a filter, page path as the row and event count as the metric. Divide scroll events by views and you have a completion rate per post. Compare completion between posts that convert and posts that do not. The difference is usually structure, not topic.
Report 3: Key events by page (which content creates value)
Path: Explore, Free form. Rows: landing page. Columns: event name. Values: key events.
The standard reports show key events in total. The question for a content strategy is which pages contribute to them, including the pages that assisted rather than closed. That needs an Exploration.
Build it once and save it. Then:
- Sort by key events to see which posts directly produce enquiries or sales.
- Switch the row to page path and look at pages that appear in sessions before a key event. Those are assisting pages. Link from them to the converting pages and to the relevant service page.
- Give leads a value. Under Admin, Key events, you can set a default value for a lead event. Without it, a post that drives ten enquiries and a post that drives one purchase look the same in the value column.
GA4’s default attribution for key events is data-driven. For content reporting that is the right setting, because last click hides almost everything a blog does. If you need to see the full path, Advertising, Attribution, Conversion paths shows how many touches a typical converting journey involves and where content sits in it.
Ecommerce stores should add one more view: Reports, Monetisation, Ecommerce purchases, with landing page as the secondary dimension. Buying guides and comparison posts often outperform category pages on revenue per session, and nobody notices until someone looks.
Report 4: Search Console queries (what people searched to find you)
Path: Reports, Search Console, Queries and Google organic search traffic (after linking).
This replaces two reports from the old guide: the keyword report that Universal Analytics lost years ago, and the gap analysis you used to do by hand. You get clicks, impressions, click-through rate and average position per query, and the organic search traffic report ties those to landing pages with GA4 engagement and key event data alongside.
Three content decisions come straight out of it:
- Impressions high, clicks low. The page ranks but the title and description are not winning the click. Rewrite them. This is a one-hour fix with a measurable result.
- Position stuck just outside the first page. Refresh the post, add the sections competitors cover that you do not, and build internal links to it. Striking-distance queries are the cheapest traffic you will find.
- Queries with no matching page. People search a question, land on something adjacent, and leave. That is a brief for a new post.
The internal site search report from the original guide still exists, it just moved. With enhanced measurement on, every search on your own site records a view_search_results event with a search_term parameter. Build an Exploration on that parameter. Terms people search on your site and cannot find are the clearest content gaps you have.
One caution for 2026. AI Overviews and AI Mode answer many informational queries on the results page, so clicks on how-to content can fall while impressions hold or rise. Judge informational posts on impressions and on branded search growth as well as clicks. We cover what to do about it in our guide to organic traffic drops from AI search, and the newer Search Console reports in this walkthrough.
Report 5: Device and tech splits (where content breaks)
Path: Reports, Tech, Tech details, then device category as the primary dimension. Or add device category as a secondary dimension on the Landing page report.
Google indexes the mobile version of your pages, and for most content sites mobile is the majority of sessions. Compare engagement rate and key event rate between mobile and desktop for your top posts. A post that converts on desktop and not on mobile has a layout problem, a form problem or a speed problem, and all three are fixable.
GA4 does not have the old Site Speed reports. For speed, use PageSpeed Insights on the individual URL and the Core Web Vitals report in Search Console for the site-wide view. Our landing page optimisation guide covers the fixes that move those numbers, and this piece on reducing bounce rate translates to GA4 engagement rate directly.
Put the five in one dashboard
Opening five reports every month is how reporting stops happening. Build a single Looker Studio page on the GA4 connector: a landing page table filtered to the blog with sessions, engagement rate and key events; a device split; and the Search Console query table. Add a date comparison and you have a content review that takes half an hour. We set these up for clients as part of our reporting work, and this article explains why live dashboards beat monthly PDFs.
Common mistakes
- Comparing GA4 to Universal Analytics. Sessions, users and engagement are all defined differently. Start your trend lines from the GA4 migration date.
- Reporting views instead of key events. Views are the easiest number to grow and the least connected to revenue.
- Counting your own team. Define internal traffic under Admin, Data streams, Configure tag settings, and create a data filter to exclude it. Small sites are badly distorted by their own staff.
- Thresholded rows. If Google signals is on, GA4 withholds rows with small user counts and your long tail disappears. For low-traffic sites, set the reporting identity to device-based.
- Chasing traffic that never converts. A post that ranks for a term your customers never search is a vanity metric. The landing page report with key events will show you which ones those are.
Five reports, one dashboard, one quarterly review. That is enough to run a content programme on evidence rather than instinct. If you want someone to build the measurement and the content plan together, that is what our SEO team does.
