Skip to content

How AI assistants read trigger.dev

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

← Back to Trigger.dev

Atlas Readinesssweptswept 2026-09-14

69/100

#19 of 109 rated Automation tools#231 of 728 in the Atlas
  • Entity0/25
  • Machine-readable31.5/35
  • Retrieval access17/20
  • Footprint20/20
all four parts read
Usedsweptswept 2026-09-14

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

55/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 movesnot read
  • Ships0/25
  • Hiringnot read
out of 55 of 100 points — content moves and hiring not read
Against the fieldsweptreadiness, out of 100
  • Trigger.dev69
  • Automation medianof 121 rated59
  • Atlas medianof 1015 rated60
What the sweep readsweptswept 2026-09-14
  • 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 words2kswept

    What a reader without JavaScript receives from the homepage.

  • Identity score90/100swept

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

  • Footprint28k GitHub stars
Position in Automationswept119 swept

90/100

identity score

0identity score, 0-100100
56th percentile of 119 · 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 Trigger.dev's Atlas Readiness?

    69 of 100 on 2026-09-14, computed from four parts — entity, machine-readable, retrieval access, footprint — all four parts read. It places #19 of 109 rated Automation tools.

  • Does Trigger.dev let AI retrieval bots in?

    Partly. On 2026-09-14, trigger.dev fenced some paths from retrieval crawlers.

  • Does Trigger.dev publish an llms.txt?

    Yes: trigger.dev/llms.txt was present on 2026-09-14.

  • Is Trigger.dev a Wikidata entity?

    No item whose official website is trigger.dev was found on 2026-09-14.

How to read a row

swept
Read by a crawler: HTTP and parsing, no model call. Every row, 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.

Measure your own site →