How to Audit Structured Data for Valid, Eligible Rich Results

A structured data audit has to confirm three separate things, in this order: that the markup is technically valid, that it meets the eligibility requirements for the rich result you want, and that it accurately describes the content visible on the page. Passing a validator is necessary but not sufficient. Markup can be syntactically perfect, complete enough to be eligible, and still cause problems because it describes things the user cannot actually see. All three layers must hold.

## Why structured data deserves its own audit

Structured data is how you make content machine-readable for search features such as rich results and knowledge panels, and increasingly for how AI systems interpret a page. Unlike most technical SEO, errors here often fail silently: the rich result simply does not appear, with no obvious symptom. A deliberate audit is the only reliable way to find these gaps.

## Layer one: technical validity

Start by confirming the markup parses correctly. Common validity failures include:

- Malformed JSON-LD: missing commas, unclosed brackets, invalid escaping.

- Wrong data types: a number where a string is expected, or vice versa.

- Incorrect nesting of entities.

- Multiple conflicting blocks describing the same entity in incompatible ways.

JSON-LD embedded in a script tag is the most maintainable format and the easiest to audit, since it is separate from the visible markup. Where structured data is injected by JavaScript, validate the rendered output, not the raw source, because that is what search engines ultimately read.

## Layer two: eligibility for the target rich result

Each type of rich result has required and recommended properties. Valid markup that omits a required property will be ineligible. Audit by working backwards from the result you want:

1. Identify the rich result type relevant to the page (for example a product, article, FAQ, recipe or breadcrumb).

2. List the required properties for that type.

3. Confirm each one is present and populated with meaningful values.

4. Add recommended properties where they genuinely apply, since they can improve presentation.

A frequent finding is markup that is valid and well-formed but missing one required field, leaving it ineligible. Distinguishing "invalid" from "valid but ineligible" is one of the most useful outcomes of the audit.

## Layer three: accuracy and content match

This is the layer audits most often skip, and it is where the real risk lies. Structured data must describe content that is actually present and visible on the page. Audit for mismatches such as:

- Markup describing prices, availability or ratings that do not appear in the visible content.

- Markup for content hidden from users or only shown after interaction.

- Aggregate ratings that are not genuinely present on the page.

- Markup applied to the wrong entity or page type.

Misleading or invisible structured data can lead to the markup being ignored or to manual action. The guiding principle is simple: structured data should represent the main content of the page as a user sees it, never invent or exaggerate it.

## Audit for consistency across templates

Structured data is usually generated by templates, so a single bug repeats across thousands of pages. Sample several URLs per template and confirm:

- The same type is applied consistently where appropriate.

- Dynamic fields populate correctly, with no leftover placeholders or empty values.

- Entities are connected sensibly, for example breadcrumbs reflecting the real site hierarchy.

- There are no duplicate or contradictory blocks for the same entity.

Because the markup is template-driven, fixing the template fixes every page at once, which makes this a high-leverage area.

## Check entity relationships and identity

Beyond individual page markup, a maturing audit looks at how entities connect across the site: a consistently described organisation, clear relationships between articles and their authors, and breadcrumb trails that mirror the real structure. Coherent, connected entity data helps search engines and AI systems build an accurate model of who you are and what you publish, which matters increasingly for answer-style results.

## Re-validate after any content change

Structured data drifts out of sync when the visible content changes but the markup does not, or vice versa. Treat re-validation as part of your release process rather than a one-off. After template or content changes, re-check validity, eligibility and the content match for a representative sample.

Keeping markup valid, eligible and accurate across a large, frequently changing site is exactly the kind of repetitive verification that benefits from dedicated tooling; neart.ai builds enterprise-grade products in this area.

## Practical takeaway

Audit structured data in three layers: confirm it is technically valid, confirm it meets the required properties to be eligible for your target rich result, and confirm it accurately matches the content a user actually sees. Validate the rendered output, fix template-level bugs once to fix every page, and never describe content that is not genuinely on the page.