电子邮件标记测试程序

时间:2014-10-31 14:23:54

标签: json email markup schema.org

Google的电子邮件标记测试程序始终失败并显示错误

" INVALID_OBJECT:orderStatus,http://schema.org/OrderStatusType"

我已尝试过此页面上的所有示例:

https://developers.google.com/gmail/markup/reference/order

我们是否认为这只是一个等待他们解决问题的问题?

示例json:

<html>
<body>
<script type="application/ld+json">
{
  "@context": "http://schema.org",
  "@type": "Order",
  "merchant": {
    "@type": "Organization",
    "name": "Amazon.com"
  },
  "orderNumber": "123-4567890-1234567",
  "priceCurrency": "USD",
  "price": "29.99",
  "acceptedOffer": {
    "@type": "Offer",
    "itemOffered": {
      "@type": "Product",
      "name": "Google Chromecast"
    },
    "price": "29.99",
    "priceCurrency": "USD",
    "eligibleQuantity": {
      "@type": "QuantitativeValue",
      "value": "1"
    }
  },
  "url": "https://www.amazon.ca/gp/css/summary/edit.html/orderID=123-4567890-1234567"
}
</script>
</body>
</html>

2 个答案:

答案 0 :(得分:1)

我遇到了同样的问题并通过添加修复验证:

"orderStatus" : "OrderDelivered",

我注意到使用以下无法正常工作(尽管Google示例in the documentation具有以下功能):

"orderStatus": "http://schema.org/OrderStatus/OrderDelivered",

答案 1 :(得分:0)

问题在于Google坚持要求您提供有效的statusOrder密钥。以下验证:

    <script type="application/ld+json">
        {
          "@context": "http://schema.org",
          "@type": "Order",
          "merchant": {
            "@type": "Organization",
            "name": "Amazon.com"
          },
          "orderNumber": "123-4567890-1234567",
          "priceCurrency": "USD",
          "price": "29.99",
          "acceptedOffer": {
            "@type": "Offer",
            "itemOffered": {
              "@type": "Product",
              "name": "Google Chromecast"
            },
            "price": "29.99",
            "priceCurrency": "USD",
            "eligibleQuantity": {
              "@type": "QuantitativeValue",
              "value": "1"
            }
        },
             "orderStatus" : "OrderDelivered",
             "url": "https://www.amazon.ca/gp/css/summary/edit.html/orderID=123-4567890-1234567"

        }
        </script>
相关问题