The VectraSEO monitor bot

Does VectraSEO show up in Google Analytics 4?

No. Our monitor makes plain server-side HTTP requests and never executes your page's JavaScript, so the GA4 tag (gtag.js) never fires. VectraSEO traffic produces zero hits in GA4 — there is nothing to filter there.

You'll only see us in layers that record raw requests: server access logs, CDN/WAF dashboards, and log-based analytics (e.g. Matomo log import, GoAccess, AWStats, or server-side GA4 via the Measurement Protocol). The rules below let you exclude us there with a single filter.

How to identify us

Every request from our monitor — including link-liveness and indexing pre-flight probes that present a browser-like User-Agent — carries this stable header:

X-VectraSEO-Monitor: 1.0 (+https://vectraseo.com/bot)

Filter on the header name (X-VectraSEO-Monitor) — the value is informational and may change; the name will not. This is the most reliable way to catch all of our traffic in one rule.

User-Agent strings

Our core page crawler self-identifies in its User-Agent. Two probe paths present a browser-like User-Agent so third-party WAFs don't serve them an anti-bot variant — for those, rely on the header above.

• Core crawlerVectraSEO-Monitor/1.0 (+https://vectraseo.com/bot)
• Link / indexing probes a current Chrome User-Agent string + the X-VectraSEO-Monitor header

Source IP

Requests originate from AWS (us-east-1) and use dynamic, rotating addresses — there is no fixed IP or CIDR range to allowlist or block. Use the header instead of an IP rule.

Exclusion snippets

Copy-paste rules to drop our monitor from your logs and analytics.

Cloudflare (WAF custom rule)

(http.request.headers["x-vectraseo-monitor"][0] ne "")

Action: Skip / log-only, or Block if you want to stop the crawl entirely (this will reduce your VectraSEO monitor coverage).

nginx (exclude from access log)

map $http_x_vectraseo_monitor $loggable {
    ""      1;
    default 0;
}
access_log /var/log/nginx/access.log combined if=$loggable;

Matomo (log analytics import)

./console core:import-logs access.log \
  --exclude-user-agents="VectraSEO-Monitor"

Matomo's log importer filters on User-Agent; our core crawler carries VectraSEO-Monitor in its UA.

Server-side GA4 / Measurement Protocol

If you forward server logs to GA4, drop any request where the X-VectraSEO-Monitor header is present before you build the Measurement Protocol event.