How to track visitors on Nuxt.

A Nuxt module, so it is two lines of config and nothing in your templates. Route changes are handled for you.

What you need

• A Nuxt 3 application.
• A VisitorPing site key, in the form vp_ABC23456 — the prefix vp_ and eight characters. The alphabet leaves out I, O, 0 and 1, so there is nothing to misread when copying it.

Install it

1
Add the module
Install it with the Nuxt CLI, which registers it for you.
```
npx nuxi module add @visitorping/nuxt
# or
pnpm add @visitorping/nuxt
```

Configure your site key

Add the module and your key to nuxt.config.ts.

export default defineNuxtConfig({
  modules: ["@visitorping/nuxt"],

  visitorping: {
    siteKey: "vp_ABC23456",
  },
});

3
Build and check
Deploy, then open the site in a private window and navigate between two routes. Both should appear in Live Radar.

Route changes are already handled

Nuxt navigates on the client without reloading the document, so a plain script tag would record the first page and nothing after it. The module follows navigation itself — there is nothing to wire into the router.

What you will actually see

Per visit: the city and region the network resolves to, where the visitor came from, the page they landed on, their device and browser, and whether they have been before.

You do not get a name, an email address, or an identity. Nobody can give you that from a page view, whatever the marketing says. Geolocation resolves a network rather than a doorstep, so a visitor on a VPN or a mobile network can appear in the wrong city entirely. Treat location as a hint.

You are collecting visitor data, so say so in your privacy notice and check which consent rules apply where your customers are — a question for your own legal advice, not for a setup guide.

If it is not working

The module is installed but nothing is tracked: Check the siteKey is inside the visitorping block in nuxt.config.ts rather than at the top level, and that you rebuilt after changing config.
It works in dev but not in production: Confirm the deployed build picked up the config change. Nuxt config is read at build time, not at runtime.

Find what is costing you search clicks, then watch the fix work.

VisitorPing reads your own Search Console data for the pages losing clicks, then rings your phone the moment someone lands on your website.

Start Free Trial See how it works

Install it

Add the module

Install it with the Nuxt CLI, which registers it for you.

npx nuxi module add @visitorping/nuxt
# or
pnpm add @visitorping/nuxt

Configure your site key

Add the module and your key to nuxt.config.ts.

export default defineNuxtConfig({
  modules: ["@visitorping/nuxt"],

  visitorping: {
    siteKey: "vp_ABC23456",
  },
});

Build and check

Deploy, then open the site in a private window and navigate between two routes. Both should appear in Live Radar.

What you will actually see

Per visit: the city and region the network resolves to, where the visitor came from, the page they landed on, their device and browser, and whether they have been before.

You are collecting visitor data, so say so in your privacy notice and check which consent rules apply where your customers are — a question for your own legal advice, not for a setup guide.

If it is not working

The module is installed but nothing is tracked

Check the siteKey is inside the visitorping block in nuxt.config.ts rather than at the top level, and that you rebuilt after changing config.

It works in dev but not in production

Confirm the deployed build picked up the config change. Nuxt config is read at build time, not at runtime.