AgenticWebScore
Scan

rubric v0.9 · scanned

developer.mozilla.org

Verdict

61.8
out of 100

L3 · Machine-readable

Web standards 88.3 · Agent conventions 0

Usable by agents: No action surface found

L3 is the highest level for a site with no action surface: L4 needs a working MCP server or a documented API. Read the level rules

Readable: HTTP 200 at https://developer.mozilla.org/en-US/, 899 words in the HTML. 3 to fix, 2 optional choices, 5 agent conventions not used, and 38 out of scope.

How this was measured

Measured at https://developer.mozilla.org/en-US/, where https://developer.mozilla.org/ redirects (HTTP 302).

Measured once, from 1 vantage point, at https://developer.mozilla.org. The scanner reads the homepage and at most 129 URLs, runs no JavaScript, and calls no API or MCP tool it finds.

Not a ranking prediction, not AI visibility, not a certification.

We sell no consulting. No ads, no sponsored listings, and we never contact the sites that are scanned. Scanning is free today.

Defects 3

Web-standards checks that fail or are partial, and optional files served with an error. Each lists what fixing it is worth.

  • Partial worth 4.9 points Adopted JSON-LD structured data — 1 RDFa item on the homepage, and no top-level node names the page entity: BreadcrumbList is a structural type.

    Observation

    JSON-LD: 0 blocks, 0 parsed · schema.org @context: no · Microdata: 0 items · RDFa: 1 items · top-level types: BreadcrumbList

    Structured data names the entity a page describes. Google reads JSON-LD, Microdata and RDFa alike.

    Sources: Google: intro to structured data (Google Search Central), schema.org (Schema.org), Bing Webmaster Guidelines, §14: structured data (Microsoft Bing)

    Read today by
    Google rich results; any schema.org reader.
    Google Search
    Direct

    Fix

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "name": "MDN Web Docs",
      "url": "https://developer.mozilla.org/"
    }
    </script>

    Note

    Fill name with the name the organization uses, and keep each block valid JSON: one syntax error, such as a trailing comma, hides the whole block.

    Verify with

    HOMEPAGE=https://developer.mozilla.org/en-US/
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' -o /tmp/aws-home.html "$HOMEPAGE"; perl -0777 -ne 'my $j = () = m{<script[^>]*application/ld\+json}gi; my $m = () = m{\bitemtype=["\x27]?https?://schema\.org/}gi; my $r = () = m{\btypeof=}gi; print "JSON-LD blocks: $j, Microdata itemtypes: $m, RDFa typeof: $r\n"' /tmp/aws-home.html; perl -0777 -ne 'while (m{<script[^>]*application/ld\+json[^>]*>(.*?)</script>}gsi) { print "$1\n" }' /tmp/aws-home.html | jq -c '[(.. | objects | select(has("@type")) | {type: .["@type"], name: (.name // .headline // null)})][:10]'

    Read the check page

  • Partial worth 3.3 points Adopted Title and description — Title "MDN Web Docs" (12 characters) and a description of 145 characters. The first H1 "Resources for Developers, by Developers" shares 0 of 2 words with the title, brand names aside. Microsoft's guide to AI search answers (October 2025) asks for an H1 that matches the title or closely reflects it.

    Observation

    title (12 characters): MDN Web Docs · description (145 characters): The MDN Web Docs site provides information about Open Web technologies including HTML, CSS, and APIs for both Web sites and progressive web apps. · first H1: Resources for Developers, by Developers

    The title and the description say what a page is about. Google uses them for the title link and the snippet.

    Sources: Google: title links (Google Search Central), Google: snippets (Google Search Central), Bing Webmaster Guidelines, §13: titles, descriptions and headings (Microsoft Bing), Microsoft: optimizing content for AI search answers (Microsoft Advertising, 2025-10)

    Read today by
    Google, Bing, and link previews.
    Google Search
    Direct

    Note

    Give the first H1 and the title the same subject. Either can change, and brand names do not count.

    Verify with

    HOMEPAGE=https://developer.mozilla.org/en-US/
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | perl -0777 -CS -ne 'if (m{<title[^>]*>(.*?)</title>}si) { my $t=$1; $t=~s/\s+/ /g; $t=~s/^ | $//g; print "title (", length($t), "): $t\n" } else { print "title: none\n" } if (m{<meta\b[^>]*\bname=["\x27]?description["\x27]?[^>]*>}i) { my ($c)=$& =~ /\bcontent=["\x27]([^"\x27]*)/i; $c //= ""; print "description (", length($c), "): $c\n" } else { print "description: none\n" }'

    Read the check page

  • optional file, served with an error 0 points Adopted Breadcrumb markup on an inner page — The inner page /en-US/docs/Web/HTML states a BreadcrumbList of 2 ListItems: 2 without a resolvable item URL ("Web", "HTML").

    Observation

    https://developer.mozilla.org/en-US/docs/Web/HTML · HTTP 200 · text/html · RDFa trail: Web > HTML · ListItem: 2 · item URLs: 0

    BreadcrumbList states where an inner page sits in the site. A homepage has no trail.

    Sources: Google: breadcrumb (Google Search Central), Google blog (Google Search Central, 2025-01)

    Read today by
    Google shows breadcrumbs in desktop results.
    Google Search
    Direct

    Fix

    <script type="application/ld+json">
    {
      "@context": "https://schema.org",
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "MDN Web Docs",
          "item": "https://developer.mozilla.org/en-US/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "<choose: name of this section>",
          "item": "<choose: URL of the /en-US/docs page, if the site has one>"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "<choose: name of this section>",
          "item": "https://developer.mozilla.org/en-US/docs/Web"
        },
        {
          "@type": "ListItem",
          "position": 4,
          "name": "HTML: HyperText Markup Language",
          "item": "https://developer.mozilla.org/en-US/docs/Web/HTML"
        }
      ]
    }
    </script>

    Note

    Replace each <choose: …> with the name or the URL the site uses for that section, and drop a level that has no page. Show the same trail as links on the page.

    Verify with

    PAGE=https://developer.mozilla.org/en-US/docs/Web/HTML
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' -o /tmp/aws-page.html "$PAGE"; perl -0777 -ne 'while (m{<script[^>]*application/ld\+json[^>]*>(.*?)</script>}gsi) { print "$1\n" }' /tmp/aws-page.html | jq -r '.. | objects | select((.["@type"]? | if type == "array" then .[] else . end) == "BreadcrumbList") | .itemListElement[] | [(.position | tostring), (.name // .item.name? // "NO NAME"), ((.item["@id"]? // .item) // "NO URL" | tostring)] | @tsv'; grep -c 'schema.org/BreadcrumbList' /tmp/aws-page.html

    Read the check page

Optional choices 2

Show 2 in Optional choices

Decisions only you can make. None earns points or holds a level.

  • Not used 0 points Adopted Snippet and AI grounding directives — Not used: the homepage has no noarchive, nocache, nosnippet or max-snippet:0 directive, and no data-nosnippet attribute, so Bing applies none of the limits they set on snippets and Copilot answers.

    Observation

    no robots meta tag for robots, bingbot or googlebot, no X-Robots-Tag header · data-nosnippet: 0 elements

    noarchive, nocache, nosnippet and data-nosnippet limit how Bing shows a page and how Copilot uses it. Each is the site owner's choice.

    Sources: Bing Webmaster Guidelines, §10: NOARCHIVE, NOCACHE and NOSNIPPET (Microsoft Bing), Bing: robots meta tags and attributes that Bing supports (Microsoft Bing), Google: robots meta tag specifications (Google Search Central)

    Read today by
    Bing reads all five, and Copilot follows noarchive and nocache. Google reads nosnippet, max-snippet and data-nosnippet.
    Google Search
    Direct

    Note

    Each directive is your choice. noarchive keeps the page out of Copilot answers, nocache lets Copilot use only the URL, the title and the snippet, and nosnippet or data-nosnippet may limit the quality of what Copilot cites.

    Verify with

    HOMEPAGE=https://developer.mozilla.org/en-US/
    curl -sSL -o /dev/null -D - -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | tr -d '\r' | grep -i '^x-robots-tag:'
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$HOMEPAGE" | perl -0777 -ne 'my $h = /^(.*?)<\/head>/si ? $1 : substr($_, 0, 8192); while ($h =~ m{<meta\b[^>]*>}gi) { my $t = $&; next unless $t =~ /\bname=["\x27]?(robots|bingbot|googlebot)["\x27]?[\s>\/]/i; my $n = lc $1; my ($c) = $t =~ /\bcontent=["\x27]([^"\x27]*)/i; print "meta $n: ", ($c // ""), "\n" } my $body = $_; $body =~ s{<!--.*?-->}{}gs; $body =~ s{<(script|style|template|title|textarea|noscript)\b[^>]*>.*?</\1\s*>}{}gsi; my $n = 0; while ($body =~ m{<[a-z][a-z0-9-]*\b((?:[^>"\x27]|"[^"]*"|\x27[^\x27]*\x27)*)>}gi) { (my $t = $1) =~ s{"[^"]*"|\x27[^\x27]*\x27}{}g; $n++ if $t =~ /(?:^|\s)data-nosnippet(?=[\s=\/]|$)/i } print "data-nosnippet: $n\n"'

    Read the check page

  • Not used 0 points Adopted security.txt (RFC 9116) — Not published: /.well-known/security.txt and /security.txt answered HTTP 404.

    Observation

    /.well-known/security.txt: HTTP 404 · text/html · first 20 KB read; /security.txt: HTTP 404 · text/html · first 19 KB read

    security.txt tells a researcher where to report a vulnerability (RFC 9116). It has no effect on search.

    Sources: RFC 9116 (IETF, 2022-04)

    Read today by
    Security researchers and disclosure tools.
    Google Search
    None

    Fix

    Contact: <choose: mailto: or https: address for security reports>
    Expires: 2027-04-18T17:06:15.000Z
    Preferred-Languages: en-US
    Canonical: https://developer.mozilla.org/.well-known/security.txt
    

    Note

    Serve this as text/plain at /.well-known/security.txt. Contact is your own decision, and RFC 9116 recommends an Expires less than a year ahead.

    Verify with

    ORIGIN=https://developer.mozilla.org
    curl -sSL -o /dev/null -w '/.well-known/security.txt HTTP %{http_code} %{content_type}\n' -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/plain, */*;q=0.5' "$ORIGIN/.well-known/security.txt"
    curl -sSL -o /dev/null -w '/security.txt HTTP %{http_code} %{content_type}\n' -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/plain, */*;q=0.5' "$ORIGIN/security.txt"
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/plain, */*;q=0.5' "$ORIGIN/.well-known/security.txt" | grep -Ei '^(contact|expires|canonical|policy|preferred-languages):'

    Read the check page

Agent conventions 5

Show 5 in Agent conventions

They make up 30% of the score. None has an effect on Google Search today. Each row not in use lists what using it is worth.

  • Not used worth 6 points Adopted AI crawler policy in robots.txt — All 18 AI crawler tokens follow the * group (3 rules); none has its own group.

    Observation

    * group: 3 rules, partly disallowed, followed by 18 AI crawler tokens · robots.txt: 1 group, 3 rules

    A crawler follows the robots.txt group that names it, otherwise the * group. A named group states the site's rules for that crawler.

    Sources: RFC 9309, 2.2.1 (IETF), Google common crawlers (Google Search Central), OpenAI bots (OpenAI)

    Read today by
    AI crawlers that document robots.txt tokens.
    Google Search
    None

    Note

    A crawler obeys the one group that names it and skips the * group (RFC 9309, 2.2.1), so a named group repeats every * rule it should keep. This convention counts a named group that allows / for its crawler. Whether to block a crawler is your choice, and a block earns no points.

    Verify with

    ORIGIN=https://developer.mozilla.org
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/plain, */*;q=0.5' "$ORIGIN/robots.txt" | grep -Ein '^[[:space:]]*(user-agent|allow|disallow)[[:space:]]*:'

    Read the check page

  • Not used worth 6 points Draft Content-Signal preferences — No Content-Signal line in robots.txt or the homepage headers. Under the policy, no signal states no preference.

    Observation

    HTTP 200 · text/plain · 119 bytes

    Content-Signal states search, ai-input and ai-train preferences in robots.txt. No crawler documents honouring it.

    Sources: Cloudflare: Content Signals Policy (Cloudflare, 2025-09), IETF AIPREF (IETF)

    Read today by
    Cloudflare's scanner scores it. The IETF AIPREF drafts are the standards track.
    Google Search
    None

    Fix

    Content-Signal: search=<choose: yes or no>, ai-input=<choose: yes or no>, ai-train=<choose: yes or no>
    

    Note

    Add this line to the site's own User-agent: * group in /robots.txt, below its User-agent lines. Each value is the site owner's choice.

    Verify with

    ORIGIN=https://developer.mozilla.org
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/plain, */*;q=0.5' "$ORIGIN/robots.txt" | grep -i -B3 '^content-signal:'
    curl -sSL -o /dev/null -D - -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/html,application/xhtml+xml,application/xml;q=0.9,text/plain;q=0.8,*/*;q=0.7' "$ORIGIN/" | grep -i '^content-signal:'

    Read the check page

  • Not used worth 6 points Adopted Structured errors for JSON requests — Not used: /aws-probe-40adf5a0570b, asked for JSON, answered HTTP 404 with an HTML page, not a JSON error.

    Observation

    HTTP 404 · text/html · first 16 KB read

    An agent that asks for JSON and gets an HTML error page has to read a page meant for people. RFC 9457 defines a JSON error format.

    Sources: RFC 9457: Problem Details for HTTP APIs (IETF, 2023-07), RFC 9110, 12.5.1: Accept (IETF)

    Read today by
    API clients and agents that send Accept: application/json. No search engine reads it.
    Google Search
    None

    Fix

    {
      "type": "about:blank",
      "title": "Not Found",
      "status": 404,
      "detail": "Nothing is published at this address."
    }
    

    Note

    Send this with Content-Type: application/problem+json and the status 404 when a request for a missing path asks for JSON. Browsers can keep the HTML page (RFC 9457).

    Verify with

    ORIGIN=https://developer.mozilla.org
    MISSING="/aws-probe-$(head -c 6 /dev/urandom | od -An -tx1 | tr -d ' \n')"
    curl -sS -D - -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: application/json, application/problem+json;q=0.9, */*;q=0.1' "$ORIGIN$MISSING" | head -20

    Read the check page

  • Not used worth 5 points Experimental Markdown content negotiation — The homepage answered `Accept: text/markdown, text/html;q=0.5` with HTML, which is a valid response.

    Observation

    HTTP 200 · text/html · Vary: Accept-Encoding · markdown body: no

    Some coding agents ask for text/markdown. Google Search does not use markdown.

    Sources: RFC 7763 (IETF), Cloudflare: Markdown for Agents (Cloudflare), Google: AI optimization guide (Google Search Central)

    Read today by
    Claude Code, OpenCode and Cursor send Accept: text/markdown by default (Cloudflare, 2026-04).
    Google Search
    None

    Fix

    Answer a request whose Accept header prefers text/markdown with a markdown version of the same page, at the same URL.
    - On a CDN that converts HTML to markdown, turn that conversion on for the site.
    - On a CMS or a static build, publish one .md file per page, and serve it when Accept prefers text/markdown.
    Send Content-Type: text/markdown; charset=utf-8 with the markdown.
    Send Vary: Accept with both the markdown and the HTML, so a shared cache keeps them apart.

    Note

    Send Vary: Accept with the HTML response too, so a shared cache never serves one representation in place of the other.

    Verify with

    HOMEPAGE=https://developer.mozilla.org/en-US/
    curl -sSL -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/markdown, text/html;q=0.5' -D - -o /tmp/aws-md.body "$HOMEPAGE" | grep -iE '^(HTTP/|content-type|vary)'; head -c 300 /tmp/aws-md.body; echo

    Read the check page

  • Not used worth 4.3 points Draft /llms.txt published and well-structured — Not served: /llms.txt answered HTTP 404.

    Observation

    HTTP 404 · text/html · first 16 KB read

    A 2024 proposal for a markdown index of a site. Google Search does not use it.

    Sources: llmstxt.org (llmstxt.org), Google: AI optimization guide (Google Search Central), Lighthouse llms.txt (Chrome for Developers)

    Read today by
    Some documentation tools and coding agents. Lighthouse audits it.
    Google Search
    None

    Fix

    # MDN Web Docs
    
    > The MDN Web Docs site provides information about Open Web technologies including HTML, CSS, and APIs for both Web sites and progressive web apps.
    
    ## Pages
    
    - [MDN Web Docs](https://developer.mozilla.org/)
    - [<choose: name of the page at /docs>](https://developer.mozilla.org/docs)
    

    Note

    Serve the file raw at /llms.txt as text/plain or text/markdown, with an H1 on its first line. A catch-all route that answers this path with the homepage serves no file.

    Verify with

    ORIGIN=https://developer.mozilla.org
    curl -sSL -D - -A 'AgenticWebScore/0.3 (+https://agenticwebscore.com/bot)' -H 'Accept-Language: en' -H 'Accept: text/plain, text/markdown;q=0.9, */*;q=0.5' "$ORIGIN/llms.txt" | head -40

    Read the check page

