SEODiff detects your web framework and assigns a fixed readiness score based on how AI-friendly the framework is by default. This reflects the typical rendering behaviour — not what's possible with custom configuration.
| Framework | Score | Why |
|---|---|---|
| MediaWiki | 95 | Fully static, zero JS dependency |
| Hugo, Jekyll, 11ty | 90 | Static site generators — HTML-first by design |
| WordPress, Astro | 85 | Server-rendered by default with optional JS islands |
| Shopify | 80 | Server-rendered Liquid templates with good defaults |
| Next.js | 70 | SSR-capable but often misconfigured for CSR |
| Nuxt | 70 | SSR-capable, similar to Next.js |
| Wix | 55 | SSR with significant JS overhead |
| React (CRA) | 50 | Client-side rendered by default |
| Angular | 40 | Heavy CSR, requires Angular Universal for SSR |
| Unknown | 50 | Default when framework can't be detected |
Tech Stack Score is a baseline, not a ceiling. A React SPA scores 50 by default, but with proper SSR configuration (Next.js, Remix) it can achieve the same real-world rendering quality as a static site. The score reflects what most sites on that framework actually deliver, not the framework's theoretical best.
You can't change your framework's default score, but you can compensate:
'use client' for content)The Rendering Score (which measures actual ghost ratio) will reflect these improvements regardless of the Tech Stack baseline.