Free Schema Markup Checker
Paste a URL to see which structured data it exposes — Organization, WebSite, FAQPage, Article, Product — and what's missing for rich results in Google and confident citations in AI answers.
What structured data does, and does not do
JSON-LD is machine-readable information about a page, embedded in a script tag using the schema.org vocabulary. It tells search engines and AI systems who published a page, what kind of thing it describes, and facts such as dates, prices and addresses, without them having to guess from your layout.
Be clear about the payoff. Schema is not a direct ranking factor. Its value is that it makes your pages unambiguous, and for some types it makes you eligible for rich results in Google. Not every type produces a visible enhancement: Google limited FAQ rich results to a small set of authoritative sites in 2023 and retired HowTo rich results, and eligibility keeps changing, so check Google's Search Gallery for what is currently supported. Valid markup is still worthwhile for the context it gives. No AI provider has published that it uses schema as a citation input, so treat it as good hygiene that helps engines resolve your identity rather than a guaranteed boost.
Which schema to add, by type of site
You do not need every type. Add the ones that describe what each page really is.
- Every site — Organization (name, url, logo, sameAs links to your official profiles) and WebSite.
- Articles and blog posts — Article or BlogPosting with headline, image, datePublished, dateModified and a real author.
- Local businesses — LocalBusiness with address, telephone, opening hours and geo coordinates.
- Online shops — Product with an Offer (price, currency, availability). Add AggregateRating only if real reviews are shown on the page.
- Software and SaaS — SoftwareApplication with an Offer.
- Navigation — BreadcrumbList on any page deeper than the home page.
- Question-and-answer content — FAQPage, only where the questions and answers are visible on the page.
Copy-ready examples
An Organization block belongs on your home page, and is the foundation the other types hang from. Replace the example values with your own.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://www.acme.example/#organization",
"name": "Acme Plumbing",
"url": "https://www.acme.example/",
"logo": "https://www.acme.example/logo.png",
"sameAs": [
"https://www.linkedin.com/company/acme-plumbing",
"https://www.facebook.com/acmeplumbing"
]
}
</script>An Article block belongs on each blog post. Dates must be in ISO 8601 form and match what the page shows. Point publisher at the same @id as your Organization so the two connect.
An Article example
This is a minimal BlogPosting that validates. Add more properties as your content warrants.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Spot a Hidden Water Leak",
"image": "https://www.acme.example/images/hidden-leak.jpg",
"datePublished": "2026-03-04",
"dateModified": "2026-09-18",
"author": { "@type": "Person", "name": "Dana Whitfield" },
"publisher": { "@id": "https://www.acme.example/#organization" }
}
</script>Rules that keep you out of trouble
Most structured-data problems come from breaking one of these.
- Match the visible page — markup describing content users cannot see can earn a manual action. Generate it from the same data that renders the page.
- Do not invent reviews or ratings — only mark up reviews that are genuinely displayed and genuine.
- Fill the required properties — a Product with no offer, or an Article with no headline, is incomplete and will be ignored.
- Use absolute URLs and ISO 8601 dates — relative URLs and free-text dates are the most common validation errors.
- Keep it in the server-sent HTML — if JSON-LD is only added by JavaScript, crawlers that do not run scripts never see it.
- Validate after every deploy — templates drift, and a stray comma silently invalidates a whole block.
How to check and fix your markup
Run the checker above to see which types your page exposes and what is missing. Then work through it.
- Fix any block that fails to parse first, since invalid JSON means none of it is read.
- Add the missing foundation types: Organization, then WebSite.
- Add the type that matches the page: Article, Product, LocalBusiness or similar, with its required properties.
- Validate with Google's Rich Results Test for rich-result eligibility, and the Schema Markup Validator at validator.schema.org for general correctness.
- Watch the Enhancements reports in Google Search Console for errors after Google recrawls.
Frequently asked questions
What is JSON-LD structured data?
Machine-readable facts about a page, written as JSON inside a script tag using the schema.org vocabulary. It is Google's recommended format and does not change how the page looks.
Does schema markup improve rankings?
Not directly. It can make a page eligible for rich results, which can lift click-through, and it gives search engines clearer context about what the page is. It is not a shortcut to ranking higher.
Why is my rich result not showing even though the schema is valid?
Valid markup only makes a page eligible. Google decides whether to show a rich result based on page quality, the query and its current policies, and some types are now shown only for certain kinds of sites. It can also take time after a recrawl.
JSON-LD or microdata?
JSON-LD. Google recommends it, it is easier to maintain because it sits apart from your HTML, and it is simpler to generate from your data.
Does structured data help with AI answers?
AI providers have not published that they use it as a ranking or citation input. It does give any system reading your page typed, unambiguous facts about who you are and what the page covers, so it is sensible hygiene, but do not rely on it for AI citations.
Can I have more than one JSON-LD block on a page?
Yes. A page commonly carries Organization, BreadcrumbList and an Article or Product block. Link them with @id references so they describe one coherent set of entities.
Go deeper
More free tools
Primary technical references & standards
- Google Search Central: SEO Starter Guide →
- Google Search Central: Structured Data & Schema Guidelines →
- Google web.dev: Core Web Vitals (LCP, INP, CLS) Documentation →
- llms.txt Standard: Providing Context for AI Crawlers →
- OpenAI: Web Crawlers & GPTBot Specification →
- Perplexity AI: PerplexityBot Indexing Overview →