> For the complete documentation index, see [llms.txt](https://help.rankability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rankability.com/track/per-keyword-ga4-data.md).

# Reading per-keyword GA4 data

See on-site engagement and conversion data for the specific pages that rank for each tracked keyword, with traffic source filtering and per-URL breakdowns.

When you drill into a tracking project in Track, the GA4 tab shows on-site behavior data for the specific landing pages that rank for that keyword. This connects the dots between where you rank and what happens when users arrive on your site.

## How it works

Rankability cross-references two data sources:

1. **GSC ranking URLs** – The pages that Google Search Console reports as ranking for your tracked keyword.
2. **GA4 page-level data** – Sessions, engagement, and conversions for those same page paths in Google Analytics.

This means you see GA4 metrics only for the pages that are actually ranking for the keyword, not your entire site.

## Metrics shown

For each landing page, the GA4 tab displays:

* **Sessions** – Total sessions on that page.
* **Engagement rate** – Percentage of sessions that were engaged (meaningful interaction beyond a single page view).
* **Conversions** – Conversion events triggered on that page.
* **Bounce rate** – Percentage of sessions where the user left without interaction.

## Daily trend chart

Below the summary metrics, a daily sessions chart shows how traffic to the landing page has trended over the selected period. If multiple pages rank for the keyword, you can filter the chart to a specific URL using the page filter dropdown.

## Traffic source filter

Use the source filter to switch between:

* **All sources** – All traffic to the landing page regardless of origin.
* **Organic search** – Only sessions from traditional search engines.
* **AI referral** – Only sessions from AI platforms.

This is useful for understanding whether the keyword’s traffic comes primarily from traditional search or AI citations.

## What to look for

* **High rank, low engagement** – If you rank well but the engagement rate is low or bounce rate is high, the page content may not match search intent. Consider revising the content to better answer the query.
* **High conversions** – Pages with strong conversion rates deserve protection. Prioritize maintaining their rankings and content quality.
* **Multiple ranking pages** – If several pages rank for the same keyword, check whether they’re cannibalizing each other. The one with better engagement metrics is usually the better target.

## Related articles

* [Connecting and using Google Analytics 4](/track/connecting-google-analytics.md) — Set up the GA4 integration.
* [Setting up keyword tracking](/track/setting-up-keyword-tracking.md) — Create tracking projects to see per-keyword data.
* [Connecting and using Google Search Console](/track/connecting-google-search-console.md) — GSC provides the ranking URLs used for cross-referencing.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rankability.com/track/per-keyword-ga4-data.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.