Seller identity declared

What the scanner requests

• /about
• /terms

It also reads documents it has already fetched: $home.

What is measured

Profile-scoped: reported as not scored and excluded from the denominator unless the e-commerce or marketplace profile has been positively identified, and this check never creates that identification itself. In scope, the scanner resolves the seller of every Offer in the JSON-LD it holds and requires an Organization carrying both a name and a url, then reads the homepage and the about and terms pages for a merchant-of-record statement naming the legal entity; a named seller plus a merchant of record is a pass, a named seller alone is a partial (0.7), and neither is a fail.

Reproduce it yourself

You do not have to take our word for any of this. Run the same measurement against your own domain:

              DOMAIN=shop.example.com
curl -sL "https://$DOMAIN/" | perl -0777 -ne 'while (m{<script[^>]*application/ld\+json[^>]*>(.*?)</script>}gsi) { print "$1\n" }' | jq -r '.. | objects | select((."@type"? | if type == "array" then .[] else . end) == "Offer") | [(.seller."@type" // "NO seller"), (.seller.name // "NO seller.name"), (.seller.url // "NO seller.url")] | @tsv'
            

The fix

This is the artifact to ship. It is the complete change, not a description of one.

              {
  "@context": "https://schema.org",
  "@type": "Offer",
  "url": "https://shop.example.com/products/aurora-desk-lamp",
  "price": "1299.00",
  "priceCurrency": "USD",
  "availability": "https://schema.org/InStock",
  "seller": {
    "@type": "Organization",
    "name": "Aurora Lighting ApS",
    "url": "https://shop.example.com/about",
    "legalName": "Aurora Lighting ApS",
    "vatID": "DK12345678"
  }
}
            

Standards referenced

• schema.org/Organization

Related checks