Product Limitations & Disclaimers
We believe in transparency. Here is a clear, factual breakdown of what SiteScore verifies, what it cannot verify, and why our scoring is heuristic.
Important Diagnostic Notice
SiteScore is an evidence-based diagnostic assistant. It observes the page markup rendered in your browser and highlights areas where common best practices are missing. It does not replace official search engine consoles, authoritative rich results validators, or comprehensive manual audits.
No Ranking, Indexing, or Traffic Guarantees
- SiteScore does NOT guarantee search engine placement, ranking positions, or traffic increases on Google, Bing, or any other platform.
- Search engine indexing is controlled entirely by search engine crawlers and webmaster policies. SiteScore cannot verify whether a URL is indexed; use Google Search Console for authoritative index data.
- On-page SEO checks are diagnostic best practices, not direct determinants of search engine algorithms.
AEO and GEO Are Directional Heuristics
- Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) are emerging methodologies evaluated through heuristic proxies (such as concise answers, entity mentions, and question headings).
- SiteScore does NOT guarantee that any generative AI system (such as ChatGPT, Perplexity, Claude, or Google AI Overviews) will cite, quote, or display your website.
- AI search readiness is a structural evaluation, not proof of AI crawler indexing or citation frequency.
Local Performance vs. Field Core Web Vitals
- Performance checks in SiteScore (such as DOM node count, render-blocking tags, and image dimensions) are browser-level observations measured on your specific computer and network.
- These observations do NOT represent real-user field Core Web Vitals (LCP, INP, CLS) captured across millions of users in the Chrome User Experience Report (CrUX).
- For official lab benchmarks, refer to Google Lighthouse. For official real-user Core Web Vitals, consult PageSpeed Insights and Google Search Console.
Automated Accessibility vs. WCAG Conformance
- Automated accessibility audits can reliably detect only approximately 30% to 40% of potential accessibility barriers (such as missing alt attributes, missing form labels, and skipped heading levels).
- Achieving a high accessibility score in SiteScore does NOT constitute legal compliance with WCAG 2.1 / 2.2 AA or ADA requirements.
- True digital accessibility requires comprehensive manual testing, keyboard-only navigation review, and evaluation with screen readers by individuals with disabilities.
Structured Data Validation Scope
- SiteScore parses schema.org JSON-LD and microdata for syntax errors, missing common properties, and entity tree relationships.
- Detecting valid structured data does NOT guarantee that Google or other search engines will display rich snippets or rich results in search results.
- Always verify rich result eligibility using the official Google Rich Results Test.
Browser-Observable vs. Server-Side Data
SiteScore runs client-side in Google Chrome. It can inspect the rendered DOM, head metadata, inline scripts, computed layout geometry, and accessible properties. It cannot inspect private server-side configuration, unexposed HTTP response headers (e.g., origin-level CORS or custom CDN headers not exposed to extension APIs), server cache hit rates, internal server log files, or proprietary search engine databases.