Skip to content
Inescapable Detail logo

How AI assistants read inescapable.app

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 Inescapable Detail; the catalogue page is for the people who choose it.

Run the full check on inescapable.app

← Back to Inescapable Detail

Atlas Readinesssweptchecked 2026-10-31

59/100

  • Entity0/25
  • Machine-readable30.1/35
  • Retrieval access17/20
  • Footprintnot read
out of 80 of 100 points — footprint not read
What to fix firstfound in our 2026-10-31 check

7 retrieval crawlers are blocked on /office

high

The heaviest thing this check found wrong, named in the words our fix list uses. Read off the site itself, not from a model.

Usedsweptchecked 2026-10-31

not read yet

Does anybody use it: audience (Tranco list, Chrome UX report, estimated organic visits), installs from registries, referring domains. Never votes, never reviews.

  • Audiencenot read
  • Installsnot read
  • Referencesnot read
nothing read yet
Alivesweptchecked 2026-10-31

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
out of 60 of 100 points — ships and hiring not read
Against the fieldsweptreadiness, out of 100
  • Inescapable Detail59
  • Atlas medianof 27479 rated61
What our weekly check readsweptchecked 2026-10-31
  • Retrieval botspartialverify

    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 words40swept

    What a reader without JavaScript receives from the homepage.

  • Identity score86/100swept

    The analyzer's crawl-only section, 0-100: identity files, schema, crawler policy, sitemap. Not the analyzer 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.

Questions this page answers
  • What is Inescapable Detail's Atlas Readiness?

    59 of 100 on 2026-10-31, computed from four parts — entity, machine-readable, retrieval access, footprint — out of 80 of 100 points — footprint not read.

  • Does Inescapable Detail let AI retrieval bots in?

    Partly. On 2026-10-31, inescapable.app fenced some paths from retrieval crawlers.

  • Does Inescapable Detail publish an llms.txt?

    Yes: inescapable.app/llms.txt was present on 2026-10-31.

  • Is Inescapable Detail a Wikidata entity?

    No item whose official website is inescapable.app was found on 2026-10-31.

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.

Run the full check on inescapable.app →