Out of scope for this site 38

Show 38 in Out of scope for this site

The scan did not ask this site for these checks. Each says why. If one should apply, the error is ours, not yours.

Sites with an API or agent surface

The scan found no API or agent surface, so API and agent checks are not asked of this site.

  • Out of scope 0 points Draft A2A agent card — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An A2A agent card describes an agent the site runs. An A2A server publishes it.

    Sources: A2A specification (A2A Project)

    Read today by
    A2A clients.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft Cryptographically signed agent card — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An A2A card may be signed with JWS. Signing is optional in the specification.

    Sources: A2A specification (A2A Project), RFC 7515 (IETF)

    Read today by
    A2A clients that verify cards.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft Agent Skills declaration — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An agent skills index lists skill packages for agent runtimes. It is a draft on GitHub.

    Sources: Agent Skills Discovery RFC (Cloudflare)

    Read today by
    Agent runtimes that read the draft.
    Google Search
    None

    Read the check page

  • Out of scope Adopted API catalog — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An API catalog lists a publisher's APIs in one document at a fixed address (RFC 9727).

    Sources: RFC 9727 (IETF, 2025-06)

    Read today by
    API clients that follow RFC 9727.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Experimental ARD resource discovery manifest — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An ARD manifest lists a site's agent resources. Lighthouse does not count a missing one against a site.

    Sources: Lighthouse agentic browsing (Chrome for Developers)

    Read today by
    Lighthouse (ard-schema audit).
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft /auth.md agent authentication guide — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    auth.md is one vendor's convention (WorkOS) for telling an agent how to authenticate.

    Sources: WorkOS auth.md (WorkOS)

    Read today by
    Agents built on WorkOS.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Experimental DNS-AID discovery record — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    DNS-AID publishes agents in DNS. It is an individual Internet-Draft with no IETF standing.

    Sources: draft-mozleywilliams-dnsop-dnsaid (IETF)

    Read today by
    Cloudflare's scanner.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Documentation reachable — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    Documentation linked as service-doc (RFC 8631), or from the homepage, is how a client learns the API.

    Sources: RFC 8631 (IETF)

    Read today by
    Developers and agents integrating the API.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft MCP server card — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An MCP server card describes a remote MCP server. It is an optional extension (SEP-2127), not core MCP.

    Sources: SEP-2127 (Model Context Protocol, 2026-10), discovery.md (Model Context Protocol)

    Read today by
    MCP clients that implement SEP-2127; Cloudflare's scanner.
    Google Search
    None

    Read the check page

  • Out of scope Adopted MCP server answers and lists its tools — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An agent given the address of an MCP server can call its tools. The scan opens one session to see that the server answers and what it offers.

    Sources: MCP 2025-11-25: lifecycle (Model Context Protocol, 2025-11), MCP 2025-11-25: transports (Model Context Protocol, 2025-11), MCP 2025-11-25: tools (Model Context Protocol, 2025-11), Agentic AI Foundation: MCP joins the Linux Foundation (Linux Foundation, 2025-12)

    Read today by
    MCP clients: agent apps, coding agents, and chat products that connect to MCP servers.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft MPP discovery in OpenAPI (x-payment-info) — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An operation with x-payment-info tells an agent that the call is paid, and states the intent, the payment method, and the amount. MPP is a draft, and charging agents is a business decision.

    Sources: MPP (mpp.dev), MPP: multi-method discovery (mpp.dev), draft-ryan-httpauth-payment (IETF (individual draft)), isitagentready.com: MPP skill (isitagentready.com)

    Read today by
    Agents that pay with MPP; isitagentready.com.
    Google Search
    None

    Read the check page

  • Out of scope Adopted OAuth discovery documents — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    OAuth metadata tells a client where and how to authorise against the API.

    Sources: RFC 8414 (IETF), RFC 9728 (IETF)

    Read today by
    OAuth clients; MCP clients use RFC 9728.
    Google Search
    None

    Read the check page

  • Out of scope Adopted OpenAPI definition — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    An OpenAPI document describes an HTTP API so a client can call it without guessing.

    Sources: OpenAPI 3.1 (OpenAPI Initiative), RFC 8631 (IETF)

    Read today by
    API clients and code generators.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Experimental Rate limits and quotas documented — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    Declared limits let a client pace its calls. RateLimit headers are an IETF draft.

    Sources: draft-ietf-httpapi-ratelimit-headers (IETF)

    Read today by
    API clients.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Experimental Sandbox or test environment documented — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    A documented sandbox lets a client test calls without touching production data.

    Sources: OpenAPI 3.1 (servers) (OpenAPI Initiative)

    Read today by
    API integrators.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Service status and changelog feed — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    A status page and a changelog feed say whether the service is up and what changed.

    Sources: RFC 9727 (status relation) (IETF), RFC 4287 (IETF)

    Read today by
    Integrators and monitoring tools.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft Web Bot Auth key directory — Not scored: the scan found no API or agent surface, so API and agent checks are not asked of this site.

    The operator of a signing agent publishes its keys here. A site that only serves content needs none.

    Sources: draft-ietf-webbotauth-httpsig-protocol (IETF, 2026-09), Cloudflare: Web Bot Auth (Cloudflare)

    Read today by
    Sites and CDNs that verify signed agents.
    Google Search
    None

    Read the check page

