Schema
Inspect JSON-LD parsing and selected structured-data types in the project's initial page HTML.
View as MarkdownSchema checks structured data in the initial HTML returned for your project URL. It helps you find missing or malformed JSON-LD, but is not a complete schema.org validator or a guarantee of rich-result eligibility.
Analyze structured data
- Open GEO Optimization → Analyze Schema.
- Review JSON-LD blocks, Schema types, Invalid blocks, and Microdata items.
- Read the checks and recommended type coverage alongside the page's actual purpose.
- Correct relevant markup in your website, publish it, then run the check again from Optimization.
A type is discovered from top-level objects, arrays, or @graph entries. Types buried in other arbitrary nested objects may not appear. Markup injected only after JavaScript runs is outside this initial-HTML analysis.
Understand the score
| Signal | Points |
|---|---|
| At least one JSON-LD block | 30 |
| Organization or WebSite type | 25 |
| BreadcrumbList type | 15 |
| Article, Product, or FAQPage type | 20 |
| At least one JSON-LD block and all blocks parse as JSON | 10 |
Microdata items are counted separately; they do not substitute for these JSON-LD scoring checks. A block that parses as JSON can still have missing properties, inaccurate values, unsupported vocabulary, or unsuitable nesting. “Valid” in this context means parseable JSON, not complete semantic validation.
Choose the right correction
- Invalid blocks: inspect JSON syntax, quoting, and trailing commas before adding more types.
- No JSON-LD: confirm whether your page intentionally uses another format or whether the markup exists only in the browser-rendered DOM.
- Missing type coverage: add only types that truthfully describe the page. Do not label unrelated content as a product, article, or FAQ solely to earn points.
- Unexpected types: inspect top-level arrays and graph entries and verify the correct URL was analyzed.
Check important structured data with appropriate external validators as well as the rendered and server-returned page. The report does not test every property or linked entity.
Save and share findings
Export downloads the displayed analysis as JSON. Share copies the report page URL without making it public. Refresh reanalyzes the current project URL for the displayed view; running the check from Optimization creates a new history entry.
For commerce-specific signals, continue to Shopping Feed. For missing server-rendered content, review Crawlability.