The Introductory report is the recommended first file to inspect or share with an AI assistant. It summarizes scan coverage, significant sitewide findings, page scores, and selected accessibility evidence without including every stored audit or discovery event.

Format: siteimp-introductory-v1
Primary data root: introductory
Does not contain: tables, database DDL, detailed audit inventories, or the complete page-discovery history.

Common export metadata

All five report formats include the same core envelope. Individual files are generated independently from the scan database; they are not slices of another downloaded JSON file.

PropertyMeaning
export_formatExact format identifier; use it when selecting a parser.
export_typeHuman-readable machine-friendly profile name.
purposeShort description of the intended use.
snapshot_idUUID for the scan represented by this report. Match it when combining scan-specific exports.
websiteWebsite identity and starting URL.
exported_at_utcTime the JSON file was generated, not the time the scan ran.
schema_fingerprintNoncryptographic fnv1a64-... identifier for the database table definitions. It is not a hash of scan results.
related_exportsNames and descriptions of the other available profiles, plus instructions for downloading them. It does not embed the other reports.
export_policyScope, retained evidence, and known omissions for the selected profile.

website contains website_key, website_slug, name, start_url, and registrable_domain. related_exports.available maps each profile name to export_format, purpose, and selected; selected identifies the current report, not a report that has already been downloaded.

JSON text stored in database columns ending in _json is decoded into JSON arrays or objects in table-based exports. Do not parse those fields as JSON strings again. SQL NULL becomes JSON null. Integer columns can represent boolean-style flags (0 and 1); consult the Schema export's create_sql for their constraints. Neither object-property ordering nor numeric row IDs should be used as a durable cross-scan identity.

Top-level structure

{
  "export_format": "siteimp-introductory-v1",
  "export_type": "introductory",
  "snapshot_id": "scan-uuid",
  "schema_fingerprint": "fnv1a64-...",
  "website": {"name": "Example", "start_url": "https://example.com"},
  "introductory": {
    "scan": {"status": "completed", "completed_at": "2026-11-16T18:18:05.876Z"},
    "signals": {"counts": {"broken_images": 1}},
    "accessibility_findings": [],
    "accessibility_summary": null,
    "count_explanations": {},
    "page_issue_summary": {"total_pages": 0, "pages_with_detected_issues": 0, "rows": []},
    "page_results": [],
    "timing": null,
    "interpretation_note": "Read this note for the limits of the overview."
  }
}

Abbreviated illustration: common metadata and many nested fields are intentionally omitted here. The example is not a complete schema validator fixture.

introductory field reference

PropertyType / shapeMeaning
scanobjectScan lifecycle, mode, version and stored completion summary.
timingobject or nullSelected timing fields from scan diagnostics.
signalsobjectSitewide generated link, image, sitemap and concentration findings.
accessibility_summaryobject or nullAggregated accessibility scores and audit-result counts.
accessibility_findingsarraySelected audits with failed, warning, manual or informative outcomes.
page_resultsarrayCompact fetch status and Lighthouse scores for every recorded page.
page_issue_summaryobjectRows for pages meeting the detected-issues filter.
count_explanationsobjectDefinitions of easily confused counts, especially image assets versus usages.
interpretation_notestringHow to interpret the report and when to request detailed evidence.

scan and timing

scan contains status, started_at, completed_at, stop_reason, stop_error, mode, pipeline_version, and summary_json. The decoded summary_json contains the stored scan summary, including counts, failures, derive_failures, timings, and snapshot metadata as available. A completed scan is not necessarily a flawless website; examine the findings and failure counts separately.

timing contains total_wall_clock_ms, internal_wait_ms, and external_wait_ms when diagnostics exist. Values are milliseconds; zero is different from missing. The scan summary may also contain a more complete timings object.

signals

