Bot intelligence record

Googlebot-News

Usually allow

Use the Googlebot-News identifier to separate Google search indexing or content discovery traffic from normal visitor requests in server logs.

Search Indexing Official Documented Confidence: High Verified: Yes robots.txt: Yes
Operator
Google
Family
Google
Type
Search
Source type
Official
Last checked
2026-05-20

User-Agent Pattern

Google
Googlebot-News
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
User-agent: Googlebot-News Disallow: /

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Search indexing, content discovery, rendering, or search-result freshness checks.

Record Details

Structured data
Operator
Google
Family
Google
Type
Search
Purpose
Indexing
Identity type
Official Documented
Confidence
High
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Official
Verification
Treat this as a Google-specific robots token and verify underlying traffic as Googlebot traffic.
Spoofing risk
User-agent strings for Googlebot-News can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.

Notes

Googlebot-News is listed in the Botcrawl directory as a search crawler from Google. The primary identifier for log review is Googlebot-News.

Identification

  • User-agent pattern: Googlebot-News
  • Family: Google
  • Type: Search
  • Kind: Crawler

Common use

Search indexing, content discovery, rendering, or search-result freshness checks.

Verification and handling

Treat this as a Google-specific robots token and verify underlying traffic as Googlebot traffic.

Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: Yes.

Evidence and Source

  • Treat this as a Google-specific robots token and verify underlying traffic as Googlebot traffic.
  • Match `Googlebot-News` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Use bot_http_agent for full user-agent examples when the client sends a longer browser-like string. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Search indexing, content discovery, rendering, or search-result freshness checks.
  • User-agent strings for Googlebot-News can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.