Sites with a commercial signal

The homepage shows no commercial signal, so commerce checks are not asked of this site.

  • Out of scope 0 points Draft ACP discovery (/.well-known/acp.json) — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    An ACP discovery document at /.well-known/acp.json tells an agent where a business's checkout API is and which services it offers. The RFC behind it is a proposal.

    Sources: ACP discovery RFC (status: Proposal) (Agentic Commerce Protocol), isitagentready.com: ACP skill (isitagentready.com)

    Read today by
    Agents that implement ACP checkout; isitagentready.com.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft Agent purchase policy — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    Whether agents may buy, and with what approval, is a policy the site states.

    Sources: ACP (Agentic Commerce Protocol)

    Read today by
    Agent checkouts.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Inventory and price freshness — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    availability says whether an item is in stock. A past priceValidUntil can hide a product snippet.

    Sources: Google: product snippet (Google Search Central)

    Read today by
    Google product snippets.
    Google Search
    Direct

    Read the check page

  • Out of scope 0 points Draft Agent payment protocol (UCP profile or x402) — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    Agent payment protocols are early. Accepting one is a business decision. This check reads UCP and x402. ACP and MPP have checks of their own.

    Sources: UCP (Universal Commerce Protocol), x402 (x402)

    Read today by
    Agent checkouts that implement UCP or x402.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Product/catalog schema — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    Product and Offer markup on product pages feeds merchant listings.

    Sources: Google: merchant listing (Google Search Central), Google: product (Google Search Central)

    Read today by
    Google merchant listings and shopping agents.
    Google Search
    Direct

    Read the check page

  • Out of scope Adopted Return policy machine-readable — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    A MerchantReturnPolicy states return terms in markup, also under the Organization.

    Sources: Google: return policy (Google Search Central)

    Read today by
    Google merchant listings.
    Google Search
    Direct

    Read the check page

  • Out of scope Adopted Seller identity declared — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    On a marketplace, the seller named on an offer is who the buyer contracts with.

    Sources: Google: merchant listing (Google Search Central)

    Read today by
    Google merchant listings.
    Google Search
    Direct

    Read the check page

  • Out of scope Adopted Shipping cost and delivery declared — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    shippingDetails lets a client compute the delivered price.

    Sources: Google: merchant listing (Google Search Central)

    Read today by
    Google merchant listings.
    Google Search
    Direct

    Read the check page

  • Out of scope 0 points Draft UCP manifest (/.well-known/ucp) — Not scored: the homepage shows no commercial signal, so commerce checks are not asked of this site.

    A UCP profile at /.well-known/ucp declares commerce capabilities. UCP is a draft.

    Sources: UCP (Universal Commerce Protocol), Shopify profiles (Shopify)

    Read today by
    UCP agents; Shopify stores serve it.
    Google Search
    None

    Read the check page

