News tab vs Google News reporting

Separate the Search News tab from news.google.com and the Google News apps.

Automatable now Intermediate

Search Console divides news visibility by the Google surface where a result appeared. The News search type in the Search results Performance report measures the News tab in Google Search. The separate Google News Performance report measures news.google.com and the Google News apps on Android and iOS.

News articles appearing in Google's default Web results—including eligible news features in the All tab—belong to the Web search type instead. The three sources must be queried and reported separately.

This guide reflects Google's documentation on July 18, 2026.

The reporting map

User surface Search Console interface API type Bulk-export search_type
Default Google Search results, including news content in the All tab Performance → Search results → Search type: Web web web
News tab in Google Search Performance → Search results → Search type: News news news
news.google.com and Google News Android/iOS apps Performance → Google News googleNews googleNews

Do not call the News-tab filter the “Google News report.” In Search Console documentation, Google News specifically means the separate app-and-website surface.

Three contexts for the same article

One canonical article can receive traffic from all three contexts:

  1. A result in the default Web/All tab.
  2. A result after the user selects Google's News tab.
  3. A recommendation or result on news.google.com or in a Google News app.

Each context has its own counting event and audience behavior. Summing them can answer “all measured Google news-related traffic,” but only after keeping the source label attached to every row. A combined number should never be presented as though it were one native Search Console metric.

Top Stories does not mean Search type: News

The search type describes the Google results tab, not the editorial format of the page.

If an article appears in a Top Stories or another news feature inside the default All tab, its traffic is part of the Web search type. It becomes news only when the result is in the dedicated News tab. Traffic from the Google News website or apps is googleNews.

When a publisher says “news traffic dropped,” ask which of these sources changed before opening a report.

News-tab reporting

Open Performance → Search results and select Search type → News.

This is still a Google Search results report. It can provide:

  • Clicks.
  • Impressions.
  • CTR.
  • Average position.
  • Query, page, country, device, date, and applicable appearance analysis.

The query dimension is meaningful because a user performed a Google Search and then viewed the News results tab.

News-tab impression rules

Google documents News-tab results as paged results, like ordinary text results. All eligible links on the current results page receive an impression whether or not the user scrolls each link into view.

This differs from the Google News app/site report, where a card must be scrolled into view.

News-tab position

Standard Google Search position rules apply. Average position is the average topmost position attributed to the property or page for recorded impressions under the chosen aggregation.

Position does not mean:

  • A fixed rank for every user.
  • The row number visible in a manual check.
  • The position of the article in the Google News app.
  • A direct measure of article quality.

Location, language, device, time, personalization, query mix, result layouts, and property-versus-page aggregation can all affect it.

Google News app and website reporting

The separate Performance → Google News report covers:

  • news.google.com.
  • The Google News Android app.
  • The Google News iOS app.

It explicitly excludes the News tab in Google Search.

The report exposes:

  • Clicks.
  • Impressions.
  • CTR.
  • Page.
  • Country.
  • Date.
  • Device.
  • Google News appearance.

It does not expose query or average position. Google News is not measured as a conventional query-ranked Search results page.

Google News counting rules

Impressions

An impression is recorded when a link to the site is scrolled into view in Google News. Scrolling away and back, or paging away and back, does not produce another impression for the same item during the session.

Clicks

A click is recorded when the Google News item sends the user to the property.

Google excludes:

  • Left or right in-article swipes between articles inside the Android and iOS apps.
  • Google News notification interactions.

Those exclusions explain some differences between Search Console, publisher analytics, and internal app-referral estimates.

CTR

CTR is clicks divided by impressions. Because Google News and the News tab count impressions differently, their CTR values are not directly comparable measures of headline quality.

The News tab can count an impression for a result on the current page before it is scrolled into view. Google News requires the item to be scrolled into view. A higher Google News CTR can partly reflect the different denominator rather than a superior preview.

No position

Position is recorded only for Google Search results. The Google News report has no average-position metric.

Do not manufacture one from feed order. A personalized, changing news feed does not provide the stable positional model implied by Search Console's Search position metric.

Why the Google News report may be missing

Search Console shows the separate Google News report only when the property has sufficient Google News traffic. Google does not publish a numeric threshold.

