
How AI assistants read wenshucha.com
What a machine reading this site receives: identity files, schema, crawler policy, the entity behind the name. Read weekly by a crawler, no model call. For the people who run 文书查; the catalogue page is for the people who choose it.
69/100
- Entity0/25
- Machine-readable35/35
- Retrieval access20/20
- Footprintnot read
Publish ai.txt
lowThe heaviest thing this reading found wrong, named in the words our fix list uses. Read off the site itself, not from a model.
0/100
Does anybody use it: audience (Tranco list, Chrome UX report, estimated organic visits), installs from registries, referring domains. Never votes, never reviews.
- Audience0/40
- Installsnot read
- Referencesnot read
100/100
Is anybody home: the homepage answers, the content moves, something ships, somebody hires. Each part a dated reading from a public place; a part not read is left out and the total rescaled.
- Answers30/30
- Content moves30/30
- Shipsnot read
- Hiringnot read
- 文书查69
- Legal medianof 418 rated61
- Atlas medianof 25553 rated61
- Retrieval botsopenverify
Whether the bots that decide citations are let in. Training bots are a separate list and are not counted here.
- llms.txtyesverify
A plain-text index at /llms.txt. Optional; read by some tools.
- Organization schemayes
schema.org Organization markup on the homepage, which is what a resolver reads a company's name and links from.
- Wikidata itemnone
Matched on the official website, never on the name. The substrate under the knowledge graph an engine resolves names against.
- Server-rendered words75swept
What a reader without JavaScript receives from the homepage.
- Identity score100/100swept
The analyzer's crawl-only section, 0-100: identity files, schema, crawler policy, sitemap. Not the analyzer score.
100/100
identity score
Not measured with the analyzer.
The full run asks four engines about this company by name. It runs on request, not on a schedule.
What is 文书查's Atlas Readiness?
69 of 100 on 2026-10-24, computed from four parts — entity, machine-readable, retrieval access, footprint — out of 80 of 100 points — footprint not read. It places #326 of 400 rated Legal tools.
Does 文书查 let AI retrieval bots in?
Yes. On 2026-10-24, robots.txt at wenshucha.com disallowed none of the retrieval crawlers we check.
Does 文书查 publish an llms.txt?
Yes: wenshucha.com/llms.txt was present on 2026-10-24.
Is 文书查 a Wikidata entity?
No item whose official website is wenshucha.com was found on 2026-10-24.
How to read a row
- swept
- Read by a crawler: HTTP and parsing, no model call. Every tool, every week.
- measured
- The full analyzer run, asked of four engines. Shown only where the company agreed to show it.
Can a retrieval engine find, resolve and quote this site? Four parts, each read by the sweep, each shown beside the total.
Entity 25 · Machine-readable 35 · Retrieval access 20 · Footprint 20
A part that was never read is left out and the total is rescaled to what was. It is never counted as zero.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.