The agent on Nuxt
No server code. Nuxt runs on Nitro, which deploys to Vercel, Netlify, Cloudflare or a Node server.
How it works on Nuxt
Nuxt runs on Nitro, which deploys to Vercel, Netlify, Cloudflare or a Node server. Use that platform's guide; on a Node server the Express middleware pattern applies to the Nitro server too.
Where the agent goes
- Vercel — runs before the response
- Netlify — wraps the response
- Cloudflare Workers — wraps the response
- Node and Express — runs before the response
What this install serves
- the 23 checks run from outside on every page check
- the agent writes the exact text and snippets — title, description, opening, FAQ, Organization JSON-LD, robots lines, llms.txt — and you paste them into the builder
- the free tools read the site the way AI does
What it does not: the agent cannot install or change anything on this host, so it does not count AI visits or apply switches here — counting and the switches need a place to run: the WordPress plugin, an edge file (a Cloudflare Worker in front of the site, Vercel or Next.js middleware, Netlify, Node) or a GitHub-connected repository.
Questions people ask
Does anything change on the site when I install it?
No. Installing puts the agent in place and binds it to the site by its token; nothing is applied. Every switch is your click in the dashboard and every word it writes is shown to you first.
Can I take it out?
Remove the file and redeploy. Whatever was last switched on stops being served on the next request. Your checks and the agent's memory stay in your account.
What can this install actually do?
The 23 checks run from outside on every page check. The agent writes the exact text and snippets — title, description, opening, FAQ, Organization JSON-LD, robots lines, llms.txt — and you paste them into the builder. The free tools read the site the way AI does. The agent cannot install or change anything on this host, so it does not count AI visits or apply switches here — counting and the switches need a place to run: the WordPress plugin, an edge file (a Cloudflare Worker in front of the site, Vercel or Next.js middleware, Netlify, Node) or a GitHub-connected repository.
Is the token a secret?
Yes. It belongs to this one site and should live in an environment variable, never in a file you commit. It grants nothing beyond this site, and the domain proof refuses it from any other host.
Start with the free check. Then tell the agent what you need.
The free check runs the 23 checks on your public pages. Nothing is installed, nothing changes until you press it.
Free check from outside in minutes · the report by email · nothing installed yet