A missing report can mean:

  • No recorded Google News app/site impressions.
  • Traffic exists but is below the report-visibility threshold.
  • Canonical URLs belong to another Search Console property.
  • Relevant data is outside the selected or available period.
  • Articles are not indexed, discoverable, or eligible for news surfaces.
  • A new property has not accumulated enough reporting evidence.

It does not prove that the publisher was rejected, that no article has appeared in the News tab, or that Publisher Center setup is incomplete.

The News-tab search type is a different data source. A site can have News-tab traffic without qualifying for the separate Google News navigation report, or Google News app traffic without material News-tab traffic.

Canonical attribution and property boundaries

Google News page metrics are assigned to Google's selected canonical URL, not necessarily the URL a user lands on after clicking.

Consequences:

  • Duplicate and alternate URLs can show zero.
  • A canonical in another protocol, subdomain, or domain property receives the data.
  • A directory property can miss traffic when its pages canonicalize outside the directory.
  • Mobile and desktop variants can consolidate under one canonical.
  • Cross-domain syndication can move reporting to the selected source URL.

When a publisher cannot find an article in the report:

  1. Inspect the article URL.
  2. Record Google's selected canonical.
  3. Open the Search Console property containing that canonical.
  4. Use an exact canonical-page filter for the same period.

Do not add duplicate-property totals without first resolving overlapping canonical scope.

Page and property aggregation

The Google News report is page-oriented, but chart and table totals can still differ under certain groupings.

  • The chart can count the property once in a session context.
  • A page-grouped table can count several distinct URLs from that property.
  • Page filters change how data is truncated and served.
  • The table exposes at most 1,000 rows.

Google advises treating the chart total as more complete than a manual sum of table rows. If chart and table disagree, retain both the selected dimensions and aggregation context in the analysis.

The 1,000-row interface limit

The Google News table is truncated to 1,000 rows before it reaches the interface. Reversing the table sort does not reveal row 1,001.

This means:

  • The visible Pages table is not a complete article inventory.
  • Table rows may not sum to chart totals.
  • A CSV or Sheets export of the UI inherits the same row boundary.
  • Long-tail country, device, and page combinations can be absent.

Use Search Analytics API pagination or BigQuery bulk export for larger analyses, while respecting their own privacy and top-row limitations.

Time, freshness, and comparisons

The default Google News date range is three months. Current views support hourly, daily, weekly, and monthly granularity where applicable.

  • The 24-hour view uses the browser's local time and contains preliminary hourly data.
  • Other views use Pacific Time.
  • Today and sometimes yesterday can remain preliminary.
  • Preliminary points are shown with a dotted line.
  • Weeks run Sunday through Saturday.
  • Months are calendar months.

The report normally takes time to publish finalized data, and Google notes that data is generally available within two to three days.

Before comparing Search Console with analytics:

  1. Align time zones.
  2. Exclude or label preliminary dates.
  3. Compare the same canonical URL set.
  4. Separate News tab from Google News referrals.
  5. Account for consent, blockers, redirects, and failed page loads.
  6. Remember that notifications and in-app swipes are excluded from the Search Console Google News metrics.

Dimensions and their limits

Page

Page is the canonical article URL credited with the result. Use it to find winners, losers, new entrants, and traffic concentration.

For a useful editorial comparison, classify pages by:

  • Section or desk.
  • Publication date.
  • Article type.
  • Author or newsroom team.
  • Evergreen versus breaking news.
  • Original reporting versus commentary or aggregation.

Those attributes must come from publisher data; Search Console does not expose them natively.

Country

Country describes where the content was viewed or clicked. It does not directly identify language, edition, residence, or intended market.

Segment country before explaining a site-wide change because geographic news demand and distribution can change independently.

Device

Device describes the device type on which the Google News item was viewed. It does not tell you whether the user was on news.google.com versus an Android or iOS app.

Do not use device as a platform surrogate. A mobile view can occur on the web, and the report does not provide an operating-system or app-versus-web dimension.

Date

Use daily data for incident diagnosis and weekly or monthly aggregation for durable trends. Avoid comparing an incomplete first or last week with a full period.

Google News appearance

The current documented appearance is News Showcase:

