News publishers should treat Google Search, the News tab, Google News, and Discover as separate distribution systems with separate reporting. Combining them into one traffic line hides whether a change came from query-led Search, the Google News app, or an interest-driven Discover feed.
Search Console provides Google exposure and clicks, not subscriber value, article completion, app usage, or all referral traffic. Join it to newsroom analytics and publishing metadata.
Know which report measures what
| Surface | Search Console source | Important distinction |
|---|---|---|
| Web Search “All” results | Search results Performance, type web |
Includes ordinary results and supported features |
| News tab in Google Search | Search results Performance, type news |
Query-led tab inside Google Search |
Google News app and news.google.com |
Google News Performance / API type googleNews |
Does not include the Search News tab |
| Discover | Discover Performance / API type discover |
Interest-led, no query dimension, thresholded and volatile |
| Image or Video Search | Search results Performance types image and video |
Separate from embedded media in Web results |
The Google News and Discover reports appear only when the property reaches sufficient impressions. Their absence does not prove that the site is ineligible or never appeared.
Set up newsroom-ready segmentation
Join canonical page URLs to first-party fields such as publication time, update time, desk, topic, author, format, paywall state, and evergreen/breaking classification. Search Console does not contain these fields.
Use a complete Domain property for governance and URL-prefix properties only for stable newsroom scopes that genuinely need separate access. Remember that Performance credit normally follows Google's canonical, including across syndication or duplicate variants.
Maintain segments for:
- breaking and live coverage;
- analysis and evergreen explainers;
- video, galleries, and Web Stories;
- desks, regions, or editions;
- free, metered, and subscriber content;
- newly published and materially updated stories.
Monitor at three speeds
First hours
Use the 24-hour Performance view for preliminary hourly direction, and inspect a small set of critical URLs for crawlability, indexed evidence, canonical choice, and detected structured data. Preliminary data can change. Do not use hourly movement as a final edition score.
First days
Compare relevant Search, News, Google News, and Discover surfaces independently. Check whether an apparent failure is isolated to a desk, template, device, country, or search type. Review server logs and publishing systems when freshness or crawling is critical.
Long-term
Compare equivalent weekdays and seasonal/event periods, not only the preceding seven days. Separate evergreen search value from spike-driven distribution. Store exports beyond the rolling Search Console history if multi-year event comparisons matter.
News sitemap rules
A separate news sitemap can help Google track recently published news articles; it does not improve ranking by itself. Google's documented rules include:
- include only articles published in the last two days;
- remove the News-specific metadata or URL from the news sitemap after two days, while the article can remain in a normal web sitemap;
- include no more than 1,000 News URLs in one sitemap, splitting larger output with a sitemap index;
- keep publication names and dates accurate and update the sitemap as new articles publish.
Submit and monitor the sitemap in Search Console, but do not interpret a successful fetch as proof that every story was crawled, indexed, or shown in Google News.
Article data, dates, and canonicals
Article, NewsArticle, or BlogPosting structured data can help Google understand headline, images, dates, and authors. It is not required for Google News and does not guarantee a rich result or distribution.
Keep visible and structured datePublished and dateModified values consistent. Change the modification date only for a meaningful update, not to simulate freshness. Provide clear bylines and author information, accurate high-resolution images, and one stable canonical per story.
For syndicated or edition variants, decide which version should accumulate signals and monitor Google's selected canonical. Search Console may credit the canonical property rather than the URL readers actually opened.
Discover strategy without false certainty
Discover eligibility is automatic for indexed content that follows policy; no special tag is required. Google recommends representative images at least 1,200 pixels wide, more than 300,000 total pixels, suitable for a 16:9 crop, and enabled with max-image-preview:large or AMP.
Avoid clickbait, sensationalism, missing context, generic logos, and text-heavy preview images. Discover traffic can change because interests, content mix, and Google systems change, even when publishing quality or frequency does not. Treat it as supplemental to query-led Search.
Diagnose a newsroom traffic change
- Check Search Console data anomalies and Google Search status.
- Separate Web, News tab, Google News, and Discover.
- Compare clicks and impressions; position exists only where the report supports it.
- Group by desk, format, template, and publication cohort outside GSC.
- Check demand with Google Trends and the real-world news cycle.
- Inspect representative affected and unaffected URLs.
- Review releases involving rendering, canonical tags, paywalls, dates, images, or sitemaps.
- Avoid claiming a Google update caused the change solely because dates overlap.
Discover is especially volatile, and row thresholds can hide low-volume pages even while their metrics contribute to totals.
Paywalls and subscriptions
Paywalled content can appear in Search when Google can access and understand it and the site follows applicable policies. Mark paywalled sections so Google can distinguish them from cloaking. Test what Googlebot can render, and join Search Console landing pages to registration and subscription outcomes in first-party systems.
Search Console cannot report whether the click hit a paywall, converted, or retained.
A defensible newsroom dashboard
Show each surface separately with:
- clicks and impressions;
- CTR where meaningful;
- absolute and percentage change;
- top gaining and losing canonical stories;
- desk and format rollups from publishing metadata;
- publication cohorts and update events;
- confirmed anomalies or technical incidents;
- subscription and engagement metrics clearly labeled as non-GSC data.
Avoid summing overlapping products into a single “Google visibility” number without documenting scope and counting differences.
Related content
- News tab vs Google News reporting
- Discover Performance: complete guide
- XML sitemaps: complete guide
- Reporting anomalies & known issues