Documentation
Pages
Clicks, impressions, CTR and position for every URL Search Console credits, with a full-URL switch and a detail view of the queries behind each page.
The Pages report lists every URL on your property that earned impressions in the selected range, with its clicks, impressions, CTR and average position, compared with the earlier period. It answers which pages carry your search traffic, which are gaining or losing it, and which queries each page is found for.
Reading the table
URLs are shortened to their path so the column stays readable; pages on a subdomain keep the subdomain in front. Tick Show full URL to see complete addresses in every table on the page. Columns are Page, Clicks, Impressions, CTR (from the column button), Avg Ranking and, when comparing, Prev Ranking, with All, Winning and Losing tabs.
Search Console credits each result to the canonical URL Google chose: "Click, impression, and position data for all variations of a page are assigned to the canonical URL" (Google's definitions). If an address you expected is missing, Google may treat another URL as the canonical one; URL Inspection shows which.
Page detail
Click a page to open Page detail: its headline numbers, a daily trend, the Queries driving this page, and its countries and devices. Open loads the live page in a new tab. The query list is where you see what a page is really found for, which is often broader than, or different from, what it was written for.
Practical uses
- Pages losing traffic. The Losing tab, sorted by clicks, lists the pages that fell most in absolute terms. Open one to see which queries went with it, then compare with Content Decay.
- Pages with views but no clicks. High impressions with a low CTR at a decent position often means the title and description lose the click to other results.
- Sections rather than single pages. Bundle URLs by folder or pattern with Content Groups to follow a blog, a product range or a language as a whole.
- Articles from the content engine. Each content type publishes under a path of its own, so filtering Page on that path (for example
/answers/) shows how the engine's articles perform; the engine itself refreshes and optimises them as described in keeping articles fresh.