The root URL for a site (for example https://example.com). Scans start here and may use sitemaps and internal links to discover candidate pages.
A single run that samples pages from a base URL and produces artifacts (report + JSON) plus a pass/fail decision when validation rules are provided.
A group of pages that share a similar URL structure. SEODiff summarizes results per template so you can see systemic issues (not just individual URLs).
A machine-readable identifier emitted by a check (for example schema_missing_required). Issue keys are what you should use in automation.
The percentage of sampled pages that have at least one failing issue key (0–100). Useful as a high-level gate when tuned carefully.
A diff-driven event created when monitoring detects a meaningful change compared to the previous run (new issues, spikes, drift).
A template-level history view that shows how a template evolves over time (drift, issue rate, scoring).