Skip to content
Dear.so logo

How AI assistants read dear.so

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

Run the full check on dear.so

← Back to Dear.so

Atlas Readinesssweptswept 2026-10-14

44/100

#159 of 165 rated Automation tools#12555 of 14530 in the Atlas
  • Entity0/25
  • Machine-readable22.8/35
  • Retrieval access20/20
  • Footprint1.5/20
all four parts read
What to fix firstfound in the sweep of 2026-10-14

No structured data on the site

critical

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

Usedsweptswept 2026-10-14

3/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
  • References2.3/30
out of 70 of 100 points — installs not read
Alivesweptswept 2026-10-14

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
  • Dear.so44
  • Automation medianof 166 rated58
  • Atlas medianof 18243 rated60
What the sweep readsweptswept 2026-10-14
  • Retrieval botsopenverify

    Whether the bots that decide citations are let in. Training bots are a separate list and are not counted here.

  • llms.txtnoverify

    A plain-text index at /llms.txt. Optional; read by some tools.

  • Organization schemano

    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 words440swept

    What a reader without JavaScript receives from the homepage.

  • Identity score65/100swept

    The analyzer's crawl-only section, 0-100: identity files, schema, crawler policy, sitemap. Not the analyzer score.

Position in Automationswept161 swept

65/100

identity score

0identity score, 0-100100
27th percentile of 161 · median 90

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 Dear.so's Atlas Readiness?

    44 of 100 on 2026-10-14, computed from four parts — entity, machine-readable, retrieval access, footprint — all four parts read. It places #159 of 165 rated Automation tools.

  • Does Dear.so let AI retrieval bots in?

    Yes. On 2026-10-14, robots.txt at dear.so disallowed none of the retrieval crawlers we check.

  • Does Dear.so publish an llms.txt?

    No: there was no /llms.txt at dear.so on 2026-10-14.

  • Is Dear.so a Wikidata entity?

    No item whose official website is dear.so was found on 2026-10-14.

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 dear.so →