Google Publisher Center Guide: What News Publishers Can Still Manage

What Does Google Publisher Center Do Now?

Google’s current Publisher Center overview focuses on Reader Revenue Manager and Google News Showcase, alongside publication administration. Publishers can maintain basic publication information, headquarters details, verified website property URLs, contact information, organisation settings, and user permissions.

Those functions should be separated from Google News inclusion. Publisher Center is not a manual approval system or a ranking control. Google states that web content is automatically considered for Google News when it meets the applicable requirements and policies.

For the wider discovery and visibility workflow, MOCOBIN’s Google News SEO guide covers crawlability, editorial transparency, technical readiness, and other site-level factors.

What You Can and Cannot Control

What Changed for Google News Publication Pages?

On April 25, 2024, Google announced that publishers could no longer set up new Google News publications in Publisher Center. A later transition update dated March 20, 2025 said Google News would move fully to automatically generated publication pages in late March 2025.

The 2025 change removed several parts of the old workflow. Google News stopped using RSS feeds and web locations submitted in Publisher Center, manually created publication pages stopped appearing to users, custom publication sections stopped appearing on ordinary Google News landing pages, and the Google News tile was removed from Publisher Center.

Branding changed as well. For ordinary Google News publication pages, Google says publisher logos now come from site favicons and publication titles from site names. Publisher Center still handles logos separately for Reader Revenue Manager and Google News Showcase.

Why Older Publisher Center Tutorials Can Mislead Teams

Instructions that tell editors to submit a publication for approval, add feed sections, arrange an ordinary Google News landing page, or optimise a Google News product tile describe a retired workflow. Keep those steps out of current internal documentation unless they relate to a still-supported product such as News Showcase or Reader Revenue Manager.

The useful question is not whether a Publisher Center profile is complete. It is whether the task you are trying to perform is still controlled inside Publisher Center at all.

How to Review Publisher Center Without Treating It as an SEO Submission Tool

Check Publication, Organisation, and Access Settings

Start with the settings Google still documents. Confirm the publication’s basic information, headquarters details, verified website property URLs, and contact information. Then review the organisation that owns the publication and remove access that is no longer needed.

Google’s user access guidance distinguishes organisation-level and publication-level roles. It states that only owners can add users and that a user needs an email address associated with a managed Google Account, such as Google Workspace or Google Cloud Identity.

These checks are most useful when ownership, staff, domains, contact details, or product use changes. A fixed review schedule adds little value if the underlying information is stable.

Separate Publisher Center Settings From Site-Controlled Signals

If the issue is the name or logo shown on an ordinary Google News publication page, review the site’s favicon and site-name signals rather than assuming a Publisher Center field will override them. Google now derives those elements from the site for ordinary publication pages.

The same separation helps when diagnosing visibility. Publisher Center can confirm administrative details and access, but Google Search Console is the better place to inspect crawling, indexing, and Google News performance when data is available.

What Actually Matters for Google News Eligibility and Visibility?

Google’s news content guidance says publishers are automatically considered for Google News and news surfaces when their content is eligible. Publisher Center does not override that automated process, and eligibility does not guarantee that content will appear or rank well.

For news publishers, site-level checks are more relevant. Google’s Google News policies call for clear dates and bylines, information about authors and the publication, information about the company or network behind the content, and contact information. Google also needs to be able to discover and process the article while it is relevant.

A Google News sitemap can help Google discover recent news articles. Google’s documentation says news-specific entries should cover articles created within the last two days. A news sitemap supports discovery, but it does not guarantee crawling, indexing, Google News inclusion, or ranking.

Article structured data can help Google understand details such as the headline, author, publication dates, and representative images. Google does not require Article structured data properties for the Article feature, and the markup should be treated as descriptive information rather than a qualification step for Google News.

A Practical Publisher Center Review Sequence

1. Define the task. If the goal is simply to apply for Google News, there is no Publisher Center application to complete.
2. Review the settings that still exist. Check publication information, headquarters details, verified website property URLs, contact information, organisation settings, and user permissions.
3. Confirm which Publisher Center products you actually use. Reader Revenue Manager and News Showcase have their own controls and should not be confused with ordinary Google News publication pages.
4. Check site-controlled identity signals. If the problem concerns the publication name or logo in Google News, inspect the site’s site-name setup and favicon.
5. Diagnose visibility outside Publisher Center. Review crawlability, indexability, policy compliance, bylines, dates, publisher transparency, Search Console data, recent-news discovery, and Article structured data where relevant.

This sequence keeps an administrative tool in its proper role and directs visibility problems to the systems that can actually explain them.