Separate Google News, Top Stories and Discover expectations
Publisher SEO planning should identify the surface being reviewed. The Google News website and apps, the News tab in Search and Top Stories are not a single screen or report. Discover recommends content around interests and is not limited to breaking news. Eligibility does not guarantee display. Another publisher’s large Discover share is not evidence that your publication should receive the same traffic mix.
Google’s 2025 transition notice describes automatically generated publication pages and the end of using submitted Publisher Center feeds and locations. Do not present the former News application and customised sections as current requirements. Distinguish other Publisher Center products from News approval. This guide does not rely on a verified algorithm called News 3.0 or paid expedited acceptance. Define the engagement through actual site output and publishing processes, including what is outside the review.
Make reporting, sources and correction responsibility visible
Content planning in a newsroom includes source, event timing, context and information not yet verified. Rewriting a wire report does not mean original reporting took place. Health, finance and other sensitive subjects require suitable sources and review. Never attribute an interview or expert check that did not happen. Give the editor enough context to distinguish a confirmed event from a source’s interpretation.
The Google News transparency policy highlights clear dates, bylines, author/publisher information and contact details. Explain editorial principles, correction routes and company relationships in terms readers can understand. Disclose sponsored content rather than disguise it as independent reporting. These details do not create a numerical E-E-A-T score. Use the length the topic requires instead of a universal breaking-news word target. The workflow below is illustrative, not the result of a Prix newsroom project.
Separate information
Identify the confirmed event, source statement and remaining uncertainty.
Identify responsibility
Match byline, editorial review and correction route to actual people.
Explain updates
Show meaningful changes rather than adjusting dates merely to appear fresh.
FROM READING TO A NEXT STEP
Review the SEO obstacles in your publishing workflow
Share the platform, publishing rhythm and priority issue. We can plan technical and editorial checks around representative templates.
Audit article and archive access together
Technical review should include categories, authors, tags and valuable archive material alongside new stories. Do not automatically noindex every archive. Assess its reader task and information. A listing that links to an article is not automatically a duplicate article. Canonical decisions need actual equivalents. Use real pagination URLs and accessible links rather than depend on Google’s retired rel next/prev handling.
Check source HTML, rendered content, status codes, robots and noindex on representative templates. There is no universally required date-based URL format. For an actual URL move, map a relevant redirect; do not redirect unrelated stories to the homepage. Old publication dates alone do not establish irrelevance. Test CDN, caching and server capacity around the existing application and newsroom load. Redis or Varnish is not a universal requirement. The authorised team should coordinate private areas, security and rollback, including how a publishing interruption will be handled.
Align news sitemaps, structured data and genuine dates
Publication output checks should compare visible dates and authors with machine-readable information. Suitable Article or NewsArticle data can describe the content; Google’s Article guidance explains there is no markup requirement for Top Stories eligibility. Valid markup does not guarantee a result card. Describe live coverage and video only where those formats actually exist. Modification dates should represent real changes.
The news sitemap guide covers articles created within the last two days and a maximum of one thousand news entries per file. Older addresses may remain in the regular sitemap and archive plan; removing news metadata is not deleting the story. A maintained sitemap may support discovery without a minutes-to-index commitment. Do not describe URL Inspection, RSS, WebSub or a ping service as instant Google News admission. The Google Indexing API is not a general article-submission tool.

