Structured Data
The Structured Data tab extracts and validates all three structured data
formats from every crawled page: JSON-LD from
<script type="application/ld+json"> tags,
Microdata from itemscope and
itemprop attributes, and RDFa from
typeof and property
attributes. It then checks the extracted markup against Google's rich result
requirements and reports what is eligible, what needs attention, and what
will not produce a result regardless of correctness.
Stats
Four summary cards at the top of the tab show the scope of structured data across the crawl:
Below the four cards, a validation summary shows the total count of errors and warnings found during schema validation. Errors indicate markup that will prevent a rich result from appearing. Warnings indicate issues that may reduce eligibility or quality but do not block the result outright.
Rich result eligibility
Below the stats, an eligibility card appears for each of the 27 rich result types Consuela validates. Each card shows:
- An eligibility badge: Eligible (green) when the markup meets all required properties, Eligible, restricted (warning) when the markup is correct but Google limits the result to certain partners or regions, or Not eligible (neutral) when required properties are missing or invalid.
- The number of pages where that type was found.
- Restriction text, when one applies, explaining why correct markup may not produce a visible result.
- A link to the Google documentation page for that type.
The 27 supported types are:
Nested objects are judged in context. A hiringOrganization
inside a JobPosting is validated as part of the
job posting, not as a standalone Organization. The exception is Carousel:
items inside an ItemList are standalone results
and are validated individually.
Restrictions
Valid markup and a visible rich result are two different things. Several types carry restrictions that mean correct markup will not produce a result for most sites. Consuela marks these as "Eligible, restricted" rather than "Eligible" and displays the restriction text on the eligibility card.
Consuela still validates these types fully. The markup may be consumed by other search engines or tools, and Google has restored removed features before. The restriction is a caveat on the outcome, not a reason to ignore the markup.
Schema validation
Validation runs in two passes. The first pass checks syntax: JSON-LD blocks
must parse as valid JSON, every block should contain an
@type property, and the
@context should reference
https://schema.org. The second pass checks each
recognised type against Google's required and recommended properties, reports
issues at three severity levels, and links each finding to the relevant
Google documentation page.
Each issue includes the property path within the JSON-LD, a description of what is wrong, a fix suggestion, and a link to Google's documentation for the affected type. For types with image requirements (Article, Recipe, Product, Video), the validator also checks minimum dimensions and supported aspect ratios.
A row of schema type filter buttons sits below the validation summary. Each button shows a type name found in the crawl. Selecting a type filters the pages table to show only pages containing that type, making it straightforward to audit one type at a time across a large site.
Pages table
The pages table lists every crawled page that contains structured data. Each row shows:
Rows are expandable. Clicking a row reveals the full list of types found on that page and a link to open the page in the page inspector, where the raw JSON-LD, Microdata elements, and RDFa attributes are shown alongside the validation findings for that individual page.
The table supports sorting by any column and filtering by the schema type buttons above it. Combined with the status column, this makes it possible to find, for example, every Product page with validation errors or every page carrying FAQ markup that will no longer produce a result.