Illustrative service page

Start with what the page can prove.

This demo audit examines public pages, their existing metadata, and their structured data before any annotation is proposed.

Audit scope

A practical baseline for a public website.

An audit begins with a crawl of publicly accessible, canonical pages. It identifies the material a visitor can see, the information already exposed to machines, and any places where an annotation could contradict the page or duplicate existing markup.

  • Page titles, descriptions, canonicals, and robots directives
  • Existing JSON-LD, Microdata, and RDFa markup
  • Visible entity facts, headings, FAQs, authorship, and navigation
  • Conflicts, duplicates, invalid syntax, and missing required properties

What a review produces

Evidence before delivery.

The prototype keeps the review record explicit so a future delivery adapter has a precise, reversible input.

A

Coverage record

The URL, canonical URL, fetch outcome, content type, and crawl time establish what was actually inspected.

B

Candidate record

The proposed type, properties, evidence links, validation result, and reviewer decision remain attributable to one page.

C

Delivery record

An immutable version identifier lets a verifier distinguish a baseline response from an annotated response.