Technical checks
Structured data checks
Structured data tells search engines what this page is about in a form they can read directly, which is what a rich result is built from. Netrix can write it for a page whose business has a verified Google Business Profile, using the details already published there. You’ll find 5 checks in this group.
| State | Evidence | Owner |
|---|---|---|
| Found | Structured dataOriginal page and available evidence recorded | Audit |
| Reviewed | Decision recordedA person checked the target and proposed value | Human |
| Checked | Public page readLive result recorded separately | Netrix |
All checks in this group
Open a check to see what triggered it and what to do next.
Missing Structured Data
Structured data tells search engines what this page is about in a form they can read directly, which is what a rich result is built from. Netrix can write it for a page whose business has a verified Google Business Profile, using the details already published there.
Invalid JSON-LD Syntax
Correct the JSON syntax in the page's structured-data script and retest. This is distinct from missing markup or search-feature eligibility. Parser limits remain unmeasured rather than being reported as invalid JSON.
Selected Structured-Data Requirements Not Met
Review the validation codes for the selected Breadcrumb and Product snippet checks. These cover required fields and selected value constraints, not every schema.org type, JSON-LD expansion, content policies or guaranteed rich-result display. Custom contexts and split or referenced entities stay unmeasured. Markup is optional; this does not require adding it everywhere.
Unrecognized Schema.org Type
Check spelling and capitalization against Schema.org 30.0. This is a lexical advisory, not proof of invalid JSON-LD or rich-result eligibility. Newer vocabulary terms can be valid; custom contexts and external vocabularies remain unmeasured. Raw customer terms are not retained.
Unrecognized Schema.org Property
Check spelling and capitalization against Schema.org 30.0. This does not validate property domains/ranges or require optional properties. Newer terms can be valid; custom contexts and external vocabularies remain unmeasured. Raw customer keys and values are not retained.