Generative Metrics logo
Checking…Create account

Sample audits — real scans, redacted.

Two completed scans: usa.gov FAIL and example.com PASS. Observed values unchanged; account identity and internal record IDs removed.

Real scans: usa.gov run 2026-09-19 under protocol set gm-ai-consumer-compat/1.3.0, and example.com run 2026-08-30 under protocol set gm-ai-consumer-compat/1.1.0. Redacted for publication: account identity and internal record IDs. Observed values unchanged. Sites change — rescan to verify.

What the machine-readable response contains

usa.gov returned FAIL: the raw HTML response exposes 36 words of main content, a browser renders 412.

Both numbers are recorded by the extraction.main-content protocol in the sealed bundle. The raw HTTP response is what a client that does not execute JavaScript receives; the rendered DOM is what a browser produces from the same page.

Raw HTTP main content

36words

332 bytes · 9931c1230d3a81ef89ee8282ff3ff86a128e8300fa54a5bae9e2cae5037f5ea8

Browser-rendered main content

412words

5531 bytes · 6596b69d312fd4ca78473963db97062036ae56c76e99c7c4d59555235565b656

Raw-to-rendered word ratio

0.0874

376 word deficit

BLOCKERRAW_MAIN_CONTENT_DEFICIT

Raw HTML omits substantial rendered main content

The raw representation exposed 36 main-content words versus 412 after browser rendering. Protocol 1.0.0 flags ratios below 0.5 when rendered content has at least 100 words.

The evidence identity is the sealed bundle digest f5df873bfc6c53b2d8d756b08987164e6246444b33468f23fe12198ea16786f7. Check the hash rather than trust the badge.

Audit 1 of 2 — the FAIL

https://usa.gov/ · 39 protocol executions · protocol set gm-ai-consumer-compat/1.3.0

What AI readsVerdictFindings & fixesProtocolsEvidenceScope

Audit profile

Public AI discovery compatibility

Scan timestamp

2026-09-19T15:25:47.590Z

Profile + protocol set

public-ai-discovery/1.0.0

gm-ai-consumer-compat/1.3.0

Sealed bundle digest f5df87…786f7

Audit verdict

FAIL

Execution state: COMPLETE

FAIL means at least one production finding recorded an open blocker. INCOMPLETE means the required evidence was not fully obtained, so compatibility was not established.

Blockers

1

Warnings

0

Information

2

Verified remediations

0

Findings and fixes

Findings below are tied to named protocol observations. Experimental observations cannot determine the verdict.

BLOCKERRAW_MAIN_CONTENT_DEFICIT

Raw HTML omits substantial rendered main content

The raw representation exposed 36 main-content words versus 412 after browser rendering. Protocol 1.0.0 flags ratios below 0.5 when rendered content has at least 100 words.

Expose primary content in the initial HTML response

Serve the meaningful page content in the raw response instead of requiring client-side JavaScript to construct it.

  1. Server-render or statically generate the primary content.
  2. Keep client-side JavaScript for progressive enhancement rather than initial content availability.

Verification protocols: acquisition.http, representation.raw-rendered, extraction.main-content

  • Main-content extraction uses a deterministic Readability implementation and does not prove extraction by a downstream AI system.
  • Readability scores are intentionally excluded from this protocol because language support is not universal.
INFOSTRUCTURED_DATA_ORGANIZATION_IDENTITY_INCOMPLETE

The raw Organization structured data is missing identity fields

An Organization node was observed in the raw response, and the bounded identity check did not observe: name. This is an informational completeness observation, not a defect by itself.

  • Completeness checks cover raw-versus-rendered schema type presence and three bounded Organization identity fields only.
  • Organization identity fields are recorded as booleans; property values are not stored.
  • The absence of an Organization node is not automatically a defect.
INFOLLMS_TXT_NOT_FOUND

The site does not publish a /llms.txt file

The observed site does not publish a /llms.txt file. This is an informational optimization opportunity and does not indicate that AI systems cannot access, understand, or cite the site.

Publish a /llms.txt file

Consider publishing a /llms.txt file describing the site for AI agents. Absence does not prove an access, understanding, or citation problem; this is an advisory optimization.

  1. Create a /llms.txt file at the site origin with a valid H1-style title heading.
  2. Ensure the body is at least the required minimum size beneath the title.
  3. Describe what information you intend to share with AI agents without exposing unpublished content.

Verification protocols: acquisition.llms-txt

  • The target does not publish a /llms.txt file.

Your URL will produce a different bundle. Run the same audit surface free — 5 scans/month, no card. New scans run the current protocol set gm-ai-consumer-compat/1.6.0.

Run this audit on your siteRead the proof contract

Protocol execution

