Product page checker
Can Google read your product's price and currency from your page's data?
- Checks your page
- Reads:HTML
- 2 rules
- Last updated
What we keep
The result appears here
Enter your page’s address and press “Check the page”. This is what the tool runs on it:
- Product offer without a valid price or currency (JSON-LD)not started
- Prices in Omani rials or Kuwaiti or Bahraini dinars without three decimalsnot started
What it checks
- Each product
Offerin JSON-LD has a price:priceorpriceSpecification.price, orlowPricefor anAggregateOffer. - The price in the data is in the digits 0–9, with a full stop for the decimal point: not in Eastern Arabic digits, and without a currency symbol.
- Each offer has a currency in
priceCurrency, as its three-letter ISO 4217 code, such asOMRorSAR, not «ر.ع.». - Prices in Omani rials, Kuwaiti dinars and Bahraini dinars in the page's text are written with three decimals, such as «12.500 ر.ع.».
Example
<!doctype html> <html lang="ar" dir="rtl"> <head> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "عطر العود الملكي", "offers": { "@type": "Offer", "price": "١٢٫٥٠٠", "priceCurrency": "ر.ع." } } </script> </head> <body> <h1>عطر العود الملكي</h1> <p>السعر: 12.50 ر.ع.</p> </body> </html>
<!doctype html> <html lang="ar" dir="rtl"> <head> <script type="application/ld+json"> { "@context": "https://schema.org", "@type": "Product", "name": "عطر العود الملكي", "offers": { "@type": "Offer", "price": "12.500", "priceCurrency": "OMR" } } </script> </head> <body> <h1>عطر العود الملكي</h1> <p>السعر: 12.500 ر.ع.</p> </body> </html>
How to fix
Generate the JSON-LD block from the price stored in your database, not from the text formatted for the page, and write the price on the page with its currency's decimals:
- Write the price in the data with the digits 0–9 and a full stop, without thousands separators or a currency symbol:
"price": "12.500"or"price": 12.5. - Put the currency in
priceCurrencyas its code:OMRfor the Omani rial,SARfor the Saudi riyal,AEDfor the UAE dirham,KWDfor the Kuwaiti dinar,BHDfor the Bahraini dinar,QARfor the Qatari riyal. - For a product with several prices (
AggregateOffer), givelowPrice,highPriceif you like, andpriceCurrency. - In your shop platform's currency settings, set three decimals for the Omani rial and the Kuwaiti and Bahraini dinars.
- After the fix, test the page with Google's Rich Results Test.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "عطر العود الملكي",
"offers": {
"@type": "Offer",
"price": "12.500",
"priceCurrency": "OMR",
"availability": "https://schema.org/InStock"
}
}
</script>
<p>السعر: 12.500 ر.ع.</p>FAQ
Because Schema.org asks for the price in the digits 0–9 rather than characters that look like them, with a full stop for the decimal point, and for the currency in priceCurrency rather than in the price. A price formatted for Arabic readers, in Eastern Arabic digits with «ر.ع.», is right on the page, but in the data it does not meet what Schema.org asks.
Not necessarily. Passing means the price and currency are written as Google asks, and Google says the required properties must be there for a page to be eligible for rich results. But the tool checks the price and currency only, not the product's other properties, so test the page with Google's Rich Results Test too.
No. The tool reads JSON-LD blocks only: not data in Microdata or RDFa, nor blocks that scripts add after the page loads. It does not check products without offers either, since Google accepts reviews or a rating instead.
What this tool runs
- Product offer without a valid price or currency (JSON-LD)moderate
product-offer-invalid - Prices in Omani rials or Kuwaiti or Bahraini dinars without three decimalsminor
price-decimals
How we measure
We fetch the page as ArablyzerBot, following its redirects, and read the HTML as the server sends it, before any JavaScript runs. We read every JSON-LD block in it that parses, @graph included, and find products by type: Product and its more specific types in Schema.org. For each offer we look for the price in price, priceSpecification.price or lowPrice, and for the currency in priceCurrency; a price passes as a number, or as text of the digits 0–9 with at most one full stop, and a currency as a code in the ISO 4217 list its maintenance agency publishes. Then we read the visible text for prices in Omani rials and Kuwaiti and Bahraini dinars, numbers with the currency's marker before or after them, and report the first price in each currency with one or two digits after its decimal mark. The same page gives the same result on every check.