LaunchRanked

Structured data validator

Paste a URL. We pull out every JSON-LD block, flag broken JSON, and check each type against the properties Google's docs list as required.

What this validator does

It fetches the page, pulls out every <script type="application/ld+json"> block and parses each one. Broken blocks get the parser’s message with a line and column, plus a hint for the usual culprits: a trailing comma, curly quotes pasted from a doc, or a raw line break inside a string. A block with a syntax error is ignored completely, so one stray comma can hide all your markup.

How we check properties

For each entity, including the members of an @graph, we read its @type and compare it with the properties Google’s documentation marks as required for that feature. The wording is deliberate: Google may require these for a rich result. Some types, like Article and Organization, have no required properties at all; for those we list the recommended ones you’re missing. Each entity links to the Google page we used.

  • Product: name, plus one of offers, review or aggregateRating.
  • SoftwareApplication: name, offers.price, and aggregateRating or review.
  • LocalBusiness: name and address. Event: name, startDate, location.
  • VideoObject: name, thumbnailUrl, uploadDate. Recipe: name and image.
  • BreadcrumbList: itemListElement, with position and name on each item and at least two items.

We also flag dates that aren’t ISO 8601 and a missing @context. FAQPage and HowTo are checked but marked as retired: Google no longer shows either rich result.

Getting markup right

  1. Only mark up what’s visible on the page. A price or rating in JSON-LD must match the page text.
  2. Generate JSON-LD from the same data that renders the page, never by hand per page.
  3. Validate after each deploy, then confirm eligibility in Google’s Rich Results Test.

Start from clean templates with the schema markup generator. On Versely, Organization, Breadcrumb, FAQ, Article, SoftwareApplication and VideoObject JSON-LD were part of the technical base, as described in the case study.

Limits

Server HTML only: markup injected by JavaScript isn’t seen here. We check common Google features, not every schema.org type, and show up to 30 blocks.

Questions

Is this the same as Google's Rich Results Test?

No. We read your server HTML and check JSON-LD syntax and the properties Google's documentation lists as required. Google's Rich Results Test renders the page and applies Google's full rules, so use it as the final word on eligibility. Ours is quicker for spotting broken JSON and missing basics across a page.

Does structured data improve rankings?

Google has said structured data isn't a general ranking factor. It helps Google understand the page and can make it eligible for rich results, like product prices or breadcrumbs, which can change how the result looks. Eligibility is never a guarantee that Google shows one.

Should I remove my FAQPage markup now?

You don't have to. Google stopped showing FAQ rich results on May 7, 2026, but FAQPage is still valid schema.org, and Google's docs say unused structured data doesn't cause problems. Other tools and AI systems may still read it.

JSON-LD, microdata or RDFa?

Google supports all three and recommends JSON-LD because it sits in one script block, separate from your HTML, and is easier to generate and maintain. This validator only checks JSON-LD; it counts microdata and RDFa so you know they're there.

Autopilot · early access

Want this fixed automatically?

Autopilot checks your site, publishes researched articles at a safe pace, and tracks whether ChatGPT, Perplexity, Gemini and Claude cite you. $49/mo.

Related free tools

See all free tools