championturkiye.com valid

Champion Türkiye

Champion Türkiye (https://www.championturkiye.com) is the licensed Turkish online store for

For agents: Licensed Turkish online store for Champion sportswear: about 1,384 products for men, women and kids, with search and agent-facing catalogue and stock docs.

sportswearturkish online storeproduct cataloguechampion apparelagent instructions

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:28:30.548Z. Cached copy · Source on championturkiye.com

# Champion Türkiye

> Champion Türkiye (https://www.championturkiye.com) is the licensed Turkish online store for
> Champion apparel, footwear and accessories, run by Ünal Perakende Spor Ürünleri İthalat İhracat
> A.Ş., Champion's Türkiye distributor since 2023. The catalogue listing reports 1,384 products for
> men, women, kids and unisex, sold first-party. Prices are in Turkish Lira and include VAT,
> delivery is within Türkiye only, and the storefront is Turkish-only. This file is the agent-facing
> index; the canonical, complete instructions are at https://www.championturkiye.com/agents.md.

**Never trust `availability` on this store.** Every product page emits
`"availability": "https://schema.org/InStock "` — trailing space included, and regardless of stock.
Of 40 products drawn at random from the product sitemap, 18 had `quantity: 0` in **every** size and
still declared `InStock`; `addToBasketDisabled` read `false` on all of them too. Answer stock from
`props.pageProps.product.variants[].quantity` and nothing else. The sitemap holds ~3,020 product
URLs against 1,384 in the catalogue listing, so a 200 is not evidence a product is still sold.

**Read the page, not the DOM.** Every response carries three layers: rendered HTML, schema.org
JSON-LD, and the server data in `<script id="__NEXT_DATA__" type="application/json">` under
`props.pageProps`. One GET answers most questions. JSON-LD here is thin and partly broken (see
above); the payload is a rich but unversioned supplement whose field names can change with any
release, so guard every field access. Policy pages differ again: their text sits in
`page.data[0].attributes.page_content` as nested CMS rows, much of it Draft.js JSON inside a string,
and some of it never reaches the HTML.

**Pagination is 1-based in the URL and 0-based in the payload.** `?pageIndex=1` returns the first
page — the same 24 `variantId`s as no parameter at all — while the payload echoes
`products.index: 0`; `?pageIndex=2` returns the second. **`?pageIndex=0` returns HTTP 504 Gateway
Timeout** with `Retry-After: 120`, reproducibly, on `/tum-urunler`, `/erkek` and `/kadin`. A
`pageIndex` past `totalPages` returns 404. Page size is 24. Sibling storefronts on this platform are
0-based; do not carry the assumption across.

**Route each question to its surface:**

- Product discovery → a category listing. `products.data[]` carries 24 cards with `price`, per-size `variants[].quantity`, `totalStock` and `badges`, plus `dynamicFilters` with a `docCount` per product type, gender, size, colour and **Fit Bilgisi** value.
- Full-text search → `?searchValue={query}` on `/tum-urunler`. Category pages accept it but **silently discard the category**: `/erkek?searchValue=hoodie` returned the same 321 hits in the same order as `/tum-urunler?searchValue=hoodie`, with `categoryModel: null`. A query with no matches omits `productList` entirely — absence means zero results, not an error. No `WebSite`/`SearchAction` JSON-LD exists on this sto
…

Related sites

Other listed sites in Ecommerce. See the whole category →

Machine-readable: GET /v1/resolve?q=championturkiye.com · GET /v1/domain/championturkiye.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for championturkiye.com:
1. POST https://agentwebmap.com/v1/sites/championturkiye.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://championturkiye.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/championturkiye.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/championturkiye.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.