CMS
Nuxt audit: routeRules, Nitro, and headers that are not next.config
· Configuration notes, not a newsroom.
SiteRune fingerprints __NUXT__ and /_nuxt/. The playbook is nuxt.config routeRules / nitro.routeRules, not a Next.js snippet.
Different framework, same sins
Client-only heroes, missing useSeoMeta on money routes, and a document with no-store because a plugin read a cookie in the root. SiteRune does not care that it is Vue. TTFB, cache, schema, llms.txt still apply.
Where headers actually go
headerFix for Nuxt names routeRules / nitro.routeRules or the edge. We will not paste next.config.ts into a Nuxt repo. If you are on a Node host, nginx in front is fine. vercel.json only if we saw Vercel headers — Nuxt on a VPS is not Vercel.
Run it on a live URL
The brief will name your CMS and attach the files. Three guest scans, no card.