wear.jp
In its own wordsLooks like: Software or appThis service is not available in your region.
In its own wordsLooks like: Software or appThis service is not available in your region.
wear.jp looks like a software product or app, is ranked in the top 10,000 sites and was registered in 2001. It uses Cloudflare, Amazon CloudFront and Akamai Edge DNS; we found no traces of an AI site builder.
The page shows little text before JavaScript runs. Sites drawn by JavaScript show fewer signals until we can render them in a browser.
Among the top 10K sites.
A popularity band, not a visit count.
Tranco: #16,925 · Chrome UX Report: Top 10,000 · Majestic Million: #71,325
| Source | Says | As of |
|---|---|---|
| TrancoA research ranking that combines several traffic and link sources, published daily. | #16,925 | list of 27 Oct 2026 |
| Chrome UX ReportRank buckets from Google’s real Chrome traffic, published monthly. | Top 10,000 | Sep 2026 |
| Majestic MillionRanks sites by how many separate networks link to them (links, not visits), published daily. CC BY 3.0 | #71,325 | list of 28 Oct 2026 |
No framework or CMS shows in the page; it uses CDN, DNS, Email, Marketing and more.
Around it: CDN, DNS, Email, Marketing and more.
cf-ray: a52b3ee9aea51243-ARN
x-amz-cf-id: T8uA3Z3QZV4wocQKfV8m9E8HhacS-KPwyUWfD2oK-YQt60CFAfelJg==
wear.jp NS a5-66.akam.net.
wear.jp MX 10 inbound-smtp.ap-northeast-1.amazonaws.com.
wear.jp TXT v=spf1 +ip4:175.111.83.0/26 +ip4:202.143.82.0/24 include:spf-bma.mpme.jp include:_spf.salesforce.com include:amazonses.com include:mail.zendesk.com ~all
wear.jp TXT v=spf1 +ip4:175.111.83.0/26 +ip4:202.143.82.0/24 include:spf-bma.mpme.jp include:_spf.salesforce.com include:amazonses.com include:mail.zendesk.com ~all
wear.jp TXT _globalsign-domain-verification=ee9u9eWQf69SG-9x-i1CR9W037T829g1sB06WJjW5w
Business tools can stay listed after a site stops using them.
We couldn’t read the page; outside records are below.
Signals, not a judgement: missing details are common on small, honest sites.
A second opinion on its security setup: Mozilla’s HTTP Observatory grades the site when you open it. Ten checks before you buy · A signal looks wrong? Report it
Looks like: Software or app.
In its own wordsThis service is not available in your region.
Our reading of the page, medium confidence.
Q111114304: WEAR, mobile app
Wikidata: Owned by Zozo.
Q111114304: WEAR
Each name is quoted from its source. A brand and the company that owns it often go by different names.
Wikidata, the free knowledge base behind Wikipedia, lists this domain as the official website of this item. Volunteers write it; each item shows its sources.
User-agent: ClaudeBot
User-agent: GPTBot
User-agent: Meta-ExternalAgent
What its robots.txt and robots tags ask of AI crawlers. Each crawler chooses whether to follow it.
Read from what the page says about itself; we haven’t checked whether it’s true.
No AI builder traces found.
Coding tools such as Cursor leave no traces, so this doesn’t mean a person made it.
AI traces: None found
AI site builders leave traces in the sites they make. We look for the traces of 53 of them and show every match with the line it came from, so you can check it yourself.
We test this on 2,275 sites whose makers we know, and publish what we get wrong.
How we test it · Every builder we know · How to tell if a site was built with AI
AI tools may not reach it: it scores 22 of 100.
It lets every AI crawler in: the site’s choice, never scored.
AI readiness
AI tools may not reach its pages.
To reach Findable:Search listing +15
Optional: for sites with an API or a sign-in.
Below the median of the 2,439 most visited sites we read, which is 72.
Text without scripts
Now Little, 171 characters: scripts draw the rest.
Put the page’s text in its HTML, rendered on the server or at build time.
Why it matters: Most AI crawlers don’t run scripts: they read only what the HTML holds.
This service is not available in your region. This service is not available in your region. We terminated our fashion service WEAR in the EU and its neighboring countries as of February 29, 2020.…
The home page of https://cdn.wimg.jp sends only 171 characters of text before its scripts run, so AI crawlers that don’t run JavaScript see an almost empty page. Make the server send the page’s content in its HTML: render it on the server, or prerender each page at build time (static generation), so its headings, text and links are in the HTML before any script runs. Keep the interactive parts working as they do now.
Search listing
Now Asks search engines not to list it.
Remove the noindex rule, if the page should appear in search and AI answers.
Why it matters: A page search engines leave out is also left out of the AI answers built on them.
<meta name="robots" content="noindex,nofollow,noydir,noodp">
The home page of https://cdn.wimg.jp asks search engines not to list it: <meta name="robots" content="noindex,nofollow,noydir,noodp">. If the site should appear in search results and in the AI answers built on them, remove noindex (and none) from its robots meta tags and from any X-Robots-Tag header the server sends for it. Keep noindex only on pages that must stay out of search.
Structured data
Now None found.
Add schema.org structured data, as JSON-LD, to the home page’s HTML.
Why it matters: Structured data tells AI tools and search engines what the site is: a company, a shop, a product.
Add schema.org structured data to the home page of https://cdn.wimg.jp as JSON-LD, in a <script type="application/ld+json"> tag in its HTML: an Organization with its name, url, logo and sameAs links to its official profiles, and a WebSite with its name and url. Add the type that fits what the site offers too, such as Product, Article or LocalBusiness. Use only facts that are true of the site.
Title and descriptionIn part
Now A title, no description.
Give the home page a title and a meta description in its HTML.
Why it matters: A title and a description are the words AI tools and search engines quote first.
<title>This service is not available in your region.</title>
Give the home page of https://cdn.wimg.jp a descriptive <title> and a <meta name="description" content="…"> of about 150 characters that says what the site is and offers (we found: a title, no description). Put both in the HTML the server sends, not set later by scripts.
Files for AI agents
Now None of the 8 we look for.
If agents could use the site, publish what they need where they look.
Why it matters: Agents act for people: they look for these files to know what a site lets them do. Worth it only if agents can use the site.
If AI agents could use https://cdn.wimg.jp for its visitors (to search it, book, buy or sign in), publish what they need at the standard addresses, and only what the site really offers: an MCP server card at /.well-known/mcp/server-card.json if it runs an MCP server, an API catalog at /.well-known/api-catalog (RFC 9727) listing its public APIs, and OAuth protected resource metadata at /.well-known/oauth-protected-resource (RFC 9728) if agents sign in.
llms.txt
Now None found.
Publish a short Markdown summary of the site at /llms.txt.
Why it matters: A short summary for AI models, at an address they can find. A proposal: few AI companies say they read it yet.
Create https://cdn.wimg.jp/llms.txt as llmstxt.org describes it: a Markdown file with an H1 naming the site, a one-paragraph summary in a blockquote, and short sections listing its most useful pages as links, each with a line on what it holds. Serve it as text/plain or text/markdown.
Links for AI tools
Now None in the home page’s headers.
Point AI tools to the site’s files in the home page’s Link header.
Why it matters: A Link header points AI tools to a site’s files from any page, without guessing addresses.
Make the home page of https://cdn.wimg.jp send a Link header (RFC 8288) that points AI tools to the site’s files, for example: Link: </sitemap.xml>; rel="sitemap", </llms.txt>; rel="describedby"; type="text/plain". List only files the site serves.
Markdown copy
Now Not offered: it sends the page’s HTML.
Answer requests for Markdown with a Markdown version of the page.
Why it matters: A Markdown copy gives AI tools the page’s words without the HTML around them.
When a request to https://cdn.wimg.jp asks for Markdown (its Accept header includes text/markdown), answer with a Markdown version of the page’s main content and the header Content-Type: text/markdown. Requests for HTML keep getting HTML; add Vary: Accept so caches keep the two apart.
Sitemap: https://wear.jp/sitemap.xml.gz
<meta name="robots" content="noindex,nofollow,noydir,noodp">
This service is not available in your region. This service is not available in your region. We terminated our fashion service WEAR in the EU and its neighboring countries as of February 29, 2020.…
<title>This service is not available in your region.</title>
Keeping AI out is the site’s choice, so it never lowers the score.
GPTBotline 24, some pathsTo answer people and searchLet inOAI-SearchBotChatGPT-UserClaudeBotline 12, some pathsanthropic-ailet inClaude-Weblet inTo answer people and searchLet inClaude-SearchBotClaude-UserGoogle-ExtendedTo answer people and searchLet inGoogle-CloudVertexBotPerplexityBotPerplexity-Usermeta-externalagentline 36, some pathsFacebookBotlet inTo answer people and searchPartlymeta-externalfetcherlet inmeta-webindexerline 48, some pathsApplebot-ExtendedTo answer people and searchNone namedAmazonbotTo answer people and searchLet inAmzn-SearchBotAmzn-UserCCBotTo answer people and searchNone namedBytespiderTikTokSpiderTo answer people and searchNone namedMistralAI-UserNone of the 27 other AI crawlers we know is kept out.
It gives no Content Signals and no “noai” tag.
Like 68% of the 1,691 popular sites whose robots.txt we read in October 2026, it keeps no AI training crawler out. How many websites block AI crawlers?
We read the site once, as our named bot: its robots.txt, read as crawlers read it, its home page and the files AI tools ask sites for. What we couldn’t read says so. robots.txt asks and doesn’t enforce: a firewall can treat AI crawlers differently from us.
80 of 100: strong trust signals.
How established and checkable it is; AI traces carry no weight.
Scored on the parts we could check.
A high score isn’t a promise that a business is honest. How the score works.
Registered in 2001.
The web archive couldn’t be reached; we’ll ask it again. Why can this be empty?
Only from what anyone can see: the site’s public pages and public records.
934 checks on 30 Oct 2026, with version 0.6.0 of our checks and version 1.1 of the score.
It looks like a software product or app. See the evidence
Its domain was registered on 26 Mar 2001, 25 years ago. See the evidence
It uses Cloudflare, Amazon CloudFront and Akamai Edge DNS; we found 7 technologies in all. See the evidence
It is among the top 10,000 sites, by Tranco, Chrome UX Report and Majestic Million. See the evidence
We found no traces of an AI site builder. That doesn’t prove a person built it: AI coding assistants leave no traces. See the evidence
Wikidata names WEAR. See the evidence
Automated findings from the site’s public home page and public records, as of 30 Oct 2026. They describe what we found, not the people or business behind the site, and they may be incomplete or out of date. This is information, not advice. Terms · Report an error
Is this your site? Ask for a correction.