Free tool
Schema markup checker and generator
Paste a page URL to list its JSON-LD and find what is missing or broken, or use the generators below to write FAQPage and Organization markup that passes.
Free, no sign-up. Results for the same URL are cached for an hour.
Generate markup
Two generators for the markup that matters most on marketing and content pages. Fill in the fields, copy the script tag into the head of the page, then run the checker on the published URL.
The questions and answers must also be visible on the page, word for word.
Which types matter for AI visibility
- Organization on the home and About pages, with sameAs links, so engines resolve your brand to one entity.
- Article or BlogPosting on content, with headline, author, datePublished and dateModified, so answers can attribute and date what they quote.
- FAQPage wherever the page answers questions visibly; it hands engines ready-made question-and-answer pairs.
- SoftwareApplication or Product on product pages, with a name and category, and offers when prices are public.
- BreadcrumbList on deep pages, so engines understand where a page sits in the site.
Common mistakes the checker catches
- A trailing comma or an unescaped quote that makes the whole block invalid JSON.
- A missing @context, so the node is not recognized as schema.org.
- Article markup without datePublished, or an author without a name.
- FAQPage with an empty mainEntity, or Questions without an acceptedAnswer.
- Product and SoftwareApplication nodes with no name or category.
- Markup injected by JavaScript after load, which does not appear in the HTML and is invisible to most crawlers.
FAQ
What is schema markup?
Structured data, usually written as JSON-LD inside a script tag, that describes a page in schema.org vocabulary: this is an Article by this author on this date, this is an Organization with this logo, these are the questions and answers on this page. Search engines and AI crawlers read it to understand the page without guessing.
Why does schema matter for AI search?
AI engines need to identify entities (your company, your product, the author) and the type of content they are reading. Clear JSON-LD removes ambiguity, and FAQPage markup in particular gives engines question-and-answer pairs in the exact shape they quote.
What does the checker test?
That every JSON-LD block parses, declares a schema.org context, has a @type, and includes the properties Google documents as required for that type. It also lists recommended properties that are missing. It walks nested nodes too, so an Article with an author that has no name is flagged.
Is this the same as Google's Rich Results Test?
No. Google's test checks eligibility for specific rich results and renders the page. This checker is faster and reads the raw HTML, which is what AI crawlers see. Use both: this one to catch structural mistakes, Google's for rich-result eligibility.
Should FAQ answers be visible on the page?
Yes. FAQPage markup must mirror questions and answers that visitors can read on the page. Hidden or mismatched FAQ markup is treated as spam by Google and is useless to AI engines, which quote the visible text.
Where should Organization markup go?
On the home page and the About page at minimum, with the same name, url and logo everywhere, and sameAs links to your official profiles. Consistency across pages is what lets engines treat the brand as one entity.
Does the generator send my data anywhere?
No. The FAQ and Organization generators run entirely in your browser. Copy the output into the head of your page.
More free tools
Markup is a prerequisite; citations are the result
LeapScope audits every signal on a page, not just schema, and tracks whether AI engines cite the page afterwards.