WEBSITE PLANNING

Compare Landing Pages Without Confusing Pageviews

Separate the page that starts a visit from pages viewed later when judging acquisition and navigation.

Name the business question

Which pages bring people into the site is different from which pages they view once there. GA4’s landing-page dimension describes the first pageview in a session. A pageview count can include later activity. Decide whether you are studying entrances, reading behavior or an inquiry path before selecting the report.

Follow one hypothetical visit

Imagine someone enters on a service guide, opens pricing and then reads the contact page. The guide is the landing page for that session; all three pages can contribute viewing activity. High contact-page views therefore do not automatically mean people discovered the business through that page. This is a conceptual example, not a measurement claim about your site.

Build two small tables

For acquisition, use landing page, sessions, relevant channel and the outcome you can actually measure. For navigation, review pages viewed and the path toward the next step. Keep dates, hostname and filters aligned. If the organic-search filter returns no accessible rows, label that limitation rather than reporting a verified zero without checking data availability.

Turn the result into a targeted change

A useful entry guide with weak onward navigation may need a clearer link to the relevant service. A heavily viewed contact page with an unclear request process may need a usability correction. Those are separate hypotheses. Record the changed page and expected behavior, then review comparable sessions later. Do not credit a page with sales solely because it appears somewhere in a visit.

Apply this to your website

Bring the relevant URL and a description of the decision to request a scoped website review. Do not send passwords or private customer records. The primary reference is the linked technical guidance.