38 of 39 protocol executions on this run succeeded; 1 returned NOT_APPLICABLE. Required protocols determine whether this audit is complete. Informational protocols add context but do not create a pass requirement.

  • acquisition.http1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • acquisition.robots1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • acquisition.llms-txt1.0.0

    SUCCEEDED

    gm:llms-txt-probe

    Informational

  • acquisition.sitemap1.0.0

    SUCCEEDED

    gm:sitemap-probe

    Informational

  • representation.raw-rendered1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • policy.robots1.0.0

    SUCCEEDED

    openai:oai-searchbot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    anthropic:claude-searchbot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    google:googlebot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    perplexity:perplexitybot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    openai:gptbot

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    anthropic:claudebot

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    google:google-extended

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    openai:chatgpt-user

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    anthropic:claude-user

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    perplexity:perplexity-user

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    openai:oai-searchbot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    anthropic:claude-searchbot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    google:googlebot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    perplexity:perplexitybot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    openai:gptbot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    anthropic:claudebot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    google:google-extended

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    openai:chatgpt-user

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    anthropic:claude-user

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    perplexity:perplexity-user

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    openai:oai-searchbot

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    anthropic:claude-searchbot

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    google:googlebot

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    perplexity:perplexitybot

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    openai:gptbot

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    anthropic:claudebot

    Informational

  • access.actor-probe1.0.0

    NOT_APPLICABLE

    google:google-extended

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    openai:chatgpt-user

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    anthropic:claude-user

    Informational

  • access.actor-probe1.0.0

    SUCCEEDED

    perplexity:perplexity-user

    Informational

  • extraction.main-content1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • structured-data.visible-consistency1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • structured-data.completeness1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Informational

  • freshness.dates1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

Evidence and integrity

The digest below is the original sealed digest of the unredacted bundle. This page publishes a redacted projection, not the sealed artifact; the projection does not re-verify against that digest.

Schema version

gm-evidence-bundle/1.0.0

Protocol set version

gm-ai-consumer-compat/1.3.0

This bundle was sealed under gm-ai-consumer-compat/1.3.0. The current protocol set is gm-ai-consumer-compat/1.6.0; the two are not interchangeable.

original sealed digest of the unredacted bundle

f5df873bfc6c53b2d8d756b08987164e6246444b33468f23fe12198ea16786f7

Captured artifacts

  • Artifact 1

    RAW_HTTP_RESPONSE · HTTP 200 · 48215 bytes

    https://usa.gov/

    5198d6fe1e9085983fa3b19336a08d75f4daed521293e14573bcf4085a6b319d

  • Artifact 2

    ROBOTS_TXT · HTTP 200 · 1558 bytes

    https://usa.gov/robots.txt

    57210da4611cc41b25fb10231cdadd60520cb5ef20ad92309cdd0df6fd12377a

  • Artifact 3

    LLMS_TXT · HTTP 404 · 35405 bytes

    https://usa.gov/llms.txt

    e4815ec1ecfa93a5294c1a0848c8f30d37051c1213446a771353019c340a31e3

  • Artifact 4

    SITEMAP_XML · HTTP 200 · 124717 bytes

    https://usa.gov/sitemap.xml

    9726c141642fd34913e10101a3cad0bcd7778be66ed043b430aaf4c1793a41e0

  • Artifact 5

    RENDERED_DOM · HTTP — · 54368 bytes

    https://usa.gov/

    96fd3cfc91927b6e2b7501a9d14de74cb3a20eb252e954c478421aa1bdc9a8fe

  • Artifact 6

    NO_JAVASCRIPT_DOM · HTTP — · 48273 bytes

    https://usa.gov/

    b22ac6a05b6a078062b4be0f1c4ff344a9b1f46659b8c670ef853a912ae27986

These are the six artifacts the protocols read: the raw HTTP response, robots.txt, llms.txt, sitemap.xml, the browser-rendered DOM, and the no-JavaScript DOM. Browser-derived artifacts carry no HTTP status of their own. Retrieval recorded as observed.

Verification

Baseline scan — no remediation verification on this run. A later scan is what would compare the remediated protocol against this baseline.

Scope and limitations

This audit reports what the named acquisition, policy, and extraction protocols observed. It does not promise indexing, ranking, citation, model training, provider behavior, or semantic understanding.

  • This profile tests documented public discovery controls; it does not prove indexing, retrieval, ranking, citation, training inclusion, or model use.
  • User-initiated agents are informational because provider behavior may be context dependent.

Audit 2 of 2 — a clean PASS looks like this

https://example.com · 27 protocol executions · protocol set gm-ai-consumer-compat/1.1.0

A different site and a different result: PASS, zero open blockers, one informational finding (no /llms.txt). Nothing to fix is a valid audit result — the audit reports what the evidence shows. This second projection is published for contrast: the same report surface, one FAIL and one clean run.

Audit profile

Public AI discovery compatibility

Scan timestamp

2026-08-30T10:49:58.532Z

Profile + protocol set

public-ai-discovery/1.0.0

gm-ai-consumer-compat/1.1.0

Sealed bundle digest d2ef54…70c2a

Audit verdict

PASS

Execution state: COMPLETE