UI name API value Bulk-export appearance field
News Showcase NEWS_SHOWCASE Not supported

News Showcase indicates an article in a publisher-curated Showcase panel. It is not a label for every Google News article.

Search Analytics API

The same Search Analytics endpoint can query both surfaces by changing type.

News tab

{
  "startDate": "2026-06-01",
  "endDate": "2026-06-30",
  "type": "news",
  "dimensions": ["date", "page", "query"],
  "rowLimit": 25000,
  "startRow": 0
}

Google News apps and website

{
  "startDate": "2026-06-01",
  "endDate": "2026-06-30",
  "type": "googleNews",
  "dimensions": ["date", "page", "country", "device"],
  "rowLimit": 25000,
  "startRow": 0
}

Important API boundaries:

  • Use type; the older searchType request property is deprecated.
  • type: "news" means the Search News tab.
  • type: "googleNews" means news.google.com and the apps.
  • type: "web" means the default Search All tab and excludes Google News.
  • byProperty aggregation is not supported for type: "googleNews".
  • The API returns at most 25,000 rows per request and supports startRow pagination.
  • Search Analytics returns top rows and does not guarantee every possible row.
  • Use dataState: "all" for fresh daily data and hourly_all for incomplete hourly data.

For News Showcase, filter searchAppearance to NEWS_SHOWCASE. The special byNewsShowcasePanel aggregation can be used only with that appearance and type: "googleNews" or type: "discover", subject to Google's grouping restrictions.

BigQuery bulk export

Bulk export stores the two surfaces as distinct search_type values:

  • news for the Search News tab.
  • googleNews for news.google.com and the Google News apps.

Always aggregate exported metrics because Search Console can write several rows with the same apparent keys.

SELECT
  data_date,
  search_type,
  url,
  SUM(impressions) AS impressions,
  SUM(clicks) AS clicks,
  SAFE_DIVIDE(SUM(clicks), SUM(impressions)) AS ctr
FROM `project.searchconsole.searchdata_url_impression`
WHERE search_type IN ('news', 'googleNews')
  AND data_date BETWEEN DATE '2026-06-01' AND DATE '2026-06-30'
GROUP BY data_date, search_type, url
ORDER BY impressions DESC;

Position fields exist in the shared export schema, but position is meaningful only for Google Search results. Do not calculate or publish a Google News app/site average position from googleNews rows.

Bulk export does not provide a dedicated News Showcase appearance field. Use the API or interface for that segmentation.

Publisher Center is not an inclusion gate

Publishers do not need to submit a site to qualify for Google News surfaces. Google's systems discover and rank eligible news content automatically, subject to crawling, indexing, and policy requirements.

In March 2025, Google News completed its transition to automatically generated publication pages:

  • Manually created publication pages stopped appearing.
  • Google News stopped using RSS feeds and web locations submitted through Publisher Center for those pages.
  • The Google News publication tile and nonessential page customization were discontinued.
  • Google News began using site favicons and site names for publication branding.

Publisher Center remains relevant for products such as Reader Revenue Manager and News Showcase, but creating a Publisher Center publication is not a way to force Google News inclusion or make the Search Console report appear.

Eligibility and policy evidence

Google automatically considers web content for news surfaces, but eligibility requires compliance with Google Search and Google News policies.

News-specific expectations include:

  • Clear dates and bylines.
  • Information about authors, the publication, and the publisher.
  • Information about the company or network behind the content.
  • Contact information.
  • Clear disclosure of sponsorship, ownership interests, affiliate relationships, payment, or material support.
  • No preview content that promises details absent from the article.
  • Advertising and paid promotion that do not overwhelm editorial content.

Google can remove individual content or make a site ineligible for news surfaces after repeated or serious violations. A news-surface restriction does not automatically mean the page is ineligible everywhere else in Search.

Check Security & Manual Actions in Search Console for explicit news-related actions. Do not infer a manual action solely from traffic loss.

A reliable reporting workflow

1. Name every surface

Use Web, News tab, and Google News as distinct source labels in dashboards, exports, and stakeholder reports.

2. Reconcile canonical inventory

Map CMS article IDs and live URLs to Google's selected canonicals. Preserve publication date, section, language, and migration history outside Search Console.

