Go HTTP client
The default UA of Go's standard library HTTP client, common in cloud infrastructure and bots alike.
Go-http-client/2.0Official documentation: pkg.go.dev
See what Go HTTP client sees on your site → try Peekabot, free
What Go HTTP client does
This is Go's built-in net/http client announcing itself, with the version number reflecting the HTTP protocol used rather than the program. Go is the language of cloud infrastructure, so this UA covers everything from Kubernetes health checks and link-preview fetchers to custom crawlers and mass scanners. No robots.txt handling, no JavaScript.
Why it visits your site
A program written in Go made a request without setting a custom UA. That's a tool identifier, not an identity - the operator could be anyone.
The bigger picture: utility & developer tools
This category is the honest miscellany of a server log: monitoring services, platform callbacks, and the default user agents of HTTP libraries. The unifying rule is that the string identifies software, not intent. A curl request might be your host's health check or a vulnerability probe; a python-requests hit might be a researcher or a scraper; a WordPress UA is one site talking to another. Reading these names as a threat list misses what they actually are - a census of the scripted web touching your site, most of it mundane, some of it yours.
robots.txt barely applies here, and not out of rudeness: monitors fetch the exact URL a customer configured, feed fetchers act on a user's subscription, and bare libraries simply ship with no robots logic at all. Blocking a default library UA filters the honest and the lazy while the malicious change one line and continue, so the effective levers are different - rate limiting by IP, watching which paths get requested, and reserving blocks for named services you can verify and have decided you don't want.
Should you block it?
A blanket block catches a lot of legitimate infrastructure - webhook deliveries, uptime checks, integrations you may not realize you depend on - while serious scrapers just change the string. Better to watch what these requests target and rate limit or block by IP when one misbehaves.
Block via robots.txt
Add these lines to the robots.txt at your site root to ask Go HTTP client to stay away:
User-agent: Go-http-client Disallow: /
Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.
How to see Go HTTP client traffic on your site
You have three windows onto it, each with a catch. Raw hosting access logs contain every Go HTTP client request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because Go HTTP client doesn't run scripts.
Viz's answer is the request log: filter to Go HTTP client and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.