Measurement & search data

Search Console for Content Teams: The Reports, Filters and Routines That Matter

How content teams should use Google Search Console: which reports answer which content questions, how to read average position and anonymized queries correctly, the filters worth saving and a weekly, monthly and quarterly routine.

Ulrich Svarrer

November 15, 20269 min read

Search Console is the only place you get Google’s own record of how your pages perform in Google Search: which queries showed them, how often, where, and how many people clicked. This guide is for content teams rather than technical SEOs. It covers which report answers which content question, how to read the numbers without the common mistakes, the filters worth saving, how to answer five recurring questions, when you need more than the interface gives you, and a weekly, monthly and quarterly routine.

For how Search Console fits with GA4 and business metrics in a wider measurement framework, see how to measure content performance beyond traffic.

Which report answers which question

Search Console has many reports. A content team needs a handful, and mostly one:

Question	Report
How are our pages and topics doing in Search?	Performance (Search results), and the Insights summary
Which queries bring each page, and which could it win?	Performance, filtered to a page, Queries tab
Are our pages shown in AI Overviews and AI Mode?	Generative AI performance report, where available
Is Google indexing the pages we publish?	Page indexing, filtered to submitted pages
Has Google seen the update to this page?	URL Inspection
Which pages do we link to most internally?	Links, as a sample only

What Search Console does not tell you: what happens after the click (that is GA4), what competitors rank for, or search volume for queries you do not appear for. Use a keyword tool and the live results page for those.

Reading the numbers correctly

The Performance report has four metrics: clicks, impressions, CTR and average position. Each has a detail that changes how you should read it.

Detail	What Google documents	What it means for you
Average position	The topmost position your result held, averaged across the queries it appeared for	Not a rank. A page at 1 for one query and 20 for another averages about 10. Read position per query.
AI Overviews	Counted in the Web search type. The Overview occupies one position, and every link in it gets that position	A page cited in an Overview can show a high position and few clicks
Anonymized queries	Queries issued by very few people over two to three months have no row, but count in chart totals	Query rows never add up to the page total, especially for long-tail pages
By property vs by page	The chart counts one impression when several of your URLs appear on one results page; the Pages table counts each URL	Property-level CTR and position look better than page-level ones. Compare like with like
Fresh data	The newest data is preliminary and can change; the chart shows it as a dotted line	Do not judge yesterday against last week
Dates	Days are in Pacific Time; weeks run Sunday to Saturday	Day-level comparisons with GA4 in another time zone will not line up exactly
Rows shown	The interface shows and exports up to 1,000 rows per table	Large sites need the API, Looker Studio or the BigQuery export

The details come from Google’s definitions of impressions, position and clicks, its notes on the data and its deep dive on filtering and limits. The report keeps 16 months of data, so save dated exports if you want year-over-year comparisons further back.

The reports content teams use

Performance

The main report, with dimensions for queries, pages, countries, devices, search appearance and dates, and search types for Web, Image, Video and News. Web is now split into text-based and multimodal searches, such as searches with Lens or an uploaded image. Since late 2025 you can switch the chart between daily, weekly and monthly views, which makes trends on smaller pages much easier to read, and add your own annotations to the chart, such as “refreshed the payroll guide”, visible to everyone with access to the property.

Insights

A summary view inside Search Console since June 2025. It shows top and trending pages and queries, where “trending” is based on the absolute change in clicks, plus a branded and non-branded split. For sites with enough data it can also group similar queries together. It is the quickest way for a writer or editor to check their own pages without learning the full Performance report.

Generative AI performance

Since mid-2026, sites with enough impressions in Google’s AI features get separate reports for AI Overviews and AI Mode in Search, and for Discover. They show impressions only, by page, country, device and date, with no queries. The same activity is still counted in the regular Performance report under Web, as Google’s AI features documentation explains. Use the AI report to see which pages appear there, and the Performance report for clicks.

Page indexing, URL Inspection and Links

Page indexing: filter to “All submitted pages” to see only URLs from your sitemaps, then read the reasons for pages that are not indexed. “Crawled, currently not indexed” on important pages often points to thin or overlapping content.
URL Inspection: for one page, whether it is indexed, which canonical Google chose, when it was last crawled, and a button to request indexing after a substantial update.
Links: a sample of your most linked pages, internally and externally. Google says it is not a complete list, so use it to spot patterns, not to audit every link.

Filters worth saving

Filters can combine several dimensions, and query and page filters accept regular expressions. Google uses RE2 syntax; matches are partial unless you anchor them with ^ or $, and they ignore case. These cover most content work:

