Check Engine / Tools / JSON-LD checker

JSON-LD structured data checker

Paste the address of any page. The checker reads every JSON-LD block on it, says which line breaks the JSON if one does, and lists the properties each item needs for a rich result that are missing.

    Free, no sign-up required. No account, and nothing about the page you check is stored.

    1. Paste the address of a product, recipe, event or article page.
    2. Press Check structured data.
    3. Read each block's verdict and the properties it still needs.

    You will see:

    • Every JSON-LD block on the page, with its type and name
    • The line and column where broken JSON stops a parser
    • The properties a rich result needs that are missing

    This reads the page you paste. Check Engine reads the structured data on every page of your site and checks that what the markup says matches what the page shows.

    Reading structured data page after page? The free Check Engine SEO add-on for Chrome does it from the tab you are on, with nothing uploaded.

    What it checks

    • Whether each block is valid JSON. One stray comma makes a search engine discard the whole block. The checker names the line and column where the parser stopped.
    • Whether it says it is schema.org. A block with no @context declares types that mean nothing to a search engine.
    • Required properties. For 15 types (Article, BlogPosting, BreadcrumbList, Event, FAQPage, HowTo, JobPosting, LocalBusiness, Offer, Organization, Product, Recipe, Review, SoftwareApplication, VideoObject), the properties Google requires for a rich result, from the same table Check Engine uses. Items inside other items, such as an Offer inside a Product, are checked too.

    Which properties each type needs

    The checker reports a type as incomplete when one of these is missing or empty. The list is the one inside Check Engine, taken from Google's structured data documentation.

    TypeNeeds
    Productname, image
    Offerprice, priceCurrency
    Recipename, image, recipeIngredient, recipeInstructions
    Eventname, startDate, location
    JobPostingtitle, datePosted, hiringOrganization, jobLocation
    FAQPagemainEntity
    HowToname, step
    Articleheadline
    BlogPostingheadline
    LocalBusinessname, address
    Organizationname
    ReviewreviewRating, author
    BreadcrumbListitemListElement
    VideoObjectname, thumbnailUrl, uploadDate
    SoftwareApplicationname, applicationCategory

    An Offer is usually nested inside a Product, and a Review inside a Product or a LocalBusiness. Both are checked where they sit, so a Product with a complete name and image can still fail on the price of its Offer.

    What it does not check

    • Microdata and RDFa. It reads JSON-LD, the format Google recommends.
    • Whether the markup matches the page. A price or rating in the markup that the visitor cannot see is against Google's guidelines. Check Engine compares the markup with the visible page; one free check cannot.
    • Whether Google will show a rich result. Valid, complete markup makes a page eligible. Google decides whether to show it.

    Check Engine reads the structured data on every page it crawls, compares it with what each page shows, and ranks what to fix with the rest of its 99 checks.

    $59once

    For Macs with Apple silicon or Intel, macOS 12 or later, and 64-bit Windows

    Priced in US dollars. Checkout shows your currency and any local tax.

    On a Mac? Get the Mac version.

    Launch price: $29.50 once, through 30 November. From 1 December: $59. Buy applies the code FOUNDINGDOCKET for you; if the checkout shows $59, enter it under ‘Have a discount code?’.

    Screaming Frog is $279 a year. Ahrefs plans with Site Audit run $129–$449 a month. Check Engine is $59 once. Screaming Frog’s price read 4 November 2026, Ahrefs’ 9 November 2026.

    30 days, no conditions, no questions asked. Refund policy

    Related

    Common questions

    How do I test my structured data?

    Paste the page address into the checker above. It reads every JSON-LD block on the page, reports invalid JSON with the line and column, and lists missing required properties.

    Why is my structured data not showing in Google?

    Usually because the JSON is invalid, a required property is missing, or the marked-up content is not visible on the page. Valid, complete markup makes a page eligible; Google decides whether to show a rich result.

    Does this check Microdata or RDFa?

    No. It reads JSON-LD, the format Google recommends for structured data.