Schema validator.

Why schema markup exists.

This schema validator reads the JSON-LD and microdata on a page, or in code you paste, and checks it against the full schema.org vocabulary and Google’s documented rules for rich results. Each item gets a clear status: green for valid, amber for warnings and red for errors, with a plain explanation of every problem and how to fix it.

Search engines are good at reading words, but a page doesn’t tell them what those words are. Is “4.8” a rating or a version number? Is this page a question, an article or an event? In 2011, Google, Bing and Yahoo launched schema.org as one shared vocabulary for answering those questions, and Yandex joined later that year. Today it covers more than 900 types of things, from articles and products to forum posts and job listings.

You add it to a page as structured data, most often as a JSON-LD script in the page’s HTML. Google recommends JSON-LD because it sits apart from your design and is easy to maintain. Microdata and RDFa, which add attributes to your HTML tags, work too.

What it does for a page.

• Rich results. Correct markup makes a page eligible for richer search listings: breadcrumbs, review stars, event dates, job listings, and forum and Q&A results.
• Clear meaning for machines. Search engines and AI assistants can tell who wrote a post, when, and what it answers, instead of guessing from the layout.
• Connections between things. Linking your organization, authors and pages helps search engines understand who is behind your content.

What it doesn’t do: Google says structured data isn’t a ranking factor on its own, and valid markup doesn’t guarantee a rich result. It makes your page eligible and easier to understand. The content still has to earn the click.

What this validator checks.

• Every schema.org type and property. All 941 types and 1,538 properties from the current schema.org vocabulary, with spelling suggestions, so “Prodcut” points you to “Product”.
• Syntax. Broken JSON, missing @context and missing @type: the mistakes that make search engines skip a block entirely.
• Properties that fit the type. Properties schema.org doesn’t define for that type, and properties that have been superseded.
• Formats. ISO 8601 dates, full URLs, and numbers where numbers belong.
• Google’s rules. Required and recommended properties for the rich result types below.
• Community pages. Answer counts that don’t match the answers, replies that aren’t typed as comments, and markup that doesn’t match the page’s visible text.
• Conflicts. Two Organization or Article blocks on one page, a common sign that a theme and a plugin are both adding markup, plus pages set to noindex.

Types with Google rule checks.

• Article, NewsArticle, BlogPostingHeadline, image, author and dates
• DiscussionForumPostingAuthor, author name, post date, and text, image or video
• CommentAuthor, author name, date, and text, image or video
• QAPage and QuestionQuestion name, answer count, and an accepted or suggested answer
• AnswerAnswer text, with author, date, link and upvotes recommended
• FAQPageQuestion name and accepted answer text
• BreadcrumbList and ListItemItem list, position and name
• OrganizationName, URL and logo
• LocalBusiness and its subtypesName and address
• Product, Offer, Review, AggregateRatingName, plus offers, reviews or ratings
• EventName, start date and location
• JobPostingTitle, description, date posted, employer and location
• RecipeName and image
• VideoObjectName, thumbnail and upload date
• CourseName and description
• SoftwareApplicationName, offers, and a rating or review
• ProfilePageMain entity
• DatasetName and description

Every other schema.org type is still checked for spelling, properties and formats.

Tips that prevent most schema mistakes.

1. Mark up only what visitors can see. Markup that describes hidden content, or content that isn’t on the page, can cost you rich results altogether.
2. One page, one main thing. Pick the type that describes the page’s main content, and nest the rest inside it.
3. Use the most specific type. BlogPosting or NewsArticle tells search engines more than Article; Restaurant more than LocalBusiness.
4. Use full URLs and ISO dates. https://example.com/image.jpg and 2026-11-08T09:00:00+05:30, never relative paths or “8 Nov”.
5. Keep counts honest. Answer counts, ratings and review counts must match the page.
6. Check for duplicates after every plugin or theme change. Two tools adding the same type is one of the most common problems.
7. Validate the live page, not just your template. Paste the URL after publishing; caching and plugins can change what ships.
8. Watch Search Console. Its Enhancements reports show errors across your whole site, not just one page.

Schema for forums and communities.

Community pages need the right type, not just a valid one. Use DiscussionForumPosting for a thread members write, with replies as Comment. Use QAPage only when the page is built around one question that members can answer. Use Article for content your team publishes.

Forum platforms get this wrong more often than you’d think. When we audited them in 2026, XenForo marked every thread as a discussion, Q&A threads included; vBulletin had open Search Console warnings about authors and comments; and Discourse used microdata rather than JSON-LD. Paste a thread from your own community above and see what your platform actually outputs.

Need to write markup from scratch? The schema markup generator has discussion forum, Q&A, Article, Organization and Breadcrumb templates.

Questions.