Every site

  • Out of scope 0 points Experimental AI usage policy page — Not scored: robots.txt and Content-Signal state no AI restriction, so there is none for a policy page to explain.

    A page that explains in prose the AI restrictions the site states. No standard defines it.

    Sources: RFC 9309 (IETF)

    Read today by
    People reading the site's terms.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft Machine-readable booking action — Not scored: this check applies to services sites; this site was measured as API platform.

    A ReserveAction declares a booking target in markup. No search engine documents a feature that reads it.

    Sources: schema.org/ReserveAction (Schema.org)

    Read today by
    None documented.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Structured contact information — Not scored: the homepage markup declares no Organization-type node.

    A ContactPoint in the Organization markup makes the contact route machine-readable.

    Sources: Google: Organization structured data (Google Search Central)

    Read today by
    Google lists contactPoint as a recommended Organization property.
    Google Search
    Indirect

    Read the check page

  • Out of scope 0 points Adopted Documents in machine-readable formats — Not scored: this check applies to institution sites; this site was measured as API platform.

    Tagged PDF or an HTML version can be read by screen readers and by machines.

    Sources: GOV.UK: HTML not PDF (Government Digital Service), ISO 14289 (PDF/UA) (ISO)

    Read today by
    Screen readers; GOV.UK publishes HTML first.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Adopted FAQ markup for visible questions — Not scored: no heading on the homepage names a FAQ section, and the homepage carries no FAQPage markup.

    Observation

    visible questions under a FAQ heading: 0

    FAQPage marks up questions that are visible on the page. Google stopped showing FAQ rich results on 7 May 2026.

    Sources: Google Search updates (Google Search Central), Google: structured data policies (Google Search Central)

    Read today by
    Bing names FAQ markup as an example of labelled content.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Draft Reuse and licensing terms declared — Not scored: this check applies to publisher or institution sites; this site was measured as API platform.

    TDMRep reserves text and data mining rights in a machine-readable form, as EU DSM Article 4(3) allows.

    Sources: TDMRep CG report (W3C), Directive (EU) 2019/790 (European Union)

    Read today by
    Text and data mining tools that implement TDMRep.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Discovery via Link response headers — Not scored: there is nothing for a Link header to name. No llms.txt or markdown variant is in use, and the site serves no OpenAPI document or API catalog.

    A Link header (RFC 8288) points a client at a resource before it parses the HTML.

    Sources: RFC 8288 (IETF), IANA link relations (IANA)

    Read today by
    Clients that follow RFC 8288 and RFC 9727 links.
    Google Search
    None

    Read the check page

  • Out of scope Draft /llms-full.txt expanded context — Not scored: /llms.txt is not served (HTTP 404), so /llms-full.txt is not asked for.

    A convention that puts a site's text in one file. The llms.txt proposal does not define it.

    Sources: llmstxt.org (llmstxt.org), Mintlify (Mintlify)

    Read today by
    Some documentation tools.
    Google Search
    None

    Read the check page

  • Out of scope Adopted Structured pricing information — Not scored: no Offer or PriceSpecification in the homepage markup states a price, and no pricing page states a complete one.

    A price in markup is read without parsing prose. An Offer with a price and no currency is ambiguous.

    Sources: schema.org/Offer (Schema.org), Google: product snippet (Google Search Central)

    Read today by
    Clients that read schema.org Offer. Google reads an Offer only inside a Product, which product-schema measures.
    Google Search
    None

    Read the check page

  • Out of scope 0 points Adopted Content provenance declared — Not scored: this check applies to publisher or institution sites; this site was measured as API platform.

    Article markup with an author and dates lets a client attribute and date a source.

    Sources: Google: Article structured data (Google Search Central)

    Read today by
    Google article features.
    Google Search
    Direct

    Read the check page

  • Out of scope Adopted Service/product scope machine-readable — Not scored: the homepage markup declares no Service-type node.

    Service markup states what is offered, by whom and where. An incomplete node leaves a client to guess.

    Sources: schema.org/Service (Schema.org)

    Read today by
    Clients that read schema.org Service. Google has no Service rich result.
    Google Search
    None

    Read the check page

  • Out of scope Experimental WebMCP browser tool declaration — Not scored: the homepage has no form and calls no registerTool, so it offers no task to declare.

    WebMCP lets a page register tools for an in-browser agent. It is a W3C Community Group draft.

    Sources: WebMCP draft (W3C Web Machine Learning Community Group), Chrome: WebMCP (Chrome for Developers)

    Read today by
    Chrome, behind an origin trial. Lighthouse audits it.
    Google Search
    None

    Read the check page

