# Where a textile certification can actually live in machine-readable form

Source: https://activatedigital.ai/knowledge/evidence/where-a-textile-certification-can-live
Last verified: 30 August 2026
Summary: You hold a certificate. You want a system to be able to find it, read it and tell it apart from a logo on a product page. The commerce feed that would be the obvious home accepts exactly four certification authorities and not one of them covers textiles. There is one route that does fit, it has been available since March 2026, and we found nobody using it.

## In 60 seconds

Two places will accept a structured certification today, and they are not equivalent.

- Google Merchant Center's certification authority list is closed at four entries: EPREL, the French and German vehicle carbon dioxide registries and Energy Star. No textile scheme fits.
- schema.org release 30.0, **19 March 2026**, added a general credential class and worked examples for EU product passports.
- Markup does not populate a commerce feed, verify a certificate or put it in a passport.
- No primary source from any AI shopping surface states that verified or regulatory-grade attributes are consumed or preferred.
- GOTS, GRS and OEKO-TEX certify an input, a process or a facility rather than the finished article.
**Google Merchant Center carries a certification attribute** with sub-attributes for the authority, the name, the code and the value. Its authority list is closed and holds four entries: [EPREL](https://activatedigital.ai/knowledge/digital-product-passport/tyres/eprel-data-reuse), the French and German vehicle carbon dioxide registries, and Energy Star. A textile scheme cannot be expressed in it. Not because it is unsupported yet, but because the field does not accept an authority outside that list.

**schema.org carries a certification type** with properties for the certifying body, an identifier, a status, a publication date and an expiry. It also gained, in release 30.0 of March 2026, a general credential class and a set of worked examples for EU product passports aligned to international trade codes, with equivalence annotations to the main product identification vocabulary.

That second route is the only one available to a textile certificate. It costs almost nothing to use. It has no demonstrated effect on anything.

## Why the feed route is closed rather than immature

The one regulated attribute in production in a commerce feed exists because energy labelling law compelled it into the feed. A regulator required a public registry entry, the registry became the authority, and the feed added a field that points at it. The mechanism ran law first, feed second.

Nothing has compelled a textile certification into any feed, so no feed carries one. The absence is not a backlog. It is the same mechanism, not yet triggered.

Waiting for a commerce surface to ask for your certification data is waiting for something that has never happened in that order in this category. What the rails carry today, and why that is a schema fact rather than an opinion, is set out on [who decides what your product is made of when an AI answers for you](https://activatedigital.ai/knowledge/passport/who-decides-what-your-product-is-made-of). This page starts where that one stops, at the question of where a textile certificate can go instead.

## What the open vocabulary route actually gives you

Modest and specific.

You can publish, on a page you control, a structured statement that this product holds a certification, issued by a named body, carrying an identifier, with a status and dates attached. That statement is parseable by anything that reads the vocabulary, which includes search crawlers and general retrieval systems.

That gets you one thing. **A machine reading your page can tell the difference between a certification and a logo.** A logo in an image is a picture. A structured certification is an assertion with a body, a number and an expiry against it.

Four things it does not get you.

It does not get you into a commerce feed. The two are separate pipes and publishing markup does not populate a feed.

It does not verify anything. The vocabulary supplies a place to state a certification. It does not check that the certificate exists, that it covers these goods or that it is current. Which of your documents establishes something about the goods, as opposed to about a facility or an organisation, is the harder question and it sits on [certificates, declarations and test reports](https://activatedigital.ai/knowledge/evidence/documents).

It does not improve visibility to AI shopping surfaces. No primary source from any such surface states that verified or regulatory-grade attributes are consumed or preferred, and one major operator's own documentation states that no special structured data is needed to appear in its AI features. Two research programmes rejected the visibility proposition independently and a retest upheld it.

It does not put your certificate in a passport. A passport is a separate artefact with its own requirements, none of which are settled for textiles.

## The distinctions this territory keeps collapsing

| The distinction | What it is not the same as |
|---|---|
| Machine-readable | Not the same as accurate. A parseable false statement parses fine. |
| Structured | Not the same as verified. The vocabulary supplies a shape, not a check. |
| Published | Not the same as consumed. Nothing obliges any system to read it. |
| Discoverable | Not the same as selected. Availability does not cause a system to choose your value over its own inference. |
| A certification | Not the same as a claim you may make. What a certificate authorises you to say is governed elsewhere and is narrower than people expect. |

The last row is the one that costs money. A scheme certifies what it certifies and nothing adjacent to it, and the gap between holding a certificate and being permitted to say something is set out on [what a passport field can and cannot prove](https://activatedigital.ai/knowledge/evidence/claims-and-substantiation). What each document establishes, and what none of them does, is on [certificates, declarations and test reports](https://activatedigital.ai/knowledge/evidence/documents).

## Machine-checkable is a fifth distinction

Whether a certificate can be checked by a machine (OEKO-TEX label verification, GOTS's published certified suppliers and scope, the EU Ecolabel catalogue, EUDAMED certificate state, the W3C Verifiable Credentials 2.0 Recommendation with data integrity and status-list revocation) is a different question from whether it covers the product in front of you, and absence from a catalogue doesn't prove a licence doesn't exist: [what a machine has actually verified when it verifies a product certificate](https://activatedigital.ai/knowledge/evidence/verifiable-credentials).

## What to do, and how to classify it

Treat this as an experiment, not a strategy. It's cheap, current and reversible, and it has no revenue thesis attached to it. Those four properties together make it worth doing anyway.

**Publish the certification you actually hold, with its real identifier and its real expiry.** Not the scheme's logo, not a marketing sentence. If the expiry is in the past, the honest state is that it has expired.

**Publish it on the page that already exists.** If you are building a passport page or a product page, this is markup on a page you are shipping regardless. It is not a project.

**Say what the certificate covers.** Textile schemes certify different things. GOTS and GRS certify organisations in the chain, with transaction certificates for specific shipments. OEKO-TEX STANDARD 100 certifies the articles named on the certificate, which can include finished goods. A structured statement that implies more than your certificate covers is worse than a logo, because a machine will take it literally.

**Write it out in plain fields first.** Before any markup, set down the scheme, the body that issued the certificate, the holder, what it covers, its number and its dates. The holder is often a supplier or a site rather than your brand. If you can't trace a line from that holder and that scope to the product on the page, the statement isn't ready to publish in any format, structured or not.

Keep one more field apart from the rest: whether anyone has checked the status, where and on what date. A certificate you hold isn't the same as a certificate found current on the issuer's own register, and the record should say which of the two it is.

**Instrument nothing on the strength of it.** There is no measurement to make here and no target to set. Anybody offering you a citation rate or a visibility uplift for this work is selling a number nobody can produce.

**Re-check the vocabulary before relying on it.** This is a young addition to a vocabulary that releases regularly, and the passport examples in it are examples rather than a specification anybody is obliged to follow. Whether the certificate supports the claim you want to make is a separate test, on [what a passport field can and cannot prove](https://activatedigital.ai/knowledge/evidence/claims-and-substantiation).

Wherever the certificate ends up, it is worth keeping beside the product it describes rather than in a folder of its own. ActivateDigital can [hold the certificate against the textile record it belongs to](https://activatedigital.ai/textile-digital-product-passport-software).

## Three things that would move this

A textile scheme being added to the closed authority list in a commerce feed. That would move this subject from the open web route into the feed route, and it would be the first time the mechanism described above ran for a non-energy scheme.

Any AI surface or commerce operator documenting that it consumes a structured certification. That would convert this from an experiment into something with a reason attached.

A product act for textiles specifying how certification data is carried in a passport. That would replace the question rather than answer it.

## Keep exploring

The question this one usually raises next.

- [CompareEvidence & suppliersCertificates, declarations and test reports, and what each is worthWhat each document class establishes, and what makes each one stop being current.→](https://activatedigital.ai/knowledge/evidence/documents)
Also worth reading

- [CompareEvidence & suppliersWhat a passport field can and cannot proveThe distance between holding evidence and being permitted to say something.→](https://activatedigital.ai/knowledge/evidence/claims-and-substantiation)
- [Another angleImplementationWhere product data stops meaning the same thingWhy an attribute with the same name in two systems describes different objects.→](https://activatedigital.ai/knowledge/guides/what-does-not-map)

## Sources

- Google Merchant Center certification attribute, re-verified at source 28 August 2026 Specification
Cited for its sub-attributes and for the closed authority list, including the count and the categories of the four entries. Carried here as an absence claim for textiles.

- schema.org release 30.0, 19 March 2026 Specification
Cited for the certification type and its properties, for the general credential class added in that release, and for the release's addition of EU product passport examples aligned to international trade codes with equivalence annotations to the main product identification vocabulary. Read at the release notes and the type definitions. Whether anything consumes any of it is not established and is stated as such.

- A search operator's own developer documentation on AI features Vendor documentation
Cited for one proposition: that no special structured data is required to appear in its AI features.

- Cross-system attribute alignment research across seven product data systems, compiled 27 August 2026 Field research
Used for the finding that the commerce feed certification attribute and the open web certification property are both modelled around the same energy registry, that this is the tightest cross-system alignment found in that study, and that it does not reach textiles.

Sources as at 30 August 2026.