Paste a page and see which schema.org types it carries, which blocks are broken, and which fields that say who and where you are are empty.
One public page, read as delivered, without running scripts. Nothing is stored.
A person reading your home page knows at a glance that the logo is your name and the line in the footer is your address. A program sees a page of text. Markup puts labels on the facts: this is the business, this is its name, this is where it is, these are its profiles on other sites. When those labels are missing, a reader that wants to describe you has to infer them, and it may infer wrong or not bother.
The fields this checker cares about are the ones that identify you: name, url, logo, sameAs (your profiles elsewhere) and, for a local business, address and telephone. Our study of 731 websites lists missing structured data among the five reasons assistants find a site hard to read and quote.
OperStack<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Harbor Dental Studio",
"url": "https://example.com/",
"logo": "https://example.com/logo.png",
"telephone": "+1 503 555 0100",
"address": { "@type": "PostalAddress", "streetAddress": "12 Harbor St", "addressLocality": "Portland", "addressRegion": "OR", "addressCountry": "US" },
"sameAs": ["https://www.instagram.com/example", "https://maps.google.com/?cid=0"]
}
</script> An invented example. Every value must match what the page itself says: markup that disagrees with the visible text is worse than none.
Labelled facts make you easier to read, not more likely to be recommended. The free OperStack check reads your site the way an assistant does and asks ChatGPT the questions your buyers ask, to see whether it names you.
No, and be wary of anyone who promises that. Markup helps a machine read who you are and what a page is without guessing. Whether an assistant names you depends far more on what it knows about you from other sites. Google says there is no special schema.org markup you need to add to appear in AI Overviews and AI Mode (Google: AI features and your website).
Because the alternative is guessing. Without markup, a program reading your page has to work out from layout and wording which line is your name, which is your city and which number is a price. With it, the facts are labelled. Google also uses markup for rich results in ordinary search (Google: introduction to structured data).
JSON-LD, unless your platform already writes one of the others. It is one block in the page that does not tangle with your HTML, and it is the format Google recommends. All three are read, and this checker looks for all three.
A JSON-LD block that is not valid JSON: a missing comma, a stray quote, an unescaped line break. Programs skip a block they cannot parse, so everything in it is lost, not only the faulty line. That is the one problem here worth fixing today.
No. It reads one page as delivered, without running scripts, and checks the fields that tell a machine who you are. For every property of every type use the Schema.org validator, and for Google's rich results the Rich Results Test. Markup added by JavaScript after the page loads is not seen here, and many AI robots do not see it either.
No. We read the page once while this page loads and keep nothing: no account, no cookie, no database.
Built by Maksim Shchegolev, founder of OperStack. Free, no account, no cookie. The address you check is not stored.