Query and page views
In plain English: Queries describe searches; pages describe the URLs credited with performance.
Open Queries to find terms associated with impressions and clicks. Open Pages to find canonical URLs receiving visibility. Because most data is assigned to canonical URLs, duplicate URLs may not receive separate rows.
- Query: css gradient generator
- Page: https://example.com/tools/css-gradient
Combine the dimensions
In plain English: Filter a page, then inspect Queries to learn what that page appears for.
Select a page row or add an exact page filter, then switch to Queries. Reverse the workflow to see which pages Google showed for one query. Use country, device, search type and appearance filters when they answer a real question.
Dates and comparisons
In plain English: Compare equivalent periods and read changes with context.
A week-over-week comparison can be distorted by weekends, launches or seasonality. A year-over-year comparison can be more useful for seasonal sites. Check whether the latest data is preliminary before treating a small change as final.
Why query totals do not reconcile
In plain English: The table is not a complete list of every search term.
Search Console omits anonymised queries to protect privacy and retains only a limited set of the most significant rows. Omitted queries can still contribute to chart totals unless a query filter changes the aggregation.
Do not invent labels for the missing difference or claim every user query is available.
Keep in mind: Property and page aggregation rules can also make chart and table totals differ.