JSON-LD structured data checker
Paste JSON-LD to check syntax and the properties Google asks for on common types.
FreeRuns in your browserNo signupUpdated 2026-11-05
Required and recommended properties follow Google Search Central's structured data docs, last checked November 2026. Runs in your browser.
Items
1
from 1 JSON-LD block
Errors
1
1 warning
Item 1 · Event
1 errorChecked as: Event
Required by Google
- ✓ name
- ✓ startDate
- ✓ location
- ✗ location.address
Recommended, not present
- endDate
- eventStatus
- offers
- organizer
- performer
- Warningimage "/images/open-day.jpg" is not an absolute URL. Use the full https:// address.
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Open day at Example Dental Clinic",
"description": "Meet the team, tour the clinic and ask about whitening and implants.",
"startDate": "2026-12-05T10:00:00+04:00",
"image": "/images/open-day.jpg",
"location": {
"@type": "Place",
"name": "Example Dental Clinic, Dubai Marina"
}
}This checks syntax and Google's listed properties. Google's Rich Results Test also checks the live page and policies; use both before you publish.
About this tool
How it works and how to read the result.
Need this done for you?
Technical SEO & performance
Faster pages, clean structure and better visibility in search.
See the serviceWhat it does
A JSON-LD checker reads structured data the way a search engine would and tells you what is wrong with it. Paste a single JSON-LD object or a whole page's HTML; every script of type application/ld+json is pulled out and parsed. Syntax errors are reported with the line and column, and a common cause, the trailing comma, is called out. Each item is then checked against the properties Google lists as required and recommended for that type. The checker also flags relative image and page URLs, dates that are not in ISO 8601 format and empty values. Items inside an @graph are checked one by one.
How to use it
- Paste your JSON-LD, or view the page source and paste all of it.
- Fix any "Syntax" errors first; nothing else can be checked until the JSON parses.
- Work through each item's red badges, which are required properties that are missing.
- Add the grey "recommended" properties that apply to your content.
- Publish, then confirm the live page with Google's Rich Results Test.
How to read the result
The sample is an Event for a clinic open day, inside a script tag. The Items stat shows 1 item from 1 JSON-LD block, and Errors shows 1, with 1 warning.
In the item's panel, "Required by Google" lists four properties. name, startDate and location have green ticks. location.address is red: the location is a Place with a name but no postal address, and Google needs the address to show the event. Add a PostalAddress inside location to clear it.
The warning is the image: "/images/open-day.jpg" is a relative path, and structured data should use the full https:// address. The grey badges under "Recommended, not present" are endDate, eventStatus, offers, organizer and performer. None is required, but each one gives Google more to show; endDate and eventStatus are worth adding to almost every event.
When the JSON itself is broken, a "Syntax" line replaces the item panels, for example "invalid JSON at line 1, column 63. Expected double-quoted property name. Check for a trailing comma before } or ]." Fix that line and the checks run again as you type. The formatted JSON at the bottom is your markup re-indented, which makes nesting mistakes easier to see.
To write markup from scratch, use the article schema generator, the product schema generator or the breadcrumb schema generator. For tidying any JSON, try the JSON formatter. We add, test and monitor structured data as part of our technical SEO service.
Questions
Frequently asked.
How is this different from Google's Rich Results Test?
Google's test fetches the live page or code, renders it and reports what Google itself can read, including policy problems. This checker works on what you paste, before anything is published, and explains syntax errors by line and column. Use it while writing markup, then confirm with the Rich Results Test once the page is live.
Which types does it check?
Article, NewsArticle and BlogPosting, Product, LocalBusiness and its common subtypes, Organization, BreadcrumbList, Event, Recipe, JobPosting, VideoObject, SoftwareApplication, FAQPage, Review and AggregateRating. Required and recommended properties come from Google Search Central's documentation. Other types are checked for valid JSON, @context, @type, dates and URLs.
Does valid markup guarantee a rich result?
No. Google decides whether to show a rich result based on the page, the query and its own policies. Valid markup makes a page eligible; it does not promise anything. Some types, such as FAQPage, no longer produce rich results in Google at all, although the markup is still valid schema.org.
More in SEO
Related tools.
Your next move
Like what you see? Tell us about it.
A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.
India · Working with clients worldwide