Passed 12

Show 12 in Passed

Scored checks that pass, the heaviest first.

  • Passed Adopted Content that needs no JavaScript — 6265 characters of text are in the HTML before any script runs.

    Observation

    static text: 6265 characters · inside <noscript>: 0 characters · markup: 121595 characters

    Several AI crawlers do not run JavaScript. Text that appears only after scripts run is invisible to them.

    Sources: Vercel: the rise of the AI crawler (Vercel), Google: JavaScript SEO basics (Google Search Central), Bing Webmaster Guidelines, §8: rendering (Microsoft Bing)

    Read today by
    GPTBot and ClaudeBot fetch HTML without rendering; Googlebot renders.
    Google Search
    Indirect

    Read the check page

  • Passed Adopted Readable homepage — Measured at https://developer.mozilla.org/en-US/, where https://developer.mozilla.org/ redirects (HTTP 302). HTTP 200 text/html, 119 KB, 899 words of visible text. A temporary redirect is a weaker canonical signal than 301 or 308.

    Observation

    HTTP 200 · text/html · 119 KB · final https://developer.mozilla.org/en-US/

    The homepage is the first URL every agent requests. An error or an empty page gives it nothing to read.

    Sources: RFC 9110 (IETF), Google: 301 redirects (Google Search Central), Bing Webmaster Guidelines, §7: 301 and 302 redirects (Microsoft Bing)

    Read today by
    Every crawler and agent.
    Google Search
    Direct

    Read the check page

  • Passed Adopted Semantic heading structure — 1 H1, 4 H2s, and 8 H3s in an outline of 13 headings, with no skipped level.

    Observation

    outline: H1 H2 H3 H3 H3 H3 H2 H3 H3 H3 H3 H2 H2

    Headings outline the page for screen readers and for any client that splits text by section.

    Sources: W3C WAI headings tutorial (W3C), Google SEO starter guide (Google Search Central), Bing Webmaster Guidelines, §13: titles, descriptions and headings (Microsoft Bing)

    Read today by
    Screen readers; clients that chunk HTML by heading.
    Google Search
    Indirect

    Read the check page

  • Passed Adopted Homepage indexable: no noindex directive — No noindex: the homepage has no robots meta tag for robots, bingbot or googlebot, and no X-Robots-Tag header.

    Observation

    no robots meta tag for robots, bingbot or googlebot, no X-Robots-Tag header

    A noindex in a meta tag or in a response header keeps the page out of search results. Bing keeps it out of Copilot too.

    Sources: Bing Webmaster Guidelines, §10: NOINDEX and the other robots directives (Microsoft Bing), Bing: robots meta tags and attributes that Bing supports (Microsoft Bing), Google: block indexing with noindex (Google Search Central), Google: robots meta tag specifications (Google Search Central)

    Read today by
    Google and Bing. Bing applies the same directives to Copilot answers.
    Google Search
    Direct

    Read the check page

  • Passed Adopted robots.txt crawl policy — /robots.txt has 1 group and 3 rules across all groups, and 1 Sitemap line.

    Observation

    HTTP 200 · text/plain · 119 bytes · User-agent: * Sitemap: https://developer.mozilla.org/sitemap.xml Disallow: /api/ Disallow: /*/files/ Disallow: /media

    Crawlers read robots.txt before they fetch a page (RFC 9309). Its Sitemap line tells them where the URL list is.

    Sources: RFC 9309 (IETF, 2022-09), Google robots.txt (Google Search Central)

    Read today by
    Google, Bing, and the AI crawlers that document robots.txt support.
    Google Search
    Direct

    Read the check page

  • Passed Adopted XML sitemap — Sitemap index https://developer.mozilla.org/sitemap.xml parses and lists 10 child sitemaps. This scan does not read the child sitemaps.

    Observation

    HTTP 200 · application/xml · 1.3 KB · root <sitemapindex>

    A sitemap lists the URLs a site wants crawled. Google says a small, well-linked site may not need one.

    Sources: Google: build a sitemap (Google Search Central), sitemaps.org (sitemaps.org), Bing Webmaster Guidelines, §3: lastmod (Microsoft Bing)

    Read today by
    Google and Bing.
    Google Search
    Direct

    Read the check page

  • Passed Adopted Canonical URL — Measured at https://developer.mozilla.org/en-US/, where https://developer.mozilla.org/ redirects (HTTP 302). Canonical https://developer.mozilla.org/en-US/ matches the page reached.

    Observation

    <link rel="canonical" href="https://developer.mozilla.org/en-US/">

    A canonical link names the one URL a page is known by. Google treats it and redirects as canonical signals.

    Sources: Google: consolidate duplicate URLs (Google Search Central), RFC 6596 (IETF), Bing Webmaster Guidelines, §6: duplicate URLs and canonicals (Microsoft Bing)

    Read today by
    Google and Bing.
    Google Search
    Direct

    Read the check page

  • Passed Adopted HTTP caching of the homepage — The homepage sends Cache-Control "public, max-age=3600" and ETag and Last-Modified, and a request with If-None-Match and If-Modified-Since was answered HTTP 304 Not Modified.

    Observation

    Cache-Control: public, max-age=3600 · ETag: W/"b76b498cae7043ee81e25fd04fe755e6" · Last-Modified: Tue, 20 Oct 2026 01:09:12 GMT · conditional GET with If-None-Match and If-Modified-Since: HTTP 304

    Cache-Control says how long the homepage may be reused. A validator lets a crawler ask whether it changed, and a 304 answer skips the body.

    Sources: RFC 9111: HTTP Caching (IETF, 2022-06), RFC 9110, 13: conditional requests (IETF), Google: HTTP caching for crawlers (Google Search Central, 2024-12), Bing Webmaster Guidelines, §3: ETag and lastmod (Microsoft Bing)

    Read today by
    Googlebot sends If-None-Match and If-Modified-Since. Every HTTP cache reads Cache-Control.
    Google Search
    Direct

    Read the check page

  • Passed Adopted Language declaration and multilingual access — html lang="en-US" is a well-formed BCP 47 tag, with no hreflang alternates.

    Observation

    html lang="en-US" · alternates: none · content-language: (none)

    The lang attribute names the language of the text. WCAG 3.1.1 requires it at level A. Google reads hreflang, not lang.

    Sources: WCAG 2.2, 3.1.1 (W3C), Google: managing multi-regional sites (Google Search Central), Google: localized versions (Google Search Central)

    Read today by
    Screen readers and translation tools. Google ignores the lang attribute and reads hreflang.
    Google Search
    Indirect

    Read the check page

  • Passed Adopted A real 404 for a missing page — /aws-probe-40adf5a0570b, a path that does not exist, answered HTTP 404.

    Observation

    HTTP 404 · text/html · first 16 KB read

    A URL that does not exist answers 404 or 410 (RFC 9110). A 200 there makes every mistyped link look like a page.

    Sources: RFC 9110, 15.5.5: 404 Not Found (IETF), Google: HTTP status codes and soft 404s (Google Search Central), Bing Webmaster Guidelines, §9: 404 for missing pages (Microsoft Bing)

    Read today by
    Google reports a missing page that answers 200 as a soft 404. Every HTTP client reads the status first.
    Google Search
    Direct

    Read the check page

  • Passed Adopted Per-page content separation (no SPA fallback) — The homepage and /en-US/docs/Web/HTML have different titles ("MDN Web Docs" and "HTML: HyperText Markup Language | MDN") and different main text (14% word overlap).

    Observation

    compared / with /en-US/docs/Web/HTML · titles "MDN Web Docs" / "HTML: HyperText Markup Language | MDN" · skeleton 82% · main-text word overlap 14% · main text 6995 characters

    A route that answers every URL with the same page makes every URL look alike to a crawler.

    Sources: Google: HTTP errors and soft 404s (Google Search Central)

    Read today by
    Google flags such pages as soft 404s.
    Google Search
    Direct

    Read the check page

  • Passed Adopted Responsive markup — viewport content "width=device-width, initial-scale=1.0" sets width=device-width and leaves zoom on.

    Observation

    viewport meta: width=device-width, initial-scale=1.0

    Google indexes the smartphone rendering of a page. A viewport that blocks zoom fails WCAG 1.4.4.

    Sources: Google: mobile-first indexing (Google Search Central), WCAG 2.2, 1.4.4 (W3C)

    Read today by
    Browsers; Google's smartphone crawler renders the page with it. No Google feature reads the tag itself.
    Google Search
    Indirect

    Read the check page