PathMeaning
signals.countsSummary counts, including broken external links, broken internal links, broken images, sitemap-only pages, and crawl-only pages.
signals.broken_imagesfailure_count and rows describing defective distinct media assets.
signals.broken_external_linksfailure_count and supporting rows for external-link failures.
signals.broken_internal_linksfailure_count and supporting rows for internal-link failures.
signals.external_link_concentrationMay be null; when present, includes distinct_domain_count, total_external_links, and top_domains.
signals.sitemap_mismatchsitemap_only_count, crawl_only_count, and their associated URL lists.

In a broken-image row, useful fields include asset_url, final_url, issue_kind, status_code, content_type, fetch_error, usage_kinds, usage_count, page_count, and example_source_page_key. A response returning HTTP 200 can still be an invalid image if the content type does not represent the expected media.

accessibility_findings

Each entry identifies an audit (audit_key, source_audit_id) and counts its outcomes: affected_page_count, failed_page_count, warning_page_count, manual_page_count, informative_page_count, passed_page_count, not_applicable_page_count. It can also contain impact_hint, likely_scope_hint, and failure_pages with page_key, url, and status for failed or warning page results.

Confirmed failures appear before manual or informative checks. The ordering helps readers find tested failures first; use the count/status fields, not an array index, as the source of truth. A manual result means the check requires human assessment. It does not mean a failed accessibility test. notApplicable does not mean pass or fail.

accessibility_summary includes scores (average_accessibility_score, lowest_accessibility_score, highest_accessibility_score), coverage (scanned_pages, pages_with_lighthouse, pages_without_lighthouse), occurrence classification (site_wide_issue_count, recurring_issue_count, isolated_issue_count), and aggregate outcome counts (total_failed_audits, total_warning_audits, total_manual_audits, total_informative_audits, total_passed_audits, total_not_applicable_audits, total_audit_results). It also includes top_issues_json, affected_page_count, and lighthouse_version when present. Aggregate counts cover audit outcomes, not necessarily distinct defects.

page_results

Every entry contains page_key, url, status_code, fetch_error, robots_blocked, and lighthouse. The lighthouse value may be null; when populated it holds lighthouse_mode, performance_score, accessibility_score, best_practices_score, and seo_score. Reported Lighthouse category scores use a 0–100 scale. Do not interpret a missing score as zero.

page_issue_summary

total_pages is the total number of page-summary rows considered. pages_with_detected_issues counts the rows retained after filtering. Each item of rows can include page_key, requested_url, final_url, document_title, status_code, has_fetch_issue, fetch_issue_kind, missing_title, missing_description, not_in_sitemap, broken_internal_links, broken_external_links, and broken_images.

The rows are not all pages. A page with only an accessibility audit failure, for example, may not appear for that reason alone. Consult page_results for the full recorded page list and accessibility_findings for accessibility failures.

count_explanations

The keys are literal field paths and the values are explanations. In the current export they distinguish:

  • signals.broken_images.failure_count: count of distinct broken assets.
  • signals.broken_images.rows[].page_count: number of pages referencing an asset.
  • signals.broken_images.rows[].usage_count: number of references/usages of that asset across pages.
  • page_issue_summary.rows[].broken_images: affected media usages/references on that page, not distinct asset URLs.

For example, one broken social-preview asset can appear twice on each of twelve pages, resulting in 24 usages without implying 24 different broken files.

Example: list pages with low performance scores

import json

with open("introductory.json", encoding="utf-8") as file:
    report = json.load(file)

assert report["export_format"] == "siteimp-introductory-v1"
for page in report["introductory"]["page_results"]:
    lighthouse = page.get("lighthouse") or {}
    score = lighthouse.get("performance_score")
    if score is not None and score < 90:
        print(page["url"], score)

This uses measured scores only. It does not infer the source code or framework responsible for a score.

Scope and cautions

The overview retains summary totals for N/A and manual outcomes but omits N/A-only audit records and repeated page-level manual-review evidence. For all individual accessibility checks, use the Accessibility export. For link provenance, use Page Discovery. For column definitions, use Schema. For comprehensive scan evidence, use Complete.

This is not a ready-made ticket queue. Counts are observations; recommendations and estimated repair times require separate investigation.