Retrieval and usability, control 16 of 18
R-16 Synchronise product and local facts across page, schema and feeds
Use one verified source for important product and local facts. Select the structured-data and feed pattern that fits the real entity and commercial model.
- Priority
- High priority.
- Hard gate
- No
- Change class
- EVIDENCE_REQUIRED: Authoritative facts must be supplied.
- Quality bucket
- Retrieval and usability
Why it matters
Shoppers who see one price on the page and another in search results or a feed lose confidence and may abandon the purchase. Search engines and AI answer engines compare these sources, so mismatched prices, stock or identifiers make the product data unreliable. Google's LocalBusiness guidance also assumes a real location, so a made-up one misrepresents the business.
Evidence to review
- Page-schema-feed comparison, catalog records and feature diagnostics.
How to implement
- Check identifiers, variants, currency, price timing, availability and delivery conditions.
- Use correct ProductGroup relationships when relevant.
- Keep merchant listings distinct from editorial product reviews and quote-only services.
- Do not invent prices or a physical location to complete a schema template.
How UltimateSEO checks this
Automated. A check in the scan sets PASS or FAIL for this control, and reports UNKNOWN or BLOCKED when its input is missing.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.