Example: Price and availability contradict each other between page and markup
In the visible shop, a product is available, while structured data contains an old price or “not available”. The cause may lie in the time-delayed import, another variant source or in the cache. Such contradictions cannot be solved by additional keywords in the product text.
Finding the triggering point
Choose a specific product with a variant and record the visible price, currency, availability and the associated markup output. Check if the data is for the same variant. Then compare the time of merchandise management with the update of HTML and search engine markup.
Checking a limited fix
Allow visible information and structured data to emerge from the same reliable product information. Clarify how to deal with price ranges, sold-out variants, and temporarily unavailable items. A product family may not inadvertently assume the availability of any single variant.
Test a change in inventory or price until the public issue. Then check a second product with a different variant structure. The correction is only robust if a future import no longer generates contradictory data.
Symptoms in the audit
- Error focuses on products or categories
- Variants and filters create duplicates
- Structured data missing for certain product types
Then they test the cause.
- 1. Products, variants and categories crawl separately
- 2. Check data fields in the PIM or shop backend
- 3. Compare Sitemap against Product Status
Fixed route
- Define mandatory fields for SEO data
- Consolidating variant logic
- Correct product scheme and canonicals template-wide