CMS
Rails Website Audit
Rails audit: Passenger, sessions, and a CDN in front of the app
· Configuration notes, not a newsroom.
SiteRune fingerprints Rails sessions and Passenger. Public pages should be cacheable. Headers belong in nginx or config/nginx, not a layout helper only.
RAWhat 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
Turbolinks nostalgia is not the finding
Slow TTFB on Rails is usually uncached ERB plus a session on every request. fragment caching and a CDN in front of anonymous HTML. Skip admin and account in our crawl by design.
config is the vhost
Security headers in nginx or Rack::Headers. public/llms.txt. JSON-LD in the layout. We will not emit next.config.ts because someone used Stimulus.
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.