← Back to assessments

SD006 – Dynamic Data Stability

Overview

Compares Product JSON-LD between two page loads (context.page_content vs context.page_content_first). Flags changes in name, SKU, price, availability that could indicate instability or cloaking.

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

  • SD001 and SI001 must be in context and passed (status extracted from dict or AssessmentResult).
  • Current page_content parsed for JSON-LD; first Product/ProductGroup used.
  • **Extracted fields:** name, sku, price (from offers[0]), availability (from offers[0]).
  • If page_content_first present: same extraction; compare current vs previous. **Changes flagged:** name_changed, sku_changed, price_changed, availability_changed.
  • **Penalties:** name −30, SKU −40, price −20, availability −25.
  • If no previous load: passed with recommendation to monitor stability on subsequent loads.

Pass / Fail and Score

  • **PASSED** if score >= 60.
  • **Score:** 100 minus penalties for any detected changes. First run (no previous data) passes with details "First analysis run - no previous load to compare".

How to Fix When It Fails

  • Ensure product name remains consistent across loads.
  • SKU should never change for the same product.
  • Consider caching price data or implementing price change notifications.
  • Implement real-time inventory updates (for availability changes).

Common Issues

  • Product name differs between loads.
  • SKU differs (critical: same URL should not change SKU).
  • Price or availability differs (may be acceptable; assessment flags for transparency).

Dependencies

SD001 (Field Presence), SI001 (Session Consistency). Requires two loads (page_content and page_content_first) for comparison.

How to Verify

  • Run analysis twice on same URL and compare structured data; ensure name/SKU stable; document if price/availability intentionally change.

Additional Resources

  • schema.org Product, Offer availability: https://schema.org/Offer#availability