← Back to assessments

SI008 – SPA Route Integrity

Overview

Assessment for SPA route integrity. Looks for History API usage, route definitions, navigation components, and route guards in page (script/content patterns).

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

  • **_extract_spa_routing_information:** history_api, route_definitions, navigation_components, route_guards (regex/class/data-attr based).
  • **Scoring:** history_api +30, route_definitions +25, navigation_components +25, route_guards +20. **PASSED** if >= 60.

Pass / Fail and Score

  • **PASSED** if score >= 60. Score: history_api +30, route_definitions +25, navigation_components +25, route_guards +20. Max 100.

How to Fix When It Fails

  • Implement History API for SPA routing; define route structures; add navigation components; implement route guards where appropriate.

Common Issues

  • SPA without clear route indicators or History API; missing navigation or guards.

Dependencies

None.

How to Verify

  • Inspect page script/content for History API usage, route definitions, navigation components, and route guards.

Additional Resources

  • MDN: History API — pushState/replaceState and session history; SPAs use it for client-side routing. Assessment looks for History API usage, route definitions, navigation components, and route guards in script/DOM.
  • SPA SEO: ensure crawlable content (prerender, SSR, or hybrid) and canonical/URL consistency; see SD004 (canonical) and SI007 (SSR/schema timing).