Use the analytics report for a single page, blog post, or doc to see whether people are finding it, spending time on it, and taking the next step. Overview brings together health, traffic, audience, and search information. Heatmap shows where recorded clicks and scrolling occurred.
For a view across your whole site, start with Understanding your site analytics.
Open the right report
- Open Pages, Blogs, or Docs in your site's admin. For a blog post, use the Posts list.
- Find the item and select its analytics icon. Its tooltip starts with Open analytics for and includes the item's title.
- Check the title and route beneath it so you know which public address you are measuring.
- Choose Last 7 days, Last 14 days, Last 30 days, Last 60 days, Last 90 days, or All time from Reporting window. The initial selection is Last 30 days.
- Read Overview first, then open Heatmap when you want to examine clicks or scroll depth.
The report follows the public route, rather than a particular draft revision. A new draft needs published content and recorded visits before its intended public page can show useful activity. If you change an item's URL, do not assume activity from the old route moves into the new route's report.
Wait for the report to finish loading after changing the period. Previous figures can remain on screen during a refresh; if the refresh fails, use Try again before interpreting them as the newly selected period.
All time uses the available history for headline totals, but this report's Traffic chart still shows the most recent 30 days. Daily charts use UTC calendar days, while the selected day ranges use rolling windows ending now. A current day is still incomplete.
Read traffic, attention, and audience
The Overview tiles describe different parts of the page's performance:
- Page views counts recorded views of this route, including repeat views.
- Visitors counts distinct tracked visitor identities for the period. It is not a verified count of individual people; changing devices or browsers can create separate identities.
- Time on page shows the median measured active time. Half the measurements fall at or below the median. The supporting text gives the number measured and, when available, a “75% under” time. Active time reflects a visible, focused page, rather than proof that someone read or understood it.
- Call-to-action clicks shows tracked CTA activity alongside the recorded click total. A click does not confirm that an enquiry or purchase was completed.
- Search clicks uses Search Console data when available. Otherwise, Google landings names visits measured from Google referrers on your site.
The Traffic chart helps you see changes from day to day. Use the Visitors tile for the distinct visitor count across the whole period; adding daily visitor counts can count the same visitor more than once.
Under Audience, look at Acquisition channels, Top referrers, and Campaign terms when data is available. New and Returning describe tracked visitors, not the number of times they reloaded the page. Open Technology for available device, browser, and operating-system detail.
Start with a specific question. If a page has many views but few CTA clicks, inspect whether its next step is clear. If a campaign brings visitors who leave little recorded attention, check whether the page matches the promise in that campaign.
Use Health to find something you can improve
Health highlights findings from the page's SEO checks and measured speed. Expand SEO or Speed for the supporting detail.
SEO findings can identify issues such as missing or weak page metadata. Show … passing checks reveals checks that already pass. Where a finding offers Fix, select it to open the relevant editor field. Fix takes you to the place to make the change; it does not automatically rewrite or publish the page.
Speed uses measurements collected from real browser visits. It shows the available metrics, sample counts, ratings, and the proportion rated good. The main value for each metric is its 75th percentile: 75% of the measured values were at or below that value.
No field measurements yet means there is not enough recorded information to display those measurements. Opening the analytics screen does not run a synthetic speed test. Missing measurements are different from a failing measurement.
Use an All clear health result as a summary of the checks and measurements available, not a guarantee of search rankings or sales. Low traffic alone does not make a page unhealthy.
Separate search performance from Google referrals
Expand Search in Health and read its status before interpreting the numbers:
- Live means the report is using Search Console data. Review clicks, impressions, CTR, average position, and the available top queries. A lower average-position number is better.
- Not connected means Search Console has not been connected. Locally recorded Google landings may still be available.
- Local fallback means the report is using local referral information while waiting for a successful Search Console sync.
- Unavailable means the connection needs attention after a failed sync. Use Review connection to investigate it.
Local Google landings are visits observed by your site. They cannot tell you how often Google showed the page in search results. Do not read them as Search Console impressions or a complete list of search queries.
Check the reported search dates. Search data can lag behind site activity. Search Console trend lines and change chips use its reported history, which can be longer than the selected headline period; the report states that history's date span. The change chip is not necessarily a comparison with the immediately preceding reporting window.
If Search Console is not connected, Connect Search Console opens analytics settings. You can still use the page's local traffic and engagement information while the connection is being set up.
Explore clicks and scroll depth
Select Heatmap, then choose Clicks or Scroll depth. Both modes use the same embedded live page. Scroll within it to inspect content farther down.
Clicks shows areas where recorded clicks were concentrated. The legend identifies the busiest area's click count, so a strong color can be read against the actual amount of activity. A hotspot indicates interaction in an area; it does not prove that the interaction succeeded or produced a conversion.
Scroll depth shows how far recorded visitors reached and where reach fell between measured depth markers. Use it to investigate whether an important explanation or call-to-action sits beyond the point many visitors reach. Reaching a depth does not prove that the visitor read everything above it.
Read the summary and any small-sample caveat before acting. A few visitors can produce striking percentages without establishing a reliable pattern.
The background is the current live page, not a saved image of the page each visitor saw. Changes to layout or page length, and differences between visitors' screen sizes, can affect how historical activity lines up with it. Use the map as a guide to an area worth investigating, rather than an exact replay of an individual visit.
The embedded analytics preview is excluded from tracking and blocks ordinary link and form navigation. To inspect the public page separately, use the linked route beneath the report title when available. Clicking or scrolling inside the heatmap preview is not a way to populate an empty report.
Learn from doc helpfulness feedback
For a doc, Overview includes Page helpfulness. It shows Yes, helpful, No, not helpful, and Helpful rate for the selected period. Helpful rate is the share of recorded responses marked helpful, rather than the share of all readers.
The report keeps the latest response per identified visitor within the period. Collection follows the site's analytics consent and tracking settings, so responses represent the feedback that could be recorded.
When readers leave negative feedback, What readers were looking for shows up to 20 of the most recent written comments in the period. A negative vote does not require a comment, so the written-feedback list can be shorter than the negative-vote count.
Use repeated questions to decide what needs clarification. No helpfulness responses in this period yet is different from readers saying the doc was unhelpful.
Recover from missing data or a blocked heatmap
The report failed to load. Read the error and select Try again. Older results may remain visible after a failed refresh; they are not confirmation that the latest request succeeded.
The heatmap says the page did not render. Use Try again beside that message. If it continues, check whether the public route loads separately and whether it redirects or refuses to appear inside another page. An unavailable background is different from having no recorded clicks.
There are no clicks, scroll data, or speed samples. Check the route and period, whether the page is published, and whether built-in analytics is enabled in Settings → Analytics. Real visitors and allowed tracking are needed; consent choices and blocked requests can leave gaps.
You cannot access analytics or make a suggested edit. Ask the site owner to check your analytics/settings access and content-editing access. These are separate permissions. See feature access.
After making a change, publish it through the normal editor flow and allow time for new activity. Compare a similar period and audience before deciding whether it helped.