Does ymobile.jp allow OAI-SearchBot? robots.txt as of 2026-09-12
On 2026-09-12 the robots.txt of ymobile.jp resolved 19 AI crawler tokens: 19 allowed for / and 0 disallowed for /.
| Domain | ymobile.jp |
|---|---|
| AI crawler tokens resolved | 19 |
| Allowed for / | 19 |
| Disallowed for / | 0 |
| robots.txt | robots.txt present, 48212 bytes |
| Checks that ran | robots |
| robots.txt read (tier A) | 2026-09-12 |
| Last verified |
On this domain the robots.txt only check (tier A) last ran on 2026-09-12. The full check adds the home page, the labelled edge probes, llms.txt, the headers and the structured data; the robots.txt check is the one that runs weekly for every seeded domain.
One question per crawler
- GPTBot
- ClaudeBot
- PerplexityBot
- OAI-SearchBot
- CCBot
- Bytespider
- Googlebot
- ChatGPT-User
- Google-Extended
Does ymobile.jp allow GPTBot? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow GPTBot
User-agent: GPTBot Allow: /
User-agent: GPTBot Disallow: /
The GPTBot guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow ClaudeBot? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow ClaudeBot
User-agent: ClaudeBot Allow: /
User-agent: ClaudeBot Disallow: /
The ClaudeBot guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow PerplexityBot? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow PerplexityBot
User-agent: PerplexityBot Allow: /
User-agent: PerplexityBot Disallow: /
The PerplexityBot guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow OAI-SearchBot? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow OAI-SearchBot
User-agent: OAI-SearchBot Allow: /
User-agent: OAI-SearchBot Disallow: /
The OAI-SearchBot guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow CCBot? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow CCBot
User-agent: CCBot Allow: /
User-agent: CCBot Disallow: /
The CCBot guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow Bytespider? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow Bytespider
User-agent: Bytespider Allow: /
User-agent: Bytespider Disallow: /
The Bytespider guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow Googlebot? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow Googlebot
User-agent: Googlebot Allow: /
User-agent: Googlebot Disallow: /
The Googlebot guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow ChatGPT-User? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow ChatGPT-User
User-agent: ChatGPT-User Allow: /
User-agent: ChatGPT-User Disallow: /
The ChatGPT-User guide: identity, purpose, documented verification and the vendor sources.
Does ymobile.jp allow Google-Extended? robots.txt as of 2026-09-12
allowed for /
robots.txt has a User-agent: * group with no rule matching / , so / is allowed
Observed 2026-09-12, first observed 2026-09-12, last change recorded 2026-09-12.
Allow or disallow Google-Extended
User-agent: Google-Extended Allow: /
User-agent: Google-Extended Disallow: /
The Google-Extended guide: identity, purpose, documented verification and the vendor sources.
Every crawler token in the registry
| Crawler | Vendor | Observation | Evidence | Observed |
|---|---|---|---|---|
| GPTBot | OpenAI | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| ClaudeBot | Anthropic | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| PerplexityBot | Perplexity | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| OAI-SearchBot | OpenAI | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| CCBot | Common Crawl Foundation | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Bytespider | ByteDance | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Googlebot | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 | |
| ChatGPT-User | OpenAI | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Claude-User | Anthropic | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Claude-SearchBot | Anthropic | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Perplexity-User | Perplexity | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| anthropic-ai | Anthropic | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Bingbot | Microsoft | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Applebot | Apple | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Amazonbot | Amazon | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| meta-externalagent | Meta | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| DuckAssistBot | DuckDuckGo | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Applebot-Extended | Apple | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
| Google-Extended | allowed for / | robots.txt has a User-agent: * group with no rule matching / , so / is allowed | 2026-09-12 |
What else the robots.txt says
| agents-summary | AI crawler rules: 19 allowed, 0 disallowed 19 crawler tokens resolved against https://ymobile.jp/robots.txt (HTTP 200, 48212 bytes) at 2026-09-12T02:12:05Z |
|---|---|
| file | robots.txt present, 48212 bytes GET https://ymobile.jp/robots.txt at 2026-09-12T02:12:05Z returned HTTP 200, 48212 bytes, content type text/plain, 1 user agent group(s) |
| sitemap-declared | 3 sitemap(s) declared in robots.txt line 1069: "Sitemap: /sitemap.xml"; line 1070: "Sitemap: /sitemap.xml?wovn=en"; line 1071: "Sitemap: /support/contact/sitemap.xml" |
History
Every robots.txt version we have observed for ymobile.jp.
Check your own site
The same checks, run on your domain now: what robots.txt tells each AI crawler, whether the edge answers them, and whether the text is readable without JavaScript. Free, no signup.
Limits: 8 checks and 5 different domains per address per hour; a repeat of the same domain inside 7 days is answered from what we already hold.
Limitation: this test appends a labelled marker to our own honest User Agent, it never impersonates another agent. Rules keyed to an exact User Agent string, or to a vendor's IP ranges, are invisible to this method and are neither confirmed nor ruled out.
AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.