en
/login
Koval SEO

Product priceCurrency is not an ISO 4217 code

In the reportProduct priceCurrency does not meet Google's ISO 4217 requirement

structured_data_invalid_currency_code · Issue

Short answer

Inspect the original priceCurrency and price carrier shown in the finding. Use the appropriate three-letter ISO 4217 code for the Product price.

Severity: Medium. The declared Product price currency does not meet the reviewed Google requirement. The finding does not promise that correcting one field makes the product eligible for rich results.

Why it matters

Google Product price markup uses three-letter ISO 4217 codes. A currency symbol, country code or unassigned token does not supply that code. General Schema.org prices can use crypto or local currencies outside this Product check.

What to do

  1. Review the raw value, literal kind, effective price carrier and captured Product/Offer declarations.
  2. Correct the data writer using the appropriate currency for the price; do not guess a currency from spelling or convert the amount automatically.
  3. Run a subsequent full audit of the same site. Complete coverage of the selected currency group is required before disappearance counts as a correction.

When to leave it as it is: Keep valid ISO funds, metal and special codes when they describe the intended price; this check does not establish their commercial suitability. Keep legitimate crypto or local currencies on proven non-Product Schema.org subjects.

What we read

The original typed JSON-LD, Microdata or RDFa graph from a complete current HTML 200 capture, including the selected JSON-LD root inventory and optional same-tree raw currency-attribute coverage.

Unambiguous Product and subtype offer relationships, including Offer and AggregateOffer. Offer.price has priority over alternative priceSpecification; when it is absent, an active UnitPriceSpecification can carry the price.

A sealed code/status reference with 178 current and 129 historical-only codes, snapshot 4 October 2026. Only these minimal facts are bundled; publisher XML is not distributed.

Example & evidence

Illustrative same-product currency correction; no live audit result.

{"@context":"https://schema.org","@type":"Product","name":"Lamp","offers":{"@type":"Offer","price":"19.00","priceCurrency":"EURO"}}
{"@context":"https://schema.org","@type":"Product","name":"Lamp","offers":{"@type":"Offer","price":"19.00","priceCurrency":"EUR"}}

Confirm & check again

Check for yourself: Inspect the served markup and the price currency in the source system. Check Product eligibility separately with Google’s Rich Results Test.

Check again: Full audit — A subsequent full audit uses the shared evaluator and lifecycle. The exact raw currency and literal kind define the group identity; changing its URL membership does not create a different finding.

Limits & sources

Historical codes, lowercase or whitespace variants, ambiguous literals, missing effective price/currency, untyped nodes and lost Product links remain unverified.

Partial captures, missing selected URLs, incomplete root or raw-attribute coverage, ambiguous rendering or unavailable/stale reference data cannot prove a correction; independently proven invalid values remain reported. Raw Microdata/RDFa currency attributes left after type, scope or vocabulary loss remain unverified.

Absence is measured against the reviewed current and historical lists at the stated snapshot date, not a claim that a code can never be assigned. No later announcements were part of that frozen source review.

Stored proof retains up to 25 declarations, displays 10 and preserves the total and affected URL count. Declaration excerpts show up to 1024 characters with original character counts, explicit truncation and original byte spans. ISO membership does not guarantee Google eligibility, availability or a valid amount.

Confidence: High High for definite original-value and fresh admitted reference evidence. Unknown declarations are coverage limitations, never findings or implicit passes.

Sources

  • Google, Merchant listing structured data — Three-letter ISO price currencies and Offer.price precedence over alternative price specifications. Checked 4 October 2026.
  • Google, Product snippet structured data — Product Offer and AggregateOffer price currency requirements; membership alone is not eligibility. Checked 4 October 2026.
  • Schema.org, priceCurrency — General Schema.org currency values can include crypto or local currencies; the Google Product requirement is narrower. Checked 4 October 2026.

Editorial review: 2 November 2026