Hand this report to your coding agent

The prompt lists 3 checks to fix. Each has the value the scan measured and a command that repeats the measurement. It adds the change to make where the scan could build one. After them it lists 5 agent conventions, at lower priority. The prompt is served at https://agenticwebscore.com/aws/developer.mozilla.org/prompt.md. The command below prints it, so you can paste the output into your agent.

curl -s https://agenticwebscore.com/aws/developer.mozilla.org/prompt.md

This scan cannot see which AI answers cite the site. Bing Webmaster Tools reports citations in Copilot and in Bing's AI summaries under AI Performance. Google Search Console includes AI Overviews and AI Mode in its Performance report totals, without a separate view (Google's guide to AI features). Both need a verified owner of the site.

Badge

Show this score on your own site. Press Get the badge, paste its snippet into your homepage, and press Check my badge. The directory then lists your site as a verified listing.

Agent readiness score for developer.mozilla.org

Read how listing works

Ship a fix, then re-scan

Measured 8 days ago. Nothing re-scans a site on its own. A scan runs once, when somebody asks for it — and that somebody need not be you. Anyone can request a scan of any public host, so this page may be the first you hear of it. After you ship a fix, press Re-scan now. A check that now passes adds its points to the score.

Why a re-scan can differ

The current rubric evaluates 3 of its 60 checks against a clock: security-txt, status-page, and inventory-freshness. They can change with no change to the site. A response slower than 12 s is reported as not measured, so the same bytes served slowly can move the score and the fingerprint.

