Google Search Console for Google News — Publisher Requirements and Verification for News Indexing

If you run a news site, a periodical blog, or an online magazine, you already know that traffic from Google News can make the difference between a struggling project and a thriving one. But here’s the catch: great content alone won’t cut it. Google News enforces strict technical and editorial requirements, and publisher verification through Google Search Console (GSC) is the first hurdle many get wrong. At Meteora Web, we see it often: sites excluded for unclear reasons, publishers losing weeks between appeals and re-reviews. In this hands-on guide, we’ll walk you through exactly what it takes to get accepted, how to configure GSC for the News section, and how to avoid the most common rejection causes.

What are the minimum requirements for a Google News publisher?

Let’s start with the basics: Google News is not a generic search engine. It wants authoritative, up-to-date sources with a clear structure. The first requirement is that your site has at least one article published in the last 30 days. Sounds obvious, but many sites get rejected because they lack regular updates. At Meteora Web, we recommend having an editorial calendar with at least 2–3 articles per week before applying.

Other technical requirements: unique URLs for each article (no session parameters), publication date visible on the page (in clear text, not just in the code), and identified author (name and/or byline). Google wants to know who wrote it. Also, the site must be fully accessible to Googlebot: no paywall blocking the crawler, no mandatory login to read the full text.

Finally, a often overlooked requirement: no duplicate content. If you publish the same article on multiple domains (or on subdomains with mirrored content), you risk exclusion. We recommend using the <link rel="canonical"> tag on every article, always pointing to the original URL.

How do you verify a publisher for Google News via GSC?

Publisher verification is not automatic: you must prove that you control the site. The most common method is verification through GSC. At Meteora Web, we recommend it because it’s simple and doesn’t require adding code to the site (well, unless you use the HTML tag method). Here are the steps:

1. Add your site to GSC

Go to Google Search Console, click “Add property”, and enter your site’s URL (e.g., https://www.yoursite.com). Choose verification via HTML file or DNS tag: at Meteora Web we prefer the DNS tag because it doesn’t touch the site and works even if the cache is stale.

2. Verify ownership

Follow GSC instructions. Once verified, wait a few hours, then go to “Indexing” → “Overview” to check that Googlebot is crawling correctly.

3. Apply for Google News access

This is not done from GSC: the publisher request is made through the Partner Dashboard of Google News. You’ll need to provide the URL that is already verified in GSC, a publisher description, and the legal name of the publisher. At Meteora Web, we’ve noticed that many get rejected because the description is unclear: write what you publish, the frequency, and the geographic target. Example: “Daily online newspaper covering local news in Sicily, with updates Monday through Saturday.”

4. Monitor the request status

Google takes anywhere from a few days to a month to respond. In GSC, under the “Google News” section (if visible), you can see any errors. If it doesn’t appear, don’t worry — the request is being processed.

What technical errors should you fix before applying?

We’ve seen perfectly good content sites get excluded for silly mistakes. Here are the most common, with concrete fixes:

The robots.txt file blocks Googlebot-News

Googlebot-News is a separate crawler from Googlebot. If your robots.txt blocks it, no article will be indexed for Google News. Check:

User-agent: Googlebot-News
Disallow: /private/  # OK, only internal paths
Disallow: /          # ERROR: blocks everything

We at Meteora Web always verify with the URL Inspection Tool in GSC, using the user agent “Googlebot-News”.

Missing or hidden publication date

Google News requires the date to be visible on the page (not just in meta tags). We use <time datetime="2026-03-15">March 15, 2026</time> with a CSS class that shows it. Also, in the schema.org NewsArticle (or Article) markup, you need datePublished and dateModified. Example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "NewsArticle",
  "headline": "Article Title",
  "datePublished": "2026-03-15T10:00:00+01:00",
  "dateModified": "2026-03-15T12:30:00+01:00",
  "author": {
    "@type": "Person",
    "name": "John Doe"
  }
}
</script>

Images too heavy or without description

Google News displays images in results. They must be at least 1200px wide, in JPEG/PNG/WebP format, and have descriptive alt attributes. At Meteora Web, we always optimize images: we had a news e-commerce client (yes, they exist) who reduced image weight by 60% and saw a 35% increase in Google News impressions.

What should you do if Google News rejects your publisher application?

Rejection is not final. Google provides a reason in the email or in the Partner Dashboard. The most frequent causes are:

• Insufficient or low-quality content: articles too short, copy-paste from other sources, missing author. Solution: add 10–15 original articles of at least 300 words each, with byline and date.
• Violation of guidelines for AI-generated content: Google has stated that automatically generated content (including AI) is acceptable only if it has added value and human review. At Meteora Web, we advise against publishing purely AI articles without editing. Every output must be verified by someone who knows, as we say in our firm positions.
• Persistent technical issues: 404 errors, slowness, expired SSL certificates. We solved a 3-month block for a client just by automating SSL renewal and optimizing the server.

After fixing, resubmit from the Partner Dashboard. No need to create a new account. At Meteora Web, we recommend waiting at least a week to let Google re-evaluate your site.

How to monitor Google News performance with GSC?

Once accepted, you can’t sit back. GSC offers a dedicated “Google News” section in the left menu (if you don’t see it, click “Overview” and look for the “Search type: News” block). There you find impressions, clicks, and CTR for each article. At Meteora Web, we check it weekly to understand which topics perform better. A key metric: a CTR below 1% indicates your headlines aren’t compelling enough. Try rephrasing more directly: “Google News Requirements and Publisher Verification” becomes “Google News rejecting you? Here’s how to pass publisher verification”.

Another useful tool is the “Index coverage” report filtered by “Google News” in the search bar: it shows excluded URLs with the reason. If you see “Excluded: Duplicate article”, you likely have a canonical issue or archive pages that Google treats as copies. At Meteora Web, we fix that by adding <meta name="robots" content="noindex,follow"> to archive pages (e.g., category, tag) and leaving only single articles indexable.

In summary

Here are the immediate actions you can take today to get compliant with Google News:

1. Verify your site on GSC using DNS or HTML file. Ensure Googlebot-News is not blocked in robots.txt.
2. Add NewsArticle markup to all articles with dates and author. Use the JSON-LD snippet above.
3. Check images: at least 1200px wide, descriptive alt, WebP format if possible.
4. Publish original, regular content: minimum 2–3 articles per week, with byline and visible date.
5. Apply to the Google News Publisher Center and monitor the response. If rejected, fix and retry after 7 days.

To dive deeper into other GSC topics, check out our pillar guide on Advanced Google Search Console. If you need hands-on support, reach out: we manage dozens of news sites for clients across Italy, from domain to revenue.