Let’s begin by looking at the “All Pages” report located under “Site Content” and scroll down to the data table.
- The “Pageviews” metric shows how frequently each page on your site was viewed. By default, this report will show data by the page URI. The URI is the part of the URL after the domain name in the location bar of the browser. If you switch the primary dimension of the report to “Page Title,” you can view this report by the title listed in the web page’s HTML.
- Other metrics in the “All Pages” report like “Average Time on Page” and “Bounce Rate” indicate how engaged users were on each page of your site. You can sort the report by these metrics to quickly find low-performing pages that need improvement or high-performing content to guide future content decisions.
The “Content Drilldown” report under “Site Content” groups pages according to your website’s directory structure. You can click on a directory to see the pages of your site within that directory. This is especially useful if you’re trying to understand the performance of content in a particular section of your website. If you switch to the pie chart view, you can quickly see which sections of your site are most popular with your users.
The “Landing Pages” report under “Site Content” lists the pages of your website where users first arrived. These are the first pages viewed in a session. You can use this report to monitor the number of bounces and the bounce rate for each landing page. A high bounce rate usually indicates that the landing page content is not relevant or engaging for those users.
The “Exit Pages” report under “Site Content” shows the pages where users left your site. Because you don’t want users exiting from important pages like a shopping cart checkout, it’s a good idea to periodically review this report to minimize unwanted exits.
The “Events” report tracks how users interact with specific elements of your website. For example, you can use this report to track when users click on a video player or a download link. Event tracking requires additional implementation beyond the Analytics tracking code snippet, which we’ll discuss in more detail in an advanced Google Analytics course.