Measured as: API / developer platform

Can an agent discover, authorise against and call the API without reading a tutorial? Checks that only apply to other site profiles were not scored, so you are not asked to do work that does not apply to you.

  • · API / developer platform (score 4), matched: A documentation path responds; API reference copy.

Signal scores

  • API platform 4
  • SaaS 2
  • Institution 1

Modules

  • Every site: always in scope.
  • Sites with an API or agent surface : out of scope. The scan found no API or agent surface.
  • Sites with a commercial signal : out of scope. The homepage shows no commercial signal.

Scan record

Target
https://developer.mozilla.org
Measured at
https://developer.mozilla.org/en-US/
Redirect
https://developer.mozilla.org/ to https://developer.mozilla.org/en-US/, HTTP 302
Scanned
Requests
29
Duration
3.0s
Confidence
100% · high
Rubric
rubric v0.9

Fingerprint

1f91c6124a6d… verify this record

full hash

1f91c6124a6d8ed47c606a19ee06f9b048a90700b079980ad4350e44b5ceea30

Page as an agent receives it

Words
899
Est. tokens
1214
Markup
118.8 KB
Language
en-US

“MDN Web Docs”

By dimension

Each score is the share of the in-scope web-standards points a dimension earned. A dash means the dimension has no web-standards check in scope. The agent conventions are scored apart, as their own part.

  • Discoverability

    100
    Pass
    6
    Partial
    0
    Fails
    0
    Not counted
    0

    Unscored: 0 in use, 0 not used

  • Content

    77.3
    Pass
    5
    Partial
    2
    Fails
    0
    Not counted
    3

    Unscored: 0 in use, 0 not used, 1 with an error

  • Crawler access

    100
    Pass
    1
    Partial
    0
    Fails
    0
    Not counted
    0

    Unscored: 0 in use, 2 not used

  • API and agent

    —
    Pass
    0
    Partial
    0
    Fails
    0
    Not counted
    6

    Unscored: 0 in use, 0 not used

  • Commerce

    —
    Pass
    0
    Partial
    0
    Fails
    0
    Not counted
    5

    Unscored: 0 in use, 0 not used