Purpose	Filter
Non-branded queries	The branded queries filter, where your site is eligible; otherwise Query, doesn’t match regex, `lumenpay\|lumen pay\|lumenpai` with your brand and its misspellings
One section	Page, matches regex, `/guides/`
Questions	Query, matches regex, `^(how\|what\|why\|when\|where\|which\|who\|can\|does\|is\|should)\b`
Long-tail queries (six words or more)	Query, matches regex, `^(\S+\s+){5,}\S+$`
Commercial modifiers	Query, matches regex, `best\|vs\|alternative\|review\|pricing\|cost`
Before and after an update	Date, compare, the 28 days after against the 28 days before
Seasonality check	Date, compare, last 3 months against the same 3 months last year

The branded queries filter, launched in November 2025, classifies queries with AI rather than a list of words, so it catches misspellings and product names, though Google notes it can misclassify. It is available for top-level properties, not subfolders or subdomains, with enough query volume. Comparison mode compares two values of one dimension at a time, such as two date ranges, and adds a difference column you can sort by.

Five content questions, answered in Search Console

1. Which pages are losing ground?

Performance, non-branded filter, compare the last 3 months with the same months last year, Pages tab, sort by the click difference. Then open the biggest losers one at a time and check their queries: losing the main query is more serious than losing the long tail. For the full method, see what content decay is and how to detect it.

2. Which queries could a page win?

Filter to the page, open the Queries tab, and sort by impressions. Queries with plenty of impressions at positions around 8 to 20 are the ones where the page is relevant but not the best answer. Check whether the page actually covers them; often it mentions the subject in passing.

3. Did the refresh work?

Annotate the date of the update. After at least four weeks, compare the 28 days after with the 28 days before, and also with the same period last year if the topic is seasonal. Look at the page’s queries, not only its total: a good refresh usually adds queries, not just clicks.

4. Are two of our pages competing?

Filter to an exact query and open the Pages tab. More than one URL with impressions, especially taking turns week by week, is the signal. For a whole site you need query-and-page pairs from the API. See how to find and fix keyword cannibalization.

5. What should we write next?

Look for queries with impressions where the landing page is a poor match: a broad guide showing for a specific question, or a blog post showing for a comparison query. Those are intents Google already associates with your site and no page fully serves. Check each against your keyword-to-page map before briefing a new page.

Morrison compares a week of non-branded Search Console data with the week before and finds the biggest movers and their queries; a weekly automation then emails the movers.

When the interface is not enough

The interface shows 1,000 rows per table and gives queries and pages as separate tables. For anything site-wide you will hit both limits.

Option	Limits	Use it for
Search Analytics API	Up to 25,000 rows per request, paginated; up to 50,000 rows per day per site and search type	Query-and-page pairs, automated reports, joining with other data
Looker Studio connector	Shares the same daily row limit as the API	Dashboards for stakeholders
Bulk data export to BigQuery	A daily export of all data except anonymized queries; needs a Google Cloud project	Large sites, long history beyond 16 months, heavy analysis

Whichever you use, start early. Search Console keeps 16 months of data, so anything you have not exported by then is gone for good.

A routine for content teams

When	Check	Who
Weekly, 15 minutes	Insights for trending pages and queries; biggest non-branded movers week over week; anything newly published indexed?	Content lead
Monthly	Pages losing clicks over the last 3 months year over year; queries at positions 8 to 20 for priority pages; Page indexing for submitted pages	Content and SEO
After each refresh or merge	Annotation on the day; URL Inspection; before-and-after comparison at four weeks and three months	The editor who made the change
Quarterly	Cannibalization check from query-and-page pairs; keyword map against what ranks; AI feature impressions by page	SEO

Common mistakes

Treating average position as a rank, especially at site level.
Summing query rows and expecting them to match the page total.
Leaving branded queries in when judging content performance; they hold up on their own and hide losses.
Judging changes too early, on preliminary data or before Google has recrawled the page.
Following outdated advice: the URL Parameters tool was retired in 2022, and the old Coverage report is now Page indexing.

Where Morrison fits

Morrison connects to Search Console and queries it directly: exact totals and trends for the whole site or any section, broken down by date, country, device or search appearance, plus query-and-page pairs, URL inspection and sitemaps. So you can ask questions like the five above in plain language and get the table back, joined with what Morrison knows about each page from its site index: page type, search intent and HTTP status. The URL grid shows 90 days of clicks and impressions for every page. Recurring checks can run as automations that email a written summary: weekly or monthly on Starter, up to daily on Pro. See integrations and SERP visibility use cases.

Key takeaways

One report does most of the work: Performance, with Insights as the quick view.
Know the data’s rules: average position is not a rank, anonymized queries are left out of rows, AI Overviews count under Web.
Save a few filters: non-branded, one section, questions, long tail, before and after.
Go beyond 1,000 rows with the API, Looker Studio or BigQuery, and start exports early.
Make it a routine: weekly movers, monthly losers, checks after every change.

Sources and further reading