72 of 120 API-returned 1688 English title fields repeated one token at least three times

Repeated tokens appeared across the returned title fields

The API returned both subject and subjectTrans on all 120 sampled rows. Under the published tokenisation rule, 72 subjectTrans values repeated one token at least three times and 31 repeated one at least four times. The maximum observed repeat count was 6.

The median subjectTrans length was 124 characters, while the median subject length was 31. Character counts across writing systems are not directly comparable, so this page does not convert that difference into a bloat or translation claim.

The public evidence retains only derived measurements, not title text. That protects brand, shop and product wording, but it also means a reader cannot re-tokenise these exact titles from the public file. The sampling script and metric definition are published so the method can be repeated against a later live draw.

The zero-residue result is deliberately narrow

120 of 120 subjectTrans values returned zero CJK characters. This rules out only one visible residue pattern in this draw. It does not establish that the English wording was accurate, complete, fluent or useful.

The official 1688 schema labels subject as the Chinese title and subjectTrans as the foreign-language title. It does not identify who authored the wording, what translation process produced it, or whether a website or app rendered the same value.

Search position is retained only to document the first-page sampling frame. No test links token repetition to rank, clicks, conversion or platform-reported sales.

How a buyer can use the result before payment

Treat an API-returned title as a discovery clue, not a product specification. Extract the exact product, material, size, variant and packaging you intend to buy, then confirm those details in structured attributes and a written supplier response.

Repeated words do not make an offer unsafe or a supplier unreliable. They are a reminder to move critical claims out of the title and into product-specific evidence that can be checked against the exact SKU and destination market.

If the title contains a compliance, performance or material claim, request the applicable document and confirm that it belongs to the product and market in question. This study validates none of those claims.

The stated limits, in full

All 9 of them travel inside the evidence file, so they stay attached to the data after it leaves this page.

1. 1.This is not a random sample. Rows come from the first page of a keyword search, which the platform ranks. Highly ranked listings may be optimised harder than average, in either direction.
2. 2.Title text is deliberately not published, because titles can contain brand and shop names. A reader can verify the metric definitions and re-run the repository-tracked sampling script, but cannot re-derive the counts from this file alone.
3. 3.A repeated token is not proof of bad faith, keyword stuffing, authorship or search strategy. The study reports a token-frequency threshold and does not infer why the wording occurred.
4. 4.Zero CJK characters is a narrow residue check. It does not establish that a translation was accurate, complete, fluent or suitable for buyers, and the official schema does not identify the translation process.
5. 5.Character counts across writing systems are not comparable and the length figures are description, not a bloat claim.
6. 6.The 12 keywords are ordinary consumer goods in English. Categories with regulated or technical naming may title differently and are not represented here.
7. 7.Single day of collection. Titles change, and no trend is claimed from one observation.
8. 8.The 120 rows correspond to 120 distinct offer IDs in the internal raw sample, but they are not 120 distinct suppliers. Seller identity is deliberately not collected, so the sample cannot be de-duplicated by shop and one seller may appear more than once.
9. 9.Nothing here says a platform or seller has done anything wrong. The study measures fields returned by one read-only API; it does not establish what a rendered website or app showed, who authored the title, how the wording was produced, or how buyers interpreted it.