vodafone.es

JSON-LD validates against the declared schema.org type.

{
  "warns": 4,
  "errors": 1,
  "firstError": {
    "path": "$.name",
    "message": "WebSite requires \"name\".",
    "severity": "error"
  }
}

Declared JSON-LD types cover the apparent page purpose (e.g. a product page has Product, a blog post has Article).

{
  "missing": [
    "Article|BlogPosting|NewsArticle"
  ],
  "declared": [
    "WebSite",
    "SearchAction",
    "BreadcrumbList",
    "ListItem",
    "Organization",
    "PostalAddress",
    "ContactPoint",
    "Product",
    "Brand",
    "ImageObject",
    "AggregateOffer",
    "ItemList"
  ],
  "expected": [
    "Article|BlogPosting|NewsArticle"
  ]
}

A price declared in JSON-LD appears among the prices visible on the served page, compared by numeric value ("79.00" matches "$79"). Fails only when NO declared price is visible - a page whose machine channel and human channel disagree makes agents quote a number customers never see. Both price lists are recorded as evidence.

{
  "jsonLdPrices": [
    "20.00",
    "59.99",
    "11.00",
    "45.00",
    "0.00"
  ],
  "visiblePrices": []
}

robots.txt advertises Content-Signal directives (e.g. `Content-Signal: ai-train=no, ai-summarize=yes`) that let agents respect granular usage preferences.

{}

HTTP `Link:` response headers carry useful relations (canonical, alternate, describedby) that agents consume without parsing HTML.

{}

An MCP Server Card is reachable at `/.well-known/mcp/server-card.json` (or referenced from a Link header) and validates against the Model Context Protocol spec.

{
  "status": 404
}

`/.well-known/oauth-authorization-server` is reachable and conforms to RFC 8414, letting agents discover authorization endpoints without out-of-band setup.

{
  "status": 404
}

`/.well-known/oauth-protected-resource` is published per RFC 9728 so agents can discover required scopes and authorization servers programmatically.

{
  "status": 404
}