Google News rejected three of my client’s sites last year. Same publisher, same editorial team, same content quality. Two got approved within a week. The third sat in limbo for 47 days before a rejection email that explained nothing. The difference came down to four technical signals most publishers never check — and fixing them took under an hour. Want to know how to get on Google News? Treat it as a technical compliance exercise first and an editorial pitch second.
Definition: Google News is a distribution surface that aggregates and ranks news content from publishers approved through Google Publisher Center. Inclusion isn’t automatic, and it isn’t a ranking boost in classic search. It’s a separate eligibility layer that exposes your articles to Top Stories, the News tab, and Discover feeds. Approval depends on meeting Google’s content and technical policies.
Why It Matters in 2026
News surfaces now drive a disproportionate share of discovery traffic. Top Stories blocks appear for a huge volume of queries, and Discover pushes publisher content to mobile users who never typed a search. For publishers with timely content, News eligibility can multiply visibility without a single new backlink.
The 2026 landscape punishes sloppy setups. Google tightened its transparency requirements around ownership, mastheads, and contact information. Sites built purely for aggregation get filtered fast. Meanwhile, the bar for “news” has loosened in one direction: niche trade publications, local outlets, and specialist B2B sites qualify more easily than they did five years ago, provided their technical signals are clean.
Here’s the counter-intuitive part. Getting approved matters less than staying approved. I’ve watched publishers celebrate inclusion and then lose it within months because nobody monitored policy compliance. Treat approval as a maintenance task, not a trophy.
Ranking impact works indirectly. News inclusion doesn’t lift your standard organic positions. What it does is create additional SERP real estate — a second surface where your brand can appear for breaking and trending queries. That compounding visibility is where the real value sits.
Step-by-Step
Work through these in order. Skipping steps is the fastest route to a silent rejection.
- Audit your site against the content policies. Google wants original reporting, clear authorship, dated articles, and a visible editorial team. Remove thin aggregation pages, auto-generated summaries, and any content that reads like press-release recycling. Every article needs a byline and a publish date in the visible HTML, not just structured data.
- Fix your technical foundation. Confirm your site is crawlable, fast, and mobile-friendly. Ensure your robots.txt doesn’t block Googlebot-News. Verify your XML sitemap includes a dedicated news sitemap with articles published in the last 48 hours. Check that your canonical tags resolve cleanly — conflicting canonicals are a common silent killer.
- Publish a real About, Contact, and Editorial Policy page. These aren’t decoration. Google reviewers check them for ownership transparency, physical address, and editorial standards. Include named editors, a mission statement, and a corrections policy.
- Create your publication in Google Publisher Center. Sign in with the Google account tied to your organization, add your publication, verify ownership via DNS, meta tag, or Search Console, then configure your logo, business details, and content settings.
- Submit your news sitemap inside Publisher Center. This is separate from Search Console submission. Point Publisher Center at your news sitemap URL and confirm it’s fetching without errors.
- Request a review. Publisher Center includes a review request option. Before clicking it, re-check every policy item. Reviewers assess the live site, not your intentions. One missing contact page can trigger rejection.
- Set up monitoring. Track impressions in Search Console’s News performance report, watch for policy emails, and re-audit quarterly. Approval is revocable.
Want a faster path? Spend 30 minutes reading the rejection reasons publishers post in Google’s support forums. Patterns emerge quickly, and most failures are avoidable.
3 Common Mistakes
Mistake 1: Treating Publisher Center as a one-time form. Publishers submit once, get approved, and never revisit their configuration. Then they change domains, restructure URLs, or swap CMS platforms — and their news sitemap breaks silently. Fix: Add a quarterly calendar reminder to re-verify ownership, sitemap health, and publication details. Check Search Console’s news sitemap report monthly.
Mistake 2: Publishing undated, authorless content. I’ve audited sites with hundreds of articles missing visible dates and bylines. Reviewers see this as a transparency failure. Fix: Enforce byline and date fields at the CMS template level so writers can’t skip them. Display both prominently near the headline.
Mistake 3: Confusing News eligibility with general SEO. Some publishers assume strong organic rankings guarantee News approval. They don’t. News has its own policy layer focused on originality, transparency, and topicality. Fix: Run a separate compliance audit against Google’s News content policies before requesting review. Don’t assume your SEO wins transfer.
Free Tools
You don’t need paid tooling to get this right. These free options cover the essentials:
- Google Publisher Center — the mandatory submission and configuration hub. Also surfaces policy notices and review status.
- Google Search Console — use the News performance report and sitemap diagnostics to catch crawling and indexing failures early.
- Rich Results Test — validates NewsArticle structured data, byline markup, and date fields before reviewers see them.
- Screaming Frog (free tier, 500 URLs) — audits canonicals, robots directives, and missing metadata across your news section.
- Google’s Publisher Help Center and support forums — the rejection-reason threads are the closest thing to a cheat sheet that exists.
Run all five before you request review. The combined time investment is under two hours and eliminates most rejection causes.
Advanced Tip
Most publishers stop at eligibility. The ones who win build a news sitemap strategy tuned to freshness windows. Google’s news crawlers prioritize recently published URLs, and your sitemap should reflect that with accurate publication_date and title tags for every entry.
Go one layer deeper: segment your sitemap by content type. Keep a fast-updating sitemap for breaking coverage (updated hourly) and a separate one for evergreen analysis. This gives crawlers a clean signal about what’s genuinely time-sensitive. Publishers who do this consistently report faster indexing of breaking stories — sometimes within minutes rather than hours.
Pair that with a lightweight internal freshness audit. Flag any article older than 48 hours still sitting in your news sitemap. Stale entries dilute the signal and can confuse crawlers about your publishing cadence. Automation here pays for itself.
One more test worth running: monitor which of your News-surfaced articles earn clicks versus impressions. High impressions with low CTR usually means your headlines aren’t matching News-feed intent. Adjust and re-measure. Small headline experiments compound across a publishing calendar.
Getting on Google News is a compliance problem dressed up as an editorial one. Fix the technical signals, publish transparently, and monitor continuously. The publishers who treat approval as the start of the work — not the finish line — are the ones still appearing in Top Stories two years later. Start with your sitemap and bylines this week. Everything else follows.