3. Analyze totals before rows

Record the native chart total for each source. Then segment by page, country, device, date, and supported appearance without assuming the visible table is exhaustive.

4. Compare matched periods

Use finalized Pacific-Time dates or intentionally normalized hourly data. Prefer full weeks when day-of-week publishing patterns are strong.

5. Separate reach from response

  • Impressions measure recorded exposure under each surface's counting rule.
  • CTR measures response to that exposure.
  • Clicks combine both reach and response.

A click loss driven by impressions requires a different investigation from stable impressions and falling CTR.

6. Add editorial and technical context

Annotate major stories, publishing cadence, elections, sports events, seasonality, template changes, migrations, indexing incidents, policy changes, and Google data anomalies.

Diagnose a drop by source

Web falls, News tab and Google News remain stable

Investigate default Search visibility, query demand, result features, canonical changes, and general Search ranking systems. Do not blame Google News distribution.

News tab falls, Web remains stable

Segment News-tab queries, countries, devices, pages, and average position. Review freshness, topical competition, article eligibility, and whether the change is concentrated in a desk or event.

Google News falls, News tab remains stable

Check app/site impression reach, country and device mix, canonical ownership, News Showcase, policy evidence, and whether a former feed recommendation spike ended.

All three fall

Check shared dependencies first:

  • Page indexing and canonical selection.
  • Site availability and rendering.
  • noindex, robots, or redirect changes.
  • Large template or migration releases.
  • Manual actions and security issues.
  • Publishing volume and major demand changes.
  • Search Console data anomalies.

Then segment the loss. A simultaneous decline can still have different causes on each surface.

Common mistakes

Calling every news result “Google News”

The source labels are not interchangeable. The News tab is news; apps and news.google.com are googleNews; the default All tab is web.

Looking for News-tab traffic in the Google News report

The separate report explicitly excludes the Search News tab.

Comparing CTR without counting rules

News-tab results on the current page can receive impressions without being scrolled into view. Google News items must be scrolled into view. The denominators differ.

Expecting queries or position from Google News

Those metrics belong to Search results. Use page, country, device, and date for Google News analysis.

Treating Publisher Center as an approval workflow

Inclusion is automatic and algorithmic. Publisher Center no longer supplies manually customized Google News publication pages or submitted RSS/web locations for that purpose.

Summing the first 1,000 page rows

The UI table is truncated. The chart total can be more complete.

Attributing data to the clicked duplicate

Search Console normally credits the Google-selected canonical and the property containing it.

Counting notifications as Search Console clicks

Google documents notifications and in-app article swipes as excluded from Google News Performance clicks and impressions.

What Search Console can and cannot conclude

It can show:

  • Web, News-tab, and Google News traffic as separate sources.
  • Clicks, impressions, CTR, queries, and position for the Search News tab.
  • Clicks, impressions, CTR, pages, countries, devices, and dates for Google News.
  • Canonical-page attribution.
  • News Showcase performance where supported.
  • API and bulk-export data for automation.

It cannot show:

  • One native total called “all news traffic.”
  • Queries or ranking position inside Google News apps/site.
  • Whether a Google News view came from the app or news.google.com.
  • Notification or in-app swipe traffic in the Google News metrics.
  • Every page in the 1,000-row interface table.
  • A numeric report-visibility threshold.
  • A causal explanation for a traffic change without further evidence.
  • Approval status created by Publisher Center.

Review checklist

  • Web, News tab, and Google News are labeled separately.
  • Top Stories in the All tab is not automatically classified as News-tab traffic.
  • The Google News report is understood to exclude the News tab.
  • News-tab queries and position are not transferred to Google News analysis.
  • Impression-counting differences are documented before comparing CTR.
  • Notification and in-app swipe exclusions are accounted for.
  • Canonical URLs and property scope are reconciled.
  • Pacific Time, local hourly time, and preliminary data are normalized.
  • The 1,000-row interface limit is not treated as a complete inventory.
  • API requests use news and googleNews correctly.
  • BigQuery queries keep search_type in their grouping.
  • Exported rows are aggregated before reporting.
  • Publisher Center is not treated as an inclusion gate.
  • News policies, manual actions, indexing, and demand are checked separately.

Official sources