CMS
Remix Website Audit
Remix audit: headers() on the document, not a SPA costume
· Configuration notes, not a newsroom.
SiteRune fingerprints __remixContext. Remix can send headers from the document request. The brief treats it as a server.
REWhat SiteRune checks on this stack
- CMS / framework fingerprint from HTML, headers, cookies, and generator tags — fingerprint-based, not a plugin inventory
- Titles, meta descriptions, canonicals, H1, and robots on the homepage and walked interiors
- Security headers a crawler can see: HTTPS, HSTS, CSP, framing, nosniff, Referrer-Policy, Permissions-Policy
- HTML TTFB, compression, and Cache-Control on the document — not a Lighthouse filmstrip
- AI-bot robots policy, llms.txt, and Organization / FAQ / Article JSON-LD
Common problems
- Marketing homepage looks finished; interior templates ship empty titles or leftover noindex
- Hosted CMS cannot set HSTS/CSP, so the brief tells you to put a proxy in front instead of inventing an admin UI
- A security plugin's 'block AI' preset Disallows GPTBot on a site that wanted citations
- Session cookies or no-store on every anonymous GET, so the CDN never caches HTML
Loaders are the origin
Slow TTFB is often a loader that hits the CMS on every anonymous document request with no cache. Cache the document at the CDN. Do not put cookies() equivalent on the marketing layout.
headers export
Security headers belong on the Remix headers() export or the proxy. llms.txt is a resource route. We do not generate a next.config snippet for Remix. If you deployed to Vercel we will say so only when x-vercel-* is present.
FAQ
How do you know this is my stack?
Fingerprints in HTML, headers, cookies, and generator tags. Confidence is a score, not a certificate. Unknown stacks stay generic — we will not invent a CMS.
Do I need an account?
Three guest scans, no card. Create a free account when you want history and more interiors.
Run it on a live URL
Same scan engine. Guest scans stay free.