Structured data
Structured data is machine-readable markup — Schema.org vocabulary in JSON-LD — that states explicitly what a page is about, who published it, and how its entities relate. It helps systems resolve facts they would otherwise have to infer from prose.
Structured data does not make a model cite you. It removes reasons not to.
Product, in JSON-LDschema.org
"@type": "Product",
"name": "Seolwha Daily Sun Fluid SPF50+",
"brand": { "@type": "Brand", "name": "Seolwha" },
"additionalProperty": [
{ "name": "SPF", "value": "50+" },
{ "name": "PA rating", "value": "PA++++" }
]The useful types for a consumer brand are narrow:
| Type | What it establishes | When to use it |
|---|---|---|
Organization |
Who you are, through sameAs links |
Once, for the brand |
Product |
Real specification values | On a product page that states them |
Article |
A named author |
On editorial content |
FAQPage |
Questions and answers | Only where genuine ones appear on the page |
BreadcrumbList |
Context | Where the page sits in the site |
Two rules matter more than coverage. First, never mark up content that is not visibly on the page — it violates the search engines’ own structured-data policies, whatever a syntax validator says. Second, use stable @id values so the same entity referenced from different pages resolves to one node rather than several near-duplicates.
The controlled study behind that, and where structured data ranks against the things that do move a citation, is in what ChatGPT searches before it names a brand.
Related: entity resolution.