Skip to content
Good for Bots

AIチェッカー

aibunsho.com

Free web tool that checks Japanese text for writing style, repetition and rhythm

Good for Bots: Fair, 50 of 100Get this badge →

On your homepage, it turns this report’s link to aibunsho.com dofollow.

Scanned

What is AIチェッカー?

AIチェッカー is a web tool for analyzing Japanese text. Users paste or upload Japanese text of 100 to 10,000 characters, and the tool checks its writing style, sentence rhythm, fixed expressions and repeated phrases, then shows a reference score with the main reasons. A free check requires no registration. The site states that the score is not the probability that text was generated by AI, and that an optional AI review sends the text to an external service, DeepSeek. The page addresses people who want to examine Japanese reports, essays or blog posts. Paid Basic and Pro plans add a full-text breakdown with detailed explanations, improvement suggestions and rewrite examples, within monthly word allowances. The homepage also says that the site does not store submitted text in its own database.

Through a bot’s eyes

“AIチェッカー is a free Japanese-language web tool that analyzes pasted text for writing style, repetition and rhythm and shows a reference score with main reasons, with paid Basic and Pro plans for detailed reports.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A model reading this homepage learns that the site is a Japanese-language tool for analyzing Japanese text. The text covers how the tool works in three steps, how scores should be read, a comparison of free and paid features, FAQ answers about AI detection limits, and privacy notes about sending text to an external provider. The facts a visitor would look for are present as text: the free price, the 100 to 10,000 character range, Basic at $4.99 for the first month then $9.99 per month, Pro at $14.99 then $29.99, and monthly word allowances of 60,000 and 260,000. The page repeats that a score is not an AI probability. The JSON-LD blocks add a WebSite, a WebPage, a WebApplication with a price of zero for the free tool, and an FAQPage whose five answers repeat the visible FAQ. Compared with the visible page, the structured data gives a machine-readable name, language and free price, but it does not include the paid plan prices.

What stays hidden

A model reading only this input cannot see the result of an actual check, because the results area shows only a placeholder until a user submits text. It cannot learn how the reference score is calculated beyond the listed features, the operator's name, its location or its contact details. The terms of the paid plans and the privacy policy are linked but were not read, so their content is unknown.

Good for Bots report

AIチェッカー scores 50 of 100: the whole readable base, none of the agent layer, no penalties.

Earned

The whole readable base above the line, none of the agent layer below it.

50

Still open

Behind the checks below, with prompts in Pro.

16
Penalties0
How scoring works · current methodology →

For the owner of aibunsho.com

3 prompts, 34 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

50 / 50

Passes.

3.3 of 3.3 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 8 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as WebSite, WebPage, ImageObject in valid schema.org JSON-LD.

Passes.

10 of 10 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.3 of 8.3 points.

10 of 10 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

76 of 76 assessed homepage links and buttons have a nonempty accessible name.

Passes.

2.5 of 2.5 points.

2 of 2 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

83 of 83 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.7 of 1.7 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

0 / 50

Fails.

0 of 11.3 points.

No /llms.txt on this site.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

Prompt in Pro →
Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 1513 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 203 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://aibunsho.com/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://aibunsho.com/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • goodforbotsbot (Site diagnostics)
    • * (Default robots group)
    • oai-searchbot (ai-search)
    • claude-searchbot (ai-search)
    • perplexitybot (ai-search)
    • mistralai-index (ai-search)
    • kimi-searchbot (ai-search)
    • amzn-searchbot (ai-search)
    • meta-webindexer (ai-search)
    • exasearchbot (ai-search)
    • aiwebindex (ai-search)
    • duckassistbot (ai-search)
    • shapbot (ai-search)
    • yandexadditional (ai-search)
    • yandexadditionalbot (ai-search)
    • gptbot (ai-training)
    • claudebot (ai-training)
    • mistralai-training (ai-training)
    • kimibot (ai-training)
    • ai2bot (Unknown)
    • applebot-extended (ai-training)
    • webzio-extended (ai-training)
    • chatgpt-user (user-fetch)
    • claude-user (user-fetch)
    • perplexity-user (user-fetch)
    • mistralai-user (user-fetch)
    • kimi-user (user-fetch)
    • amzn-user (user-fetch)
    • diffbot-user (user-fetch)
    • firecrawlagent (extraction)
    • webzio (extraction)
    • meta-externalfetcher (user-fetch, agent)
    • google-extended (ai-training, grounding)
    • meta-externalagent (ai-training, product-improvement)
    • amazonbot (ai-training, product-improvement)
    • ccbot (open-dataset, ai-training)
    • googlebot (search)
    • bingbot (search)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://aibunsho.com/

    https://aibunsho.com/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

60th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 60AIチェッカー · this reportaibunsho.com

The prompts in the owner view would take AIチェッカー to 84, 10th in its category.

To the prompts →

Category average 58. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
10 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
238.4 KB
Took
13.4 s
Homepage
203 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /ai-checker/guide/collection · linked from the homepage · from the sitemap · read
  • /pricing/pricing · linked from the homepage · from the sitemap · read
  • /free/linked from the homepage · from the sitemap · read

Do you run aibunsho.com? Open the owner view → Removing the listing is free. Remove →