PASS means every required protocol completed without an open production blocker. INCOMPLETE means the required evidence was not fully obtained, so compatibility was not established.

Blockers

0

Warnings

0

Information

1

Verified remediations

0

Findings and fixes

Findings below are tied to named protocol observations. Experimental observations cannot determine the verdict.

INFOLLMS_TXT_NOT_FOUND

The site does not publish a /llms.txt file

The observed site does not publish a /llms.txt file. This is an informational optimization opportunity and does not indicate that AI systems cannot access, understand, or cite the site.

Publish a /llms.txt file

Consider publishing a /llms.txt file describing the site for AI agents. Absence does not prove an access, understanding, or citation problem; this is an advisory optimization.

  1. Create a /llms.txt file at the site origin with a valid H1-style title heading.
  2. Ensure the body is at least the required minimum size beneath the title.
  3. Describe what information you intend to share with AI agents without exposing unpublished content.

Verification protocols: acquisition.llms-txt

  • The target does not publish a /llms.txt file.

Your URL will produce a different bundle. Run the same audit surface free — 5 scans/month, no card. New scans run the current protocol set gm-ai-consumer-compat/1.6.0.

Run this audit on your siteRead the proof contract

Protocol execution

27 of 27 protocol executions on this run succeeded. Required protocols determine whether this audit is complete. Informational protocols add context but do not create a pass requirement.

  • acquisition.http1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • acquisition.robots1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • acquisition.llms-txt1.0.0

    SUCCEEDED

    gm:llms-txt-probe

    Informational

  • representation.raw-rendered1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • policy.robots1.0.0

    SUCCEEDED

    openai:oai-searchbot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    anthropic:claude-searchbot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    google:googlebot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    perplexity:perplexitybot

    Required

  • policy.robots1.0.0

    SUCCEEDED

    openai:gptbot

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    anthropic:claudebot

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    google:google-extended

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    openai:chatgpt-user

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    anthropic:claude-user

    Informational

  • policy.robots1.0.0

    SUCCEEDED

    perplexity:perplexity-user

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    openai:oai-searchbot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    anthropic:claude-searchbot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    google:googlebot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    perplexity:perplexitybot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    openai:gptbot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    anthropic:claudebot

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    google:google-extended

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    openai:chatgpt-user

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    anthropic:claude-user

    Informational

  • policy.ai-usage-headers1.0.0

    SUCCEEDED

    perplexity:perplexity-user

    Informational

  • extraction.main-content1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • structured-data.visible-consistency1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

  • freshness.dates1.0.0

    SUCCEEDED

    gm:direct-http-probe

    Required

Evidence and integrity

The digest below is the original sealed digest of the unredacted bundle. This page publishes a redacted projection, not the sealed artifact; the projection does not re-verify against that digest.

Schema version

gm-evidence-bundle/1.0.0

Protocol set version

gm-ai-consumer-compat/1.1.0

This bundle was sealed under gm-ai-consumer-compat/1.1.0. The current protocol set is gm-ai-consumer-compat/1.6.0; the two are not interchangeable.

original sealed digest of the unredacted bundle

d2ef5484349e31407d72a95374dff480e03f233795fd644b560cf21673f70c2a

Captured artifacts

  • Artifact 1

    RAW_HTTP_RESPONSE · HTTP 200 · 559 bytes

    https://example.com

    ff67a9d764d6a2367a187734e697f6a53217db9a21c101d410a113ca871a299d

  • Artifact 2

    ROBOTS_TXT · HTTP 404 · 559 bytes

    https://example.com/robots.txt

    ff67a9d764d6a2367a187734e697f6a53217db9a21c101d410a113ca871a299d

  • Artifact 3

    LLMS_TXT · HTTP 404 · 559 bytes

    https://example.com/llms.txt

    ff67a9d764d6a2367a187734e697f6a53217db9a21c101d410a113ca871a299d

  • Artifact 4

    RENDERED_DOM · HTTP — · 559 bytes

    https://example.com

    7b6cd9a1d881c4a69bf70b9babb5a4a90e38aa6f9933785508a38f665d4d4aab

  • Artifact 5

    NO_JAVASCRIPT_DOM · HTTP — · 559 bytes

    https://example.com

    7b6cd9a1d881c4a69bf70b9babb5a4a90e38aa6f9933785508a38f665d4d4aab

These paths return the same fallback document on example.com; identical hashes are expected here. Retrieval recorded as observed.

Verification

Baseline scan — no remediation verification on this run. A later scan is what would compare the remediated protocol against this baseline.

Scope and limitations

This audit reports what the named acquisition, policy, and extraction protocols observed. It does not promise indexing, ranking, citation, model training, provider behavior, or semantic understanding.

  • This profile tests documented public discovery controls; it does not prove indexing, retrieval, ranking, citation, training inclusion, or model use.
  • User-initiated agents are informational because provider behavior may be context dependent.

Get this same sealed bundle for your site — 5 free scans/month

Run this audit on your siteRead the proof contract