` — useful when one path serves many titles. | | **Entries** | **Entry pages** — the first page of each session, ranked by how many sessions start there. | | **Exits** | **Exit pages** — the last page of each session, ranked by how many sessions end there. | | **Hostnames** | Traffic by hostname — useful when one site tracks several domains or subdomains. | ## When should I use URL mode? Use **URLs** when one site serves the same path from more than one hostname — a marketing site and an app on `example.com` and `app.example.com`, or a staging subdomain sharing a path with production. By default the report is in **Pages** (path) mode, which groups `example.com/pricing` and `app.example.com/pricing` into a single `/pricing` row. Switching to **URLs** splits them into one row per hostname-and-path pair. Selecting the **URLs** tab turns URL mode on, and selecting **Pages** turns it back off. While it's on, the **Entries** and **Exits** views become host-aware too, and their headings read **Entry URLs** and **Exit URLs**. <Tip> When your selected date range contains more than one hostname, tinyanalytics shows a banner above the report offering to **Switch to URL**. Dismissing it hides it for your current visit only. </Tip> <Note> URL mode travels in the page address as `?pagesMode=url`, so a dashboard link you copy and share reopens in URL mode for whoever you send it to. Hostnames are matched in lowercase, and `www.example.com` and `example.com` are **not** merged — they rank as separate rows. </Note> ## How do I show the hostname without splitting rows? Turn on **Show full URL** to display each row as `hostname/pathname` while keeping the Pages report grouped by path. The switch appears when the current page rows contain more than one hostname. This display option is useful when you want hostname context without changing the report's grouping. It also makes the row's external link open the displayed hostname. Because the row still represents a path grouped across hostnames, tinyanalytics shows its latest representative hostname; it does not split traffic by host. <Tip> Use **Show full URL** for context. Use the **URLs** tab when `example.com/pricing` and `app.example.com/pricing` must become separate rows with separate metrics. </Tip> ## How do I read the Landing pages report? A **landing page** is the first page a visitor sees in a session — where the visit begins. The **Landing pages** report ranks your entry pages and adds the engagement metrics that tell you whether each one actually holds attention: | Column | What it means | | ----------------- | --------------------------------------------------------------------- | | **Landing page** | The path where sessions started, with a link to open it. | | **Trend** | A sparkline of sessions starting on this page over your date range. | | **Sessions** | Sessions that began here, with the change versus the previous period. | | **Bounce** | The share of those sessions that viewed only this one page and left. | | **Avg. duration** | How long those sessions lasted on average. | | **Avg. scroll** | How far down the landing page visitors scrolled on average. | | **Avg. time** | The average time spent on the landing page itself. | <Accordion title="How bounce and missing engagement values are calculated"> Bounce here is measured against each session's **real, unfiltered pageview count** — so applying a dashboard filter can't inflate or deflate it. Missing engagement data shows as "—" rather than zero, so a page with no scroll signal isn't mistaken for one nobody scrolled. </Accordion> <Tip> Read landing pages to judge your **acquisition quality**, not just volume: a page that draws many sessions but bounces most of them is pulling the wrong traffic — or making the wrong first impression. </Tip> ## How do I see one page's full stats? **Click a row to open the main dashboard already filtered to that page.** Every metric, chart, and breakdown is scoped to visitors who saw it, so you land on a complete picture of how that one page performs. Your current date range and any other active filters come along with you. Because the click navigates rather than toggling a filter in place, you clear it the way you clear any filter — remove the page filter on the dashboard, or use your browser's Back button. See [filter your data](/docs/analytics-filters). In **URLs** mode a row click applies **two** filters together, hostname and path, so you scope to that exact URL rather than to the path across every host. <Warning> A click on an **Entries** row filters by **entry page** — sessions that *started* there — not by sessions that viewed the page at any point. The **Exits** view still filters by pages *visited*, so an Exits row click and an Entries row click don't mean the same thing. </Warning> ## Common workflows * **Find your top content.** The default ranking shows which pages drive the most traffic. * **Check a page's momentum.** Read the trend sparkline to see whether a page is gaining or losing visits. * **Drill into one page.** Click a page to open the dashboard filtered to it, and read its sources, devices, and geography in the [Overview](/docs/web-analytics-dashboard) breakdowns. * **Separate two hostnames.** Switch to the **URLs** view when the same path is served from several domains or subdomains. ## Frequently asked questions <AccordionGroup> <Accordion title="How are pages ranked in the Pages report?"> Pages are ranked by visitors, most-visited first. Each row shows the page's title and path, a trend sparkline over your selected date range, the number of distinct sessions that viewed it, and its total pageviews. </Accordion> <Accordion title="What's the difference between the Pages and Titles views?"> The Pages view ranks pages by their path, which is the standard read of your top content. The Titles view ranks them by their HTML `<title>` instead, which is useful when one path serves many titles. Both views re-slice the same traffic by a different key. </Accordion> <Accordion title="What's the difference between an entry page and an exit page?"> An entry page is the first page of a session and an exit page is the last. In the tinyanalytics Pages report, the **Entries** view ranks pages by how many sessions start there, and the **Exits** view ranks them by how many sessions end there. </Accordion> <Accordion title="How do I see stats for a single page?"> Click that page's row in the Pages report. tinyanalytics opens the main dashboard already filtered to that page, carrying your date range and any other active filters with it, so you can read its sources, devices, and geography. The click navigates rather than toggling a filter in place, so you clear it by removing the page filter on the dashboard or using your browser's Back button. See [filter your data](/docs/analytics-filters). </Accordion> <Accordion title="Why do two hostnames share one row in the Pages report?"> The report groups by path by default, so `example.com/pricing` and `app.example.com/pricing` combine into one `/pricing` row. Switch to the **URLs** tab to group by host and path together and see them separately. When your date range contains more than one hostname, tinyanalytics offers this switch in a banner above the report. </Accordion> <Accordion title="What's the difference between Show full URL and the URLs tab?"> **Show full URL** adds a representative hostname to each displayed path but keeps traffic grouped by path. The **URLs** tab changes the grouping to hostname plus path, so the same path on two hostnames becomes two rows with separate metrics. </Accordion> </AccordionGroup> ## Related <Columns cols={2}> <Card title="Dashboard overview" icon="gauge" href="/docs/web-analytics-dashboard"> Top-line metrics and breakdowns for your whole site. </Card> <Card title="Sessions" icon="list-timeline" href="/docs/session-analytics"> See the visits behind the pageviews. </Card> <Card title="Journeys" icon="diagram-project" href="/docs/user-journey-analytics"> See the paths visitors take between pages. </Card> <Card title="Filter your data" icon="filter" href="/docs/analytics-filters"> Narrow reports to a page, source, or country. </Card> </Columns> ## Related topics - [Session Analytics](/docs/session-analytics.md) - [Analytics Alerts](/docs/analytics-alerts.md) - [User Journey Analytics](/docs/user-journey-analytics.md)

> ## Documentation Index > Fetch the complete documentation index at: https://tinyanalytics.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Page Analytics > Rank pages by visitors, pageviews, and trends, then analyze URLs, titles, entries, exits, hostnames, and landing-page engagement. The Pages report ranks your site's pages by how many people visit them. Each row is a page, with its number of visitors, its pageviews, and a small trend sparkline, so you can see your top content at a glance and how each page is trending. ## What each column means | Column | What it means | | ------------- | ----------------------------------------------------------------- | | **Page** | The page's title and its path, with a link to open the live page. | | **Trend** | A sparkline of the page's visits over your selected date range. | | **Sessions** | The number of distinct sessions that viewed the page. | | **Pageviews** | The total number of times the page was viewed. | Pages are ranked by visitors, most-visited first. ## How do I switch to URLs, titles, entries, exits, or hostnames? The Pages section has tabs that re-slice the same traffic by a different key, so you can answer different questions from one place: | View | What it ranks | | ------------- | ------------------------------------------------------------------------------------------ | | **Pages** | Pages by path — your top content. | | **URLs** | Pages by host **and** path together, so the same path on two hostnames stays separate. | | **Titles** | Pages by their `` — useful when one path serves many titles. | | **Entries** | **Entry pages** — the first page of each session, ranked by how many sessions start there. | | **Exits** | **Exit pages** — the last page of each session, ranked by how many sessions end there. | | **Hostnames** | Traffic by hostname — useful when one site tracks several domains or subdomains. | ## When should I use URL mode? Use **URLs** when one site serves the same path from more than one hostname — a marketing site and an app on `example.com` and `app.example.com`, or a staging subdomain sharing a path with production. By default the report is in **Pages** (path) mode, which groups `example.com/pricing` and `app.example.com/pricing` into a single `/pricing` row. Switching to **URLs** splits them into one row per hostname-and-path pair. Selecting the **URLs** tab turns URL mode on, and selecting **Pages** turns it back off. While it's on, the **Entries** and **Exits** views become host-aware too, and their headings read **Entry URLs** and **Exit URLs**. <Tip> When your selected date range contains more than one hostname, tinyanalytics shows a banner above the report offering to **Switch to URL**. Dismissing it hides it for your current visit only. </Tip> <Note> URL mode travels in the page address as `?pagesMode=url`, so a dashboard link you copy and share reopens in URL mode for whoever you send it to. Hostnames are matched in lowercase, and `www.example.com` and `example.com` are **not** merged — they rank as separate rows. </Note> ## How do I show the hostname without splitting rows? Turn on **Show full URL** to display each row as `hostname/pathname` while keeping the Pages report grouped by path. The switch appears when the current page rows contain more than one hostname. This display option is useful when you want hostname context without changing the report's grouping. It also makes the row's external link open the displayed hostname. Because the row still represents a path grouped across hostnames, tinyanalytics shows its latest representative hostname; it does not split traffic by host. <Tip> Use **Show full URL** for context. Use the **URLs** tab when `example.com/pricing` and `app.example.com/pricing` must become separate rows with separate metrics. </Tip> ## How do I read the Landing pages report? A **landing page** is the first page a visitor sees in a session — where the visit begins. The **Landing pages** report ranks your entry pages and adds the engagement metrics that tell you whether each one actually holds attention: | Column | What it means | | ----------------- | --------------------------------------------------------------------- | | **Landing page** | The path where sessions started, with a link to open it. | | **Trend** | A sparkline of sessions starting on this page over your date range. | | **Sessions** | Sessions that began here, with the change versus the previous period. | | **Bounce** | The share of those sessions that viewed only this one page and left. | | **Avg. duration** | How long those sessions lasted on average. | | **Avg. scroll** | How far down the landing page visitors scrolled on average. | | **Avg. time** | The average time spent on the landing page itself. | <Accordion title="How bounce and missing engagement values are calculated"> Bounce here is measured against each session's **real, unfiltered pageview count** — so applying a dashboard filter can't inflate or deflate it. Missing engagement data shows as "—" rather than zero, so a page with no scroll signal isn't mistaken for one nobody scrolled. </Accordion> <Tip> Read landing pages to judge your **acquisition quality**, not just volume: a page that draws many sessions but bounces most of them is pulling the wrong traffic — or making the wrong first impression. </Tip> ## How do I see one page's full stats? **Click a row to open the main dashboard already filtered to that page.** Every metric, chart, and breakdown is scoped to visitors who saw it, so you land on a complete picture of how that one page performs. Your current date range and any other active filters come along with you. Because the click navigates rather than toggling a filter in place, you clear it the way you clear any filter — remove the page filter on the dashboard, or use your browser's Back button. See [filter your data](/docs/analytics-filters). In **URLs** mode a row click applies **two** filters together, hostname and path, so you scope to that exact URL rather than to the path across every host. <Warning> A click on an **Entries** row filters by **entry page** — sessions that *started* there — not by sessions that viewed the page at any point. The **Exits** view still filters by pages *visited*, so an Exits row click and an Entries row click don't mean the same thing. </Warning> ## Common workflows * **Find your top content.** The default ranking shows which pages drive the most traffic. * **Check a page's momentum.** Read the trend sparkline to see whether a page is gaining or losing visits. * **Drill into one page.** Click a page to open the dashboard filtered to it, and read its sources, devices, and geography in the [Overview](/docs/web-analytics-dashboard) breakdowns. * **Separate two hostnames.** Switch to the **URLs** view when the same path is served from several domains or subdomains. ## Frequently asked questions <AccordionGroup> <Accordion title="How are pages ranked in the Pages report?"> Pages are ranked by visitors, most-visited first. Each row shows the page's title and path, a trend sparkline over your selected date range, the number of distinct sessions that viewed it, and its total pageviews. </Accordion> <Accordion title="What's the difference between the Pages and Titles views?"> The Pages view ranks pages by their path, which is the standard read of your top content. The Titles view ranks them by their HTML `<title>` instead, which is useful when one path serves many titles. Both views re-slice the same traffic by a different key. </Accordion> <Accordion title="What's the difference between an entry page and an exit page?"> An entry page is the first page of a session and an exit page is the last. In the tinyanalytics Pages report, the **Entries** view ranks pages by how many sessions start there, and the **Exits** view ranks them by how many sessions end there. </Accordion> <Accordion title="How do I see stats for a single page?"> Click that page's row in the Pages report. tinyanalytics opens the main dashboard already filtered to that page, carrying your date range and any other active filters with it, so you can read its sources, devices, and geography. The click navigates rather than toggling a filter in place, so you clear it by removing the page filter on the dashboard or using your browser's Back button. See [filter your data](/docs/analytics-filters). </Accordion> <Accordion title="Why do two hostnames share one row in the Pages report?"> The report groups by path by default, so `example.com/pricing` and `app.example.com/pricing` combine into one `/pricing` row. Switch to the **URLs** tab to group by host and path together and see them separately. When your date range contains more than one hostname, tinyanalytics offers this switch in a banner above the report. </Accordion> <Accordion title="What's the difference between Show full URL and the URLs tab?"> **Show full URL** adds a representative hostname to each displayed path but keeps traffic grouped by path. The **URLs** tab changes the grouping to hostname plus path, so the same path on two hostnames becomes two rows with separate metrics. </Accordion> </AccordionGroup> ## Related <Columns cols={2}> <Card title="Dashboard overview" icon="gauge" href="/docs/web-analytics-dashboard"> Top-line metrics and breakdowns for your whole site. </Card> <Card title="Sessions" icon="list-timeline" href="/docs/session-analytics"> See the visits behind the pageviews. </Card> <Card title="Journeys" icon="diagram-project" href="/docs/user-journey-analytics"> See the paths visitors take between pages. </Card> <Card title="Filter your data" icon="filter" href="/docs/analytics-filters"> Narrow reports to a page, source, or country. </Card> </Columns> ## Related topics - [Session Analytics](/docs/session-analytics.md) - [Analytics Alerts](/docs/analytics-alerts.md) - [User Journey Analytics](/docs/user-journey-analytics.md)