Lingo.dev
Translates application content using language models and native speakers, with quality scoring and continuous localization pipelines.
59/100
- Entity0/25
- Machine-readable22.8/35
- Retrieval access17/20
- Footprint18.7/20
- Lingo.dev59
- Localization medianof 5 rated90
- Atlas medianof 537 rated61
- 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 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 words767swept
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.
- Footprint5.4k GitHub stars
65/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 Lingo.dev?
Translates application content using language models and native speakers, with quality scoring and continuous localization pipelines.
What is Lingo.dev's Atlas Readiness?
59 of 100 on 2026-09-15, computed from four parts — entity, machine-readable, retrieval access, footprint — all four parts read. It places #5 of 5 rated Localization tools.
Does Lingo.dev let AI retrieval bots in?
Partly. On 2026-09-15, lingo.dev fenced some paths from retrieval crawlers.
Does Lingo.dev publish an llms.txt?
Yes: lingo.dev/llms.txt was present on 2026-09-15.
Is Lingo.dev a Wikidata entity?
No item whose official website is lingo.dev was found on 2026-09-15.
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.