columbia.com.tr valid
Columbia Türkiye
Columbia Türkiye (https://www.columbia.com.tr) is the official Turkish online store of the
For agents: Columbia Türkiye: official Turkish online store for Columbia outdoor apparel, with about 1,326 catalogue entries, facet filtering, stock and basket pricing rule
outdoor-clothingcolumbia-sportswearonline-storeproduct-catalogueturkey
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-21T14:48:47.033Z. Cached copy · Source on columbia.com.tr
# Columbia Türkiye
> Columbia Türkiye (https://www.columbia.com.tr) is the official Turkish online store of the
> Columbia Sportswear brand, operated first-party by Con-Teks İç ve Dış Ticaret A.Ş.: outdoor
> apparel, footwear, bags and equipment for men, women and children. The catalogue lists 1,326
> entries, but those are colourways rather than distinct models, so the number of designs is far
> smaller. Prices are in Turkish Lira and include VAT, delivery is within Türkiye only, and the
> catalogue is Turkish. This file is the agent-facing index; the canonical, complete instructions
> are at https://www.columbia.com.tr/agents.md.
**The shelf price is not the checkout price.** This is the one thing to get right here. On many
products `price.newPrice` is the list price while a basket campaign published separately in
`sectionGroupedTexts` cuts it hard — observed as "1 Üründe Sepette 6.874,95 TL" and "2 Ürün ve
Üzerinde Sepette 5.624,96 TL" on a product whose `price.newPrice` read 12.499,90 TL: a 45% / 55%
reduction that `percent`, `markdown` and `oldPrice` all report as zero. A second line adds a
members-only 5% ("Columbia Dünyası Üyelerine Sepette %5 İndirim"). Read `sectionGroupedTexts`
before quoting any price, say the campaign price applies in the basket, and never present the list
price as what the visitor pays.
**Read the payload — there is no structured data here.** Product pages emit **no JSON-LD**, **no
`rel="canonical"`**, **no Open Graph tags**, and a generic site-wide `<title>` of "Columbia Türkiye
Online Shop" whichever product you opened. Everything you can say about a product comes from
`<script id="__NEXT_DATA__">` under `props.pageProps` — a framework hydration channel, not a
versioned API, so guard every field access. The only JSON-LD is two home-page blocks, both partly
broken.
**Route each question to its surface:**
- Discovery → a category listing. `props.pageProps.productList` gives 24 cards per page plus
`dynamicFilters` with a `docCount` per gender, size, product type, product kind and colour.
- Search → `?searchValue={query}` on any listing route, but **it always searches the whole
catalogue**: `/erkek?searchValue=mont` and `/tum-urunler?searchValue=mont` both returned 202
results and `currentFilter.slug` came back `null`. No matches returns 200 with **no `productList`
key** — and so does a 404 page, so check the status before reading absence as zero results.
Ignore the home page's `SearchAction`: its target is `/false{search_term_string}`, a literal
`false` where the path belongs, and following it 404s.
- Filtering → facet parameters reach the server, but only by **id**: `?Cinsiyet=34`, `?color=822`,
`?size=5`, `?Ürün Tipi=110`, `?Ürün Cinsi=5666` — comma-separated for OR, combined for AND, ids
from `dynamicFilters[].filters[].id`. A label instead (`?size=S`) returns **HTTP 504**. Don't.
- Stock by size → the product page, `variants[].quantity`. `totalQuantity` is only the variant the
URL resolved t
…
Related sites
Other listed sites in Ecommerce. See the whole category →
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| intellweb.ai | Intellweb | documentation Ecommerce Productivity +3 | US | 61 | ✓ | ✓ | |
| shopify.com | Shopify | transactional Ecommerce | CA | 77 | ✓ | ✓ | |
| wordpress.org | WordPress | transactional Media Ecommerce | US | 77 | ✓ | ||
| forter.com | Forter — Identity Intelligence for Digital Commerce | interface Ecommerce Cybersecurity +1 | US | 75 | ✓ | ✓ | |
| conviva.com | Conviva | informational AI and machine learning Data and analytics +2 | US | 70 | ✓ | ✓ | |
| dell.com | Dell Technologies | transactional Consumer electronics Ecommerce | US | 70 | ✓ | ||
| mattel.com | Mattel Shop | transactional Ecommerce | CA | 70 | ✓ | ✓ | |
| one.one | one.com | transactional Ecommerce Infrastructure | DK | 70 | ✓ |
Machine-readable: GET /v1/resolve?q=columbia.com.tr · GET /v1/domain/columbia.com.tr · 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.
Own or manage this website?
If you own or manage columbia.com.tr, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for columbia.com.tr:
1. POST https://agentwebmap.com/v1/sites/columbia.com.tr/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://columbia.com.tr/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/columbia.com.tr/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/columbia.com.tr).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.