Choose news imagery through meaning, rights and mobile experience
Visual planning should distinguish event photography, licensed stock, archive images and illustrative production. Do not present an AI image as a photograph from the scene. Alt text should describe meaning rather than list keywords. Faces, plates and sensitive information require the appropriate rights and editorial process. Ensure social previews represent the article’s scope instead of promising details absent from the story.
Google’s Discover guidance recommends relevant large images, at least 1200 pixels wide, suitable resolution and landscape framing with large-preview permission. Recommendations are not a visibility guarantee or a separate admission condition. Prefer meaningful imagery to generic logos and text-heavy covers. Do not indiscriminately lazy-load the first large visible image. Review advert slots, image dimensions, fonts and interactions on mobile. Adding a video alone does not promise ranking or reading-time improvement. A claimed editorial image should preserve its actual context and source.
Manage titles, local coverage and distribution accurately
Distribution workflows can support newsletters, social sharing and existing RSS consumers. Check current Feedly or Flipboard compatibility and terms separately; neither guarantees regular visits. A headline should explain the story without misleading omissions. Review descriptions and social cards on representative screens rather than treat one character limit as a universal display rule. Templates should support meaningful titles without forcing identical wording across channels.
In local coverage, place, event timing, institutions and verified facts belong in context. Copying district names into repeated pages is not local journalism. A Business Profile should be considered only for an actually eligible organisation location; Place or publisher markup alone does not create map visibility. For syndication, define source, rights, updates and search expectations. Do not assume a cross-domain canonical will certainly protect the original story. Disclose sponsored relationships and qualify paid links appropriately. Social sharing is not a direct numerical Google ranking score.
Read news performance in the correct report
Measurement planning should distinguish visits, reading tasks, another article and subscriptions. The Google News performance report covers news.google.com and News apps. The News tab in Search is analysed through Search performance with the News filter. Discover has a separate report. Do not combine these as one undifferentiated channel. Missing report data is not automatically proof of a technical fault.
Real-time analytics can inform editorial decisions, but provisional or incomplete data is not a final result. Interpret CTR with impressions and analytics with configured events. Reading one page and leaving is not independently evidence of a poor experience. The table below contains illustrative measures, without industry thresholds or case figures. Consider advertising revenue, subscriptions and delivery costs together. No authorised publisher dataset was supplied for this guide, so it claims no Prix traffic, Discover-share or revenue uplift. Record the period and definition behind each chart.
| Question | Evidence | Limit |
|---|---|---|
| Is the article discoverable? | Live output and relevant Search Console information | Discovery does not guarantee ranking |
| Does the reading task work? | Defined interactions and device checks | Time alone is not a quality score |
| Was subscription completed? | Authorised system acceptance | A click is not a subscription |
Plan a technical pilot, editorial checks and ongoing review
News SEO scope should follow actual issues and implementation capacity. Select article, category, author and mobile templates; inspect access, dates, sources and images. Newsroom and engineering owners should share acceptance evidence for each correction. A CMS or infrastructure move requires an agreed release plan and rollback path. Do not assume ordinary publishing permissions also authorise unrelated operational changes.
Extend the verified pilot to relevant templates. Headline and image tests must preserve source accuracy and genuine date information. A new workflow does not guarantee Google News admission, minute-by-minute crawling or traffic growth within ninety days. Maintain publication-specific reporting, ownership and review. Share the URL, publishing rhythm, priority issue and platform in the first brief. Exclude private reader records and access credentials. Implementation should support journalism rather than turn source checking into an SEO speed race. A sustainable process gives editors and developers a clear way to investigate and correct an issue without inventing outcomes.
BEFORE YOU DECIDE
Frequently asked questions
Must we apply through Publisher Center?
Do not treat the former manual publication-page and RSS setup as a current requirement. Eligible content is considered automatically; appearance is not guaranteed.
Are AMP and NewsArticle mandatory?
Do not present them as required for Top Stories. Suitable markup can describe content; actual access and accurate publishing information still need review.
Should the news sitemap contain the whole archive?
News entries cover articles created in the last two days. Valuable older stories can be addressed through the regular sitemap and archive access.
Should we change dates every day?
Do not refresh dates without genuine changes. Explain original publication and meaningful updates accurately; freshness does not guarantee results.
Is there a guaranteed Discover traffic method?
No. Apply suitable content, imagery and experience guidance, while recognising volatility and different traffic mixes across publishers.
What belongs in the first technical brief?
Share the website, CMS, publishing rhythm, affected examples and recent changes. Do not send private reader data or passwords.
LET’S DEFINE THE SCOPE
Review the SEO obstacles in your publishing workflow
Share the platform, publishing rhythm and priority issue. We can plan technical and editorial checks around representative templates.
Discuss my news SEO scope