Verification, schedule, and badge
Prove site ownership before enabling recurring scans or the public score badge.
Verification proves that a project owner can place or expose the required value on the public website. Sight stores the successful verification state and uses it as a prerequisite for operations that should not be available to an unverified third party, including recurring scans and the public score badge.
A verification result can fail because the value is missing, inaccessible, cached, or attached to a different hostname. Confirm the exact canonical domain and public response before retrying. Scheduling also depends on plan entitlement, while badge availability depends on both verification and the project’s current public settings.
Verification should be reviewed again after domain migrations, hostname changes, major CDN changes, or ownership transfers. A previously verified project can otherwise point at a site whose operational control has changed. Public badges should show current, interpretable scores and should not imply continuous monitoring when scheduling is disabled, failing, or limited by plan and credit availability.
- 1
Open Verification
Choose the supported verification method and add the provided value to the site.
Choose the method supported by the current product and copy the value exactly. Coordinate with the person who controls DNS, templates, or deployment configuration when the documentation change cannot be made directly.
- 2
Verify
Sight checks the public site and stores the verification timestamp on success.
Run verification only after the public change has propagated. If it fails, inspect the canonical hostname and delivered response rather than repeatedly submitting the same check without changing the underlying condition.
- 3
Enable scheduling
Starter and Pro can activate recurring daily scans after verification.
Confirm the project plan, recurring credit capacity, and desired configuration before enabling daily work. Assign someone to monitor failures and review whether the cadence remains useful as the project changes.
- 4
Publish a badge
Enable the public score badge only when the site is verified.
Review the score, label, destination, and public context before embedding the badge. The badge should not imply broader coverage or freshness than the latest completed verified scan supports.
Ownership is enforced
Project actions are organization-scoped. Schedule and badge changes reject unverified sites, and public badge delivery stays unavailable until verification succeeds.
Treat verification as a security boundary. Server-side authorization and project organization scope must remain in place even when a user can see or manipulate controls in the interface.