SI007 – SSR Schema Timing
Overview
Uses context.metadata to evaluate schema presence and load timing; prefers server-side rendering so schema is present in initial HTML.
Probability that AI systems use this signal: Crawlers and generative AI pipelines consume structured and visible page signals for training and inference. Assessment-specific signals (e.g. schema, canonicals, trust cues) affect how likely a page is indexed and surfaced. The probability that this assessment's signal influences AI behavior is high when the page is in a product or compliance context.
Impact on geo compliance: Passing this assessment supports geo compliance by ensuring machine-readable and visible content meet standards that reduce the risk of wrong locale, pricing, or trust in AI-generated answers. Failing can lead to non-compliant or misleading surfacing.
What We Check
- **context.metadata:** schema_load_time_ms, ssr_detected, schema_present.
- **schema_present false:** −60.
- **schema_load_time_ms > 2000:** −50; **> 1000:** −20.
- **ssr_detected false and schema_present:** −30 (client-side rendering).
- schema_load_time_ms < 500 and schema present: recommendation "Excellent schema loading performance".
Pass / Fail and Score
- **PASSED** if score >= 60.
How to Fix When It Fails
- Implement JSON-LD in initial HTML (SSR); optimize schema delivery; reduce schema load time.
Common Issues
- Schema injected client-side only; slow schema load.
Dependencies
None. Requires metadata populated by upstream (e.g. page fetcher that measures timing and SSR).
How to Verify
- Ensure schema in first HTML response; measure time to schema available.
Additional Resources
- SSR vs CSR; Core Web Vitals; JSON-LD in head