{
    "id": 1081600,
    "title": "Structured data: facts with labels that software can read",
    "slug": "structured-data",
    "type": "page",
    "url": "https://teas.co.uk/wiki/structured-data/",
    "modified": "2026-11-15T08:57:36+00:00",
    "excerpt": "Structured data is information arranged in named fields. A person can understand \u201ca box of 50 decaf green tea bags\u201d. Software benefits from separate\u2026",
    "content_text": "Structured data is information arranged in named fields. A person can understand \u201ca box of 50 decaf green tea bags\u201d. Software benefits from separate labels for the product name, quantity, tea type and caffeine status.\nWhy a tea shop cares: labels are how software knows that \"50\" is the number of tea bags and not the price.\nThe labels make the information easier to compare. They do not make it true by themselves.\nA tea example\nFor a product, the shop can record its name, identifier, pack size, price, currency and availability. A customer reads those facts on a page. Another system can receive values with explicit labels rather than guessing which number in a paragraph is the price.\nThe distinction matters for caffeine. \u201cGreen tea\u201d describes a type of tea. \u201cDecaffeinated\u201d describes its caffeine status. A record needs both if it is to answer a request for decaf green tea accurately.\nWhat are schema.org and JSON-LD?\nSchema.org supplies a shared vocabulary, including a type called Product. Using familiar names for facts helps different systems interpret them. A shop can also maintain additional fields needed for its own search and recommendations; those are not automatically standard schema.org properties.\nJSON is a text format that groups named values and lists. JSON-LD is a way to express linked data using JSON. It is one format used to put structured information into web pages. Markup means the extra instructions or labels included with content.\nGoogle's introduction to structured data explains how it helps describe page content. The facts in a page's markup should match what the page tells its readers.\nIs it different from an API?\nYes. Structured data describes how information is organised. An API describes how software can request information or use a service. An API response can contain structured data, and a normal web page can contain it too.\nWhat should a shopper expect?\nClearer comparisons, the right pack attached to the right price, and an explicit answer when an attribute is unknown. A blank ingredient or allergy field should never become a confident \u201cfree from\u201d claim.\nStructured data does not guarantee a search appearance or an assistant recommendation. At teas.co.uk it supports a more basic aim: one authoritative source for the facts a person and a machine share. The complete payload describes how those facts can be returned together.",
    "contentSignals": "ai-train=yes, search=yes, ai-input=yes",
    "links": {
        "apiCatalog": "https://teas.co.uk/.well-known/api-catalog",
        "llmsTxt": "https://teas.co.uk/llms.txt",
        "mcp": "https://teas.co.uk/mcp",
        "mcpSetupGuides": "https://teas.co.uk/ai/",
        "mcpCard": "https://teas.co.uk/.well-known/mcp/server-card.json",
        "primaryAgenticRouteAuthority": "https://teas.co.uk/.well-known/teas-primary-agentic-route-authority.json"
    }
}