← Back to assessments

PR010 – Product Personalization Check

Overview

Assessment for product personalization features. Validates that personalization (e.g. "For you", location-based, preferences) is implemented in a way that does not break AI/SEO consistency (e.g. content still crawlable and consistent).

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

  • See implementation: personalization detection, consistency of core product data when personalized content is present.
  • Full logic: `src/domain/assessments/product_relationships/pr010_product_personalization_check.py`.

Pass / Fail and Score

  • From execute().

How to Fix When It Fails

  • Ensure personalized sections do not replace or contradict core product data; keep canonical content and schema consistent.

Common Issues

  • Personalization hiding or altering core product info; inconsistent schema vs personalized view.

Dependencies

None.

How to Verify

  • Check that personalization does not break core product data consistency; ensure canonical content and schema remain consistent.

Additional Resources

  • Personalization ("For you", location-based): keep core product data and canonical content consistent; avoid serving substantially different content to crawlers vs users (cloaking). Align with SD002 (field match visible content) and VC006 (hidden content audit).
  • Search engine guidelines: personalized content should not replace or contradict the main entity and schema visible to crawlers.