Playbook: verify rendered-vs-raw content parity

Playbook: verify rendered-vs-raw content parity
Median JS site: 14.2% of primary content (title, H1, body) differs between raw and rendered HTML (sample: 84 sites). Parity gaps = indexing risk.

Check order:
— Step 1: capture raw HTML and rendered DOM for 50 sampled URLs across templates
— Step 2: diff key elements: title, meta description, H1, canonical, first 500 words
— Step 3: score parity per element. Title/canonical should be ▓▓▓▓▓▓▓▓▓▓ 100% in raw HTML
— Step 4: any SEO-critical element that's render-only → move it server-side (SSR/prerender)
— Step 5: confirm Googlebot's rendered version via 'Inspect URL > View tested page' on 10 URLs

So what: titles and canonicals injected by JS are the highest-risk gap — they fail silently. Demand 100% raw-HTML parity on those two before worrying about body content.