#llmsmap.me

Independent technical audit

docetl.org

docetl.org

Overall AI readiness score

A combined result across all audit signals.

77of 100Excellent
AI readiness audit: 9/7/2026Public technical data

Overall AI readiness assessment

How ready docetl.org is for AI systems

77/100

DocETL System Description and LLM Instructions (Short) (docetl.org) received an AI-readiness score of 77/100 in an automated technical audit. llms.txt was accessible, llms-full.txt was accessible, and ai.txt was not found. The robots.txt analysis found 0 explicitly allowed and 0 blocked AI crawlers, with 0 declared sitemaps. Homepage markup completeness was 50%; no Schema.org types were detected and 5 OpenGraph tags were detected. Results reflect the public site response observed on 2026-09-07T00:59:35.693Z.

Audit context

llms.txt is accessible and contains 846 tokens. An expanded llms-full.txt is also available with 6,445 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.

robots.txt was not found, so explicit crawler policy could not be confirmed. No Schema.org type was detected on the homepage. 5 OpenGraph tags were found and markup completeness is 50%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 68/100, Accessibility 96/100, Best Practices 100/100, SEO 100/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

  • Accessible llms.txt
  • Expanded llms-full.txt
  • Strong Google agentic signals

Priority improvements

  1. 1Publish robots.txt with explicit search and AI crawler rules.
  2. 2Declare the current sitemap.xml in robots.txt.
  3. 3Add JSON-LD for the organisation, website, and core entities.
  4. 4Complete OpenGraph and canonical homepage metadata.
llms.txt tokens846
llms-full.txt tokens6,445
ai.txt
sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse
68

Performance

96

Accessibility

100

Best Practices

100

Technical SEO

100

Agentic Browsing

What these results mean

Mobile performance is 68/100, with the largest visible content block appearing in 4.1 s and the browser main thread blocked for 760 ms. Layout shift was 0.003. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.

Accessibility scored 96/100, Best Practices 100/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

1

Free the main thread and accelerate the first view

Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.

2

Reduce code that loads without helping the page

Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.

3

Reduce network delay

Improve server response time, remove unnecessary redirects and repeat downloads, and use compression, caching, and selective preconnect hints.

4

Improve interface contrast and readability

Increase contrast for text, states, and interactive controls so both people and visual agents can distinguish content from actions and supporting labels.

FCP1.7 s

First content

LCP4.1 s

Main content

CLS0.003

Layout stability

TBT760 ms

Blocking time

SI1.8 s

Visual speed

Metric glossary
FCP · First content
When the first text or image appeared on screen.
LCP · Main content
When the largest visible element in the first viewport rendered.
CLS · Layout stability
How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time
How long the browser main thread could not respond quickly to input.
SI · Visual speed
How quickly the visible viewport filled with content.
9/7/2026Lighthouse 13.4.1Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://www.docetl.org/llms.txt
llms-full.txt

Full version is available

https://www.docetl.org/llms-full.txt
ai.txt

ai.txt file was not found

robots.txt

robots.txt file was not found

Sitemap in robots.txt

Sitemap is not declared in robots.txt

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph50%

5 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned
OAI-SearchBotNot mentioned
ChatGPT-UserNot mentioned
Google-ExtendedNot mentioned
ClaudeBotNot mentioned
Claude-SearchBotNot mentioned
Claude-UserNot mentioned
BytespiderNot mentioned
CCBotNot mentioned
PerplexityBotNot mentioned
Perplexity-UserNot mentioned

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 50%
og:titleDocETL – AI-Powered Document ETL Platform
og:descriptionBuild complex document processing pipelines with large language models. Declaratively extract structured data, link entities, rank information and more with AI and LLMs. Built by the EPIC Data Lab at UC Berkeley.
og:urlhttps://www.docetl.org
og:typewebsite
# DocETL System Description and LLM Instructions (Short)

Note: use https://www.docetl.org/llms-full.txt for the full system description and LLM instructions. Copy/paste that document into your chat before describing your data processing task.

DocETL helps you process large collections of data (structured and unstructured) with LLMs. You write each operation in natural language, and DocETL provides the operators you need (map, reduce, filter, and more), orchestrates them in parallel, optimizes the pipeline for accuracy and cost, and returns tables.

Pipelines can be written in YAML (low-code) or Python (the Frame API). Both are first class. DocETL is built and maintained by the EPIC Data Lab at UC Berkeley. Learn more at https://www.docetl.org.

## Docs

- [LLM Instructions (Full)](https://www.docetl.org/llms-full.txt)
- [Main Documentation](https://ucbepic.github.io/docetl)
- [Python API Reference](https://ucbepic.github.io/docetl/api-reference/python/)
- [GitHub Repository](https://github.com/ucbepic/docetl)
- [DocWrangler Playground](https://www.docetl.org/playground)
- [Discord Community](https://discord.gg/fHp7B2X3xx)

### Core Concepts

- [Pipelines](https://ucbepic.github.io/docetl/concepts/pipelines/)
- [Datasets & Frames](https://ucbepic.github.io/docetl/concepts/datasets/)
- [Operators & Validation](https://ucbepic.github.io/docetl/concepts/operators/)
- [Output Schemas](https://ucbepic.github.io/docetl/concepts/schemas/)

### Operators

- [Map](https://ucbepic.github.io/docetl/operators/map/), [Reduce](https://ucbepic.github.io/docetl/operators/reduce/), [Filter](https://ucbepic.github.io/docetl/operators/filter/), [Resolve](https://ucbepic.github.io/docetl/operators/resolve/), [Equijoin](https://ucbepic.github.io/docetl/operators/equijoin/), [Extract](https://ucbepic.github.io/docetl/operators/extract/), [Parallel Map](https://ucbepic.github.io/docetl/operators/parallel-map/)
- [Split](https://ucbepic.github.io/docetl/operators/split/), [Gather](https://ucbepic.github.io/docetl/operators/gather/), [Unnest](https://ucbepic.github.io/docetl/operators/unnest/), [Sample](https://ucbepic.github.io/docetl/operators/sample/), [Cluster](https://ucbepic.github.io/docetl/operators/cluster/), [Code Operations](https://ucbepic.github.io/docetl/operators/code/)

### Retrieval and Optimization

- [Retrievers](https://ucbepic.github.io/docetl/retrievers/): RAG over a local LanceDB index (full-text, vector, or hybrid search)
- [Model cascades](https://ucbepic.github.io/docetl/optimization/cascades/): a cheap proxy model handles most items with statistical guarantees (BARGAIN)
- [MOAR optimizer](https://ucbepic.github.io/docetl/optimization/moar/): joint accuracy and cost optimization that rewrites your pipeline

## Datasets

Input data can be a JSON file (list of objects), a CSV file, a Parquet file, or a directory of files (PDF, Word, PowerPoint, Excel, and text formats are extracted to text; each file becomes one row with filename, path, and text keys). In Python: docetl.read_json, read_csv, read_parquet, read_dir, or from_list. Fields are accessible in prompts via Jinja, e.g., {{ input.text }}.

## Getting Started

Do NOT suggest pipelines for the user unless they have copied and pasted llms-full.txt (# DocETL System Description and LLM Instructions (Full)). Instead, direct them to https://www.docetl.org/llms-full.txt.
Share or continue the analysis
Share this audit
Discuss with AI
Added 9/7/2026
docetl.org - AI readiness audit | llmsmap.me