What Is Google Analytics and How Do You Read It?

Jul 17, 2026 · SEO Glossary

Here's an observation from years of client onboarding: almost every website has Google Analytics installed, and almost nobody looks at it. The tag gets added on launch day, and then the account sits untouched until something goes wrong and someone finally asks, "wait, what does our traffic even look like?"

What is Google Analytics? It's Google's free measurement platform that records how people find your website, what they do once they arrive, and whether they complete the actions you care about — purchases, form submissions, signups. The current version, Google Analytics 4 (GA4), fully replaced the older Universal Analytics in 2023, and the two work so differently that a lot of long-time users still haven't adjusted.

What is Google Analytics measuring, exactly?

GA4 is built entirely around events. Every interaction — a page view, a scroll past 90%, an outbound click, a video play, a purchase — is recorded as an event with attached parameters. This is the big philosophical shift from Universal Analytics, which was built around sessions and page views with events bolted on awkwardly.

The practical consequence: metrics you knew from the old version either changed meaning or disappeared. Bounce rate was gone for a while, then returned with a different definition (the inverse of engagement rate). "Engaged session" — a session lasting 10+ seconds, or with a conversion, or with 2+ page views — became the baseline quality metric. If you're comparing GA4 numbers against pre-2023 Universal Analytics exports, you're comparing apples to a fruit that no longer exists.

The three reports worth opening every week

GA4's interface buries useful data under layers of menus, so let me save you the wandering:

1. Traffic acquisition (Reports → Acquisition). Shows where sessions come from: organic search, direct, referral, paid, social. For SEO work, watch the "Organic Search" row over time. A client's site once showed steady total traffic while organic quietly fell 25% — paid campaigns were masking the decline. Segment your channels or you'll miss stories like that.
2. Landing pages (Reports → Engagement → Landing page). Which pages actually pull visitors in from search. This is where you spot your workhorses — and the pages that get traffic but hold nobody's attention.
3. Conversions / Key events. Traffic is a vanity number until it's tied to outcomes. Define key events for the actions that matter to the business, even if it's just "contact form submitted."

One habit that makes all three reports more useful: always compare against a previous period. A landing page showing 800 sessions means nothing in isolation; the same page down from 1,400 sessions in the same month last year is a finding. GA4's date comparison is two clicks and most people never touch it.

GA4 and Search Console are different tools — use both

People conflate them constantly. Analytics tells you what happens after someone lands on your site. Google Search Console tells you what happened before: which queries you appeared for, your average position, how often people clicked. Neither replaces the other. Link the two accounts and GA4 gains a set of Search Console reports showing query data alongside behavior data — one of the few integrations that takes two minutes and pays off immediately.

Setup mistakes that poison your data

I'd estimate half the GA4 properties I inherit have at least one of these problems:

• Internal traffic not filtered. Your own team refreshing the homepage all day inflates everything. Define your office IPs as internal traffic and filter them.
• The tag firing twice. Common on WordPress when a plugin and a hardcoded snippet both load the tag — every metric doubles. If your engagement numbers look suspiciously heroic, check for this first. (More WordPress-specific pitfalls in our WordPress SEO guide.)
• No key events defined. Months of data, zero conversion tracking. You can't retroactively count conversions you never defined.
• Unwanted referrals. Payment gateways like Stripe or PayPal showing up as traffic sources, stealing attribution from the channel that actually drove the sale. Add them to the unwanted referrals list.
• Default data retention left at two months. GA4 ships with event-level data retention set to just two months, which quietly cripples year-over-year analysis in the Explore reports. Switch it to 14 months in the property settings on day one — the setting isn't retroactive, so every week you wait is a week of comparison data you never get back.

What Analytics can't tell you

GA4 measures behavior, not health. It won't tell you that 80 of your internal links return 404s, that a third of your pages are missing meta descriptions, or that your blog templates ship duplicate title tags. Those problems suppress the traffic before Analytics ever gets to measure it. That's a different discipline — and it's what a technical site audit is for. The pattern I recommend to every client: Analytics weekly for behavior, Search Console weekly for visibility, and an automated crawl on a schedule so technical regressions get caught within days instead of quarters.

One last honest note: GA4 has a real learning curve, and the interface frustrates people who knew Universal Analytics well. Push through it anyway. Making decisions about a website without measurement is guessing with extra steps.