Request transcript 29 requests

Every fetch this scan record logged, in order. A fetch that followed redirects shows how many redirect requests it made.

25 fetches, 4 redirect requests.

  1. /

    200 +1 redirect 118.8 KB 221ms

  2. /robots.txt

    200 119 B 56ms

  3. /sitemap.xml

    200 1.3 KB 80ms

  4. /llms.txt

    404 19.0 KB 592ms

  5. /.well-known/security.txt

    404 20.0 KB 486ms

  6. /security.txt

    404 19.2 KB 493ms

  7. /about

    404 20.0 KB 463ms

  8. /contact

    404 19.2 KB 473ms

  9. /pricing

    404 19.0 KB 410ms

  10. /docs

    200 +2 redirects 146.3 KB 267ms

  11. /developers

    404 20.0 KB 448ms

  12. /.well-known/api-catalog

    404 19.2 KB 401ms

  13. /openapi.json

    404 20.0 KB 417ms

  14. /.well-known/openapi.json

    404 20.0 KB 467ms

  15. /.well-known/mcp/server-card.json

    404 20.0 KB 437ms

  16. /.well-known/ai-catalog.json

    404 19.0 KB 708ms

  17. /.well-known/agent-card.json

    404 19.0 KB 489ms

  18. /.well-known/oauth-protected-resource

    404 19.0 KB 461ms

  19. /.well-known/oauth-authorization-server

    404 19.0 KB 502ms

  20. /.well-known/openid-configuration

    404 19.2 KB 527ms

  21. /en-US/docs/Web/HTML

    200 182.1 KB 23ms

  22. /

    200 +1 redirect 118.8 KB 128ms

  23. /

    304 0 B 26ms

  24. /aws-probe-40adf5a0570b

    404 20.0 KB 890ms

  25. /aws-probe-40adf5a0570b

    404 20.0 KB 486ms