Checking a page's structured data
Get the markup
View the page source in your browser and copy it all, or copy just the script block with type application/ld+json. A bare JSON object works too.
Paste it in
Every JSON-LD block in the text is found and listed separately as Block 1, Block 2 and so on, with the types it contains.
Read the counts
Each block shows its number of errors, warnings and types found, then a table of findings with the path, such as
$.address.addressCountry, and a plain message.Fix and paste again
Edit the markup in your CMS or theme, paste the new version and confirm the findings have gone.
Take a clean copy
Choose Pretty print to read it or Minify to paste it back into a page, then copy or download the block.
Example: a plumber's homepage with two blocks
A fictional Stockport plumber's site has a Plumber block written by a developer and a WebSite block added by a plugin. The first parses but gets four warnings: three recommended properties are missing, and the country is written as UK when schema.org expects the ISO code GB. The second has a trailing comma, so it is not valid JSON at all and search engines will ignore it.
None of these stop the page working for visitors, which is why they go unnoticed. They do affect how reliably search engines and data tools read the business's details.
Block 1: "@type": "Plumber" with name, url, telephone, address (addressCountry "UK"), aggregateRating, openingHours
Block 2: {"@context":"https://schema.org","@type":"WebSite","name":"Brightwell",}Block 1: Plumber, PostalAddress, AggregateRating Errors 0 Warnings 4 $.openingHoursSpecification openingHoursSpecification is recommended for Plumber. $.geo geo is recommended for Plumber. $.image image is recommended for Plumber. $.address.addressCountry The ISO country code for the UK is GB. Block 2: Not valid JSON (line 1, column 72): Expected double-quoted property name in JSON at position 71 (line 1 column 72). Common causes: a trailing comma, single quotes or a missing quote.
Why local businesses should care
LocalBusiness markup and its subtypes (Dentist, Plumber, Restaurant and hundreds more) state a firm's name, address, phone, opening hours and location in a form machines can read without guessing. Search engines use it as one source when building results, and data tools, including lead finders, use it to read a site's details accurately.
That makes broken markup a genuine opening for agencies. A site with a stray comma in its JSON-LD, a wrong country code or no opening hours is a small, concrete fix you can show a client in a few minutes.
Questions people ask
What is JSON-LD?
JSON-LD is a way of adding structured data to a web page inside a script tag, using the schema.org vocabulary. It describes things such as a business, a product or an event with named properties, so search engines and other software can read the facts directly instead of interpreting the visible text.
Is this the same as Google's Rich Results Test?
No. This tool checks that the JSON is valid and flags common missing or mistyped properties. Google's Rich Results Test checks whether a page qualifies for specific search features under Google's own rules, which change over time. Use this one for quick fixes while editing, and Google's tool before you rely on a rich result.
Why does it say the country code should be GB?
Schema.org recommends the two-letter ISO 3166-1 code for addressCountry, and the code for the United Kingdom is GB, not UK. Many sites write UK, which a person understands but software may not match. Changing it to GB is a one-word fix.
Can I check a live page by its address?
This tool works on markup you paste, so it does not fetch pages itself. Open the page, view its source, copy everything and paste it in; every JSON-LD block in the source is found and checked separately.
Where your data goes
Checking happens in your browser. The HTML or JSON-LD you paste is not sent to Map Extract or anywhere else, and no page is fetched.
Checked against the tool on