Axios

What Axios does

Axios is the go-to HTTP client for JavaScript applications, and when running server-side in Node.js it identifies as axios plus its version. The UA names the library, not the operator - the same string covers a SaaS integration calling your REST API, a webhook consumer, and a scraper someone wrote in an afternoon. It has no robots.txt logic and does not render pages.

Why it visits your site

A Node.js application made a request with the library defaults. Given how common Axios is in web apps and integrations, much of this traffic is machinery talking to machinery - APIs, webhooks, feeds.

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 is more likely to break a legitimate integration than to stop a scraper, who will change the string the moment a request fails. Treat it as a tally of how much scripted JavaScript traffic you get, and act on specific IPs when one gets greedy.

Block via robots.txt

Add these lines to the robots.txt at your site root to ask Axios to stay away:

User-agent: axios
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 Axios traffic on your site

You have three windows onto it, each with a catch. Raw hosting access logs contain every Axios 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 Axios doesn't run scripts.

Viz's answer is the request log: filter to Axios 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.