The Schema export is a reusable reference describing the SQLite scan-evidence table definitions known to Siteimp. It lists column declarations, SQL table definitions, and foreign keys. It is not a dump of scan records and is not a substitute for Introductory, Accessibility, Discovery, or Complete.
Format: siteimp-schema-v1
Primary data root: schema
Current table count: 24 table definitions.
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.
| Property | Meaning |
|---|---|
export_format | Exact format identifier; use it when selecting a parser. |
export_type | Human-readable machine-friendly profile name. |
purpose | Short description of the intended use. |
snapshot_id | UUID for the scan represented by this report. Match it when combining scan-specific exports. |
website | Website identity and starting URL. |
exported_at_utc | Time the JSON file was generated, not the time the scan ran. |
schema_fingerprint | Noncryptographic fnv1a64-... identifier for the database table definitions. It is not a hash of scan results. |
related_exports | Names and descriptions of the other available profiles, plus instructions for downloading them. It does not embed the other reports. |
export_policy | Scope, 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.
Structure
Each key under schema names a table. The corresponding value contains:
| Field | Shape | Meaning |
|---|---|---|
columns | array | SQLite PRAGMA table_info results, normalized into objects. |
columns[].cid | integer | Column position in the table. |
columns[].name | string | Stored column name. |
columns[].declared_type | string | SQLite declared type, such as TEXT, INTEGER, or REAL. |
columns[].not_null | boolean | Whether the SQLite schema declares NOT NULL. |
columns[].primary_key_position | integer | Position in a primary key; zero means not in the primary key. |
foreign_keys | array | Normalized SQLite PRAGMA foreign_key_list entries. |
foreign_keys[].id, sequence | integers | Foreign-key group ID and position within a composite key. |
foreign_keys[].target_table | string | Referenced table. |
foreign_keys[].from, to | strings or null for to | Source and target columns. |
create_sql | string or null | Recorded SQL CREATE TABLE declaration from SQLite. |
The create_sql definition is particularly useful for understanding CHECK constraints, allowed status strings, defaults, UNIQUE keys, and composite foreign keys that aren't fully described by the column list alone.
Example: a truncated table definition
{
"export_format": "siteimp-schema-v1",
"schema": {
"pages": {
"columns": [
{"cid": 0, "name": "id", "declared_type": "INTEGER", "not_null": false, "primary_key_position": 1},
{"cid": 1, "name": "snapshot_id", "declared_type": "TEXT", "not_null": true, "primary_key_position": 0}
],
"foreign_keys": [
{"id": 0, "sequence": 0, "target_table": "snapshots", "from": "snapshot_id", "to": "snapshot_id"}
],
"create_sql": "CREATE TABLE pages (...)"
}
}
}
This example is intentionally abbreviated and the create_sql string is illustrative, not executable DDL. The real report supplies the full definitions.
Current table inventory
The Schema export includes these 24 table definitions:
| Area | Tables |
|---|---|
| Scan lifecycle | snapshots, scan_diagnostics |
| Page mapping | pages, page_discovery, page_html_summary, links |
| Sitemap and robots | scan_sitemaps, sitemap_entries, sitemap_mismatches, robots_txt_records |
| Lighthouse/accessibility | lighthouse_reports, scan_accessibility_summary, scan_accessibility_issues |
| External links | external_targets, external_links, external_link_checks |
| Media | media_assets, page_media, media_exif_summary |
| Artifacts | artifacts |
| Internal execution state | page_jobs, external_link_jobs, media_jobs, external_host_state |
Important: Schema describes internal execution-state tables even though the Accessibility, Page Discovery and Complete evidence exports deliberately omit their rows. A table appearing in Schema does not mean its records appear in another profile.
Fingerprint and versioning
schema_fingerprint is calculated from the Schema export's scan-table definitions, including columns, foreign keys, and SQL declarations. It is a noncryptographic FNV-1a 64-bit fingerprint formatted fnv1a64-.... Different snapshots from the same database structure can share a fingerprint; changing a schema definition can change it.
Use it to determine whether a previously downloaded Schema reference likely applies to another export. Match it exactly. Still check the other export's export_format: a matching database schema fingerprint does not promise that transformation rules, generated analysis, or future output profiles are identical.
Unlike the four other profiles, Schema's main value is reusable table documentation. The file still includes the snapshot_id and website of the completed scan from which it was requested, but the schema object contains table definitions, not that scan's data.
Example: inspect columns and relationships
import json
with open("schema.json", encoding="utf-8") as file:
report = json.load(file)
assert report["export_format"] == "siteimp-schema-v1"
for table_name, definition in report["schema"].items():
print("TABLE", table_name)
for column in definition["columns"]:
print(" ", column["name"], column["declared_type"])
for foreign_key in definition["foreign_keys"]:
print(" ->", foreign_key["target_table"],
foreign_key["from"], foreign_key["to"])
What Schema cannot tell you
A column declaration does not prove a particular record was collected, that a crawler succeeded, or that a website has an issue. Schema cannot supply a Lighthouse score, a page title, or a list of accessibility failures. Those observations belong in the scan-specific exports.
For the actual audit results use Accessibility; for crawl events use Page Discovery; for comprehensive stored evidence use Complete.