SAP Knowledge Base Article - Preview

3796278 - H1 Tags in DOM When SAP Commerce Renders Gigya Screen-Sets Causes SEO Audit Violations

Symptom

When SAP Commerce Cloud loads a Gigya (SAP Customer Data Cloud) screen-set, SEO audit tools (e.g., Screaming Frog, Lighthouse, SiteImprove) report multiple H1 violations on the page. The violations correspond to H1 tags from every screen defined within the screen-set, not just the active screen.

The H1 elements from non-active screens are present in the DOM but not visible to the end user. Despite this, SEO crawlers and accessibility audit tools parse the full DOM and flag every H1 regardless of CSS visibility or display state.


Read more...

Environment

  • Product: SAP Customer Data Cloud (Gigya) — RaaS / Screen-Sets
  • Integration: SAP Commerce Cloud (Spartacus or custom storefront) with CDC Web SDK (gigya.js)
  • Affected surfaces: Any page embedding a multi-screen screen-set (login, registration, profile update, etc.)
  • Web SDK versions: All current versions (issue is architectural, not version-specific)

Product

SAP Customer Data Cloud all versions

Keywords

screen-set H1 multiple H1 SEO SEO audit Lighthouse Screaming Frog SiteImprove accessibility WCAG aria-hidden template node DOM onAfterScreenLoad RaaS registration SAP Commerce Spartacus gigya.js Web SDK heading hierarchy data-screenset-roles CDC Console screen-set editor
 
, KBA , CEC-PRO-RAS , RaaS (Screen-Sets, Site Policies, Schema) , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.