Vahan Petrosyan
Language · English

Structured Data and Schema Markup Audits

A schema markup audit checks both vocabulary and meaning. A page can pass a syntax test while naming two providers for one service or describing an offer that visitors cannot find. The review follows the main entity through its identifiers and relationships, then compares the resulting graph with the content on the page.

What you get

  • A template inventory of JSON-LD types, identifiers and competing markup sources.
  • A comparison between visible facts and the entities described in each graph.
  • Corrected examples and separate tests for Schema.org validity and applicable Google features.

Who it's for

  • A theme and a plugin both publish markup for the same entity.
  • New templates need to describe services, products, authors or their relationships consistently.

How it works

  1. Identify the subject

    Determine what each page describes and which facts are visible to a visitor.

  2. Trace the graph

    Follow entity identifiers, providers, offers and breadcrumbs across templates.

  3. Validate the repair

    Check vocabulary, feature-specific rules and the graph actually served by the site.

Related articles

All articles

Contact

Frequently asked questions

Can valid JSON-LD still describe the wrong thing?

Yes. A validator may accept a price, author or product type even when it belongs to another page. Comparing markup with visible content catches that mismatch.

What is the purpose of mainEntity?

On a service page it identifies the service being described. A separate identifier for the page distinguishes the published document from the service itself.

Does valid markup guarantee a rich result?

Google decides whether to show a supported feature. The audit checks eligibility where a feature exists and records vocabulary issues separately.