{
    "id": 1081600,
    "title": "Structured data",
    "slug": "structured-data",
    "type": "page",
    "url": "https://teas.co.uk/ai/structured-data/",
    "modified": "2026-11-20T13:08:45+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.\nLabels are how software knows that \u201c50\u201d is the number of tea bags and not the price. The labels make the information easier to compare. They do not make it true by themselves.\nLabels turn tea facts into something any system can read, through schema.org and the small records beside every picture. They make facts easier to compare. They cannot prove them.\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.\nPrice per cup is a good example of a field a tea shop needs that a general vocabulary does not hand it ready-made. It is one of the most useful labels in the shop, because it is the fairest way to compare a 40-bag box with a 240-bag box. teas.co.uk keeps it in its own records alongside the standard product facts.\nWhat are schema.org and JSON-LD?\nschema.org is a shared vocabulary for describing web content. JSON-LD is a way of writing structured data that can sit in a page. Both help software understand which value is the name, which is the price and which is the brand. They do not certify that the values are correct.\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.\nWhy a tea shop labels its facts\nPeople are starting to ask AI assistants which tea to buy instead of typing two words into a search box. An assistant sent to answer \u201ca decaf Earl Grey that is good value\u201d goes out, reads shops, guides and data, checks prices and pack sizes and whether the tea really is decaf, then reports back. That assistant cannot squint at a photograph of the back of a box to work out the caffeine. It needs the facts laid out, labelled and sourced.\nI built teas.co.uk so that an independent tea shop could be that source. An assistant that guesses will sometimes get it wrong, so given a choice between a tidy source and a messy one it will take the tidy one. Labelled facts are how a small shop becomes the tidy one.\nA paragraph of product copy is written for people. A labelled record is written for both: the shopper reads the page, and software reads the same facts with their names attached.\nFiles that sit beside every page and picture\nLabels behind product pages are only the start. The shop also publishes sidecar files next to images and discovery files that tell software where the facts live and how to ask for them.",
    "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"
    }
}