Frozen archive

This report was produced on September 23, 2026. Scans are no longer run, and developer.mozilla.org may have changed since.

Readiness only — no security assessment was run on sites I don't own.

This scan is incomplete

3 checks could not retrieve content. The score reflects only what was readable.

Observed responses: 200 ×3, 404 ×3

Checks without content: llms_txt, agents_md, machine_endpoint

developer.mozilla.org

Scanned on September 23, 2026

48/100

Signal breakdown

The score above combines two different things: whether an agent can understand this site at all, and whether the site has adopted the emerging optional agent conventions. They're grouped separately here because a site can be excellent at one and have none of the other.

Comprehension

Whether an agent can read and understand the page at all.

41/58(71%)

Agent convention adoption

Whether the site has adopted the emerging optional agent conventions.

7/42(17%)

Tap a row to see how to fix it.

Do these first

The highest-impact fixes, ranked by points left on the table.

  1. 1
    Structured Data (JSON-LD)+14 pts available

    Add a JSON-LD <script type="application/ld+json"> tag to your homepage with schema.org structured data (e.g. Organization, WebSite, or Product).

  2. 2
    llms.txt+12 pts available

    Add a /llms.txt file at your site root: a plain-text/markdown document with a title and links describing your site for AI agents. See https://llmstxt.org for the convention.

  3. 3
    AGENTS.md+10 pts available

    Add an /AGENTS.md file at your site root with markdown headings describing how AI agents should interact with your project. See https://agents.md for the convention.

Scanned by AgentLitmusBot. Methodology v0.1. Source. All archived reports.