Validate JSON-LD schema markup for 12 types including SoftwareApplication, SearchAction, and FAQPage. Deeper than Google's Rich Results Test.
Run Free Audit →No credit card required · Results in under 2 minutes
Deeper than Google's Rich Results Test. Validates 12 schema types including SoftwareApplication, SearchAction, and Article with named authors — and checks for deprecated patterns and AI readiness signals that Google's tool doesn't cover.
Schema markup is the part of SEO that looks deceptively simple. You add JSON-LD to your page, paste it into Google's Rich Results Test, it says "valid," and you move on. Six months later you wonder why your FAQ rich results stopped showing, why your SoftwareApplication page isn't eligible for app carousels, or why AI assistants cite your competitor instead of you. The Rich Results Test only checks whether your schema is eligible for a specific rich result type — it does not check whether it is complete, whether it uses deprecated syntax, or whether it is structured to support AI citation.
seo.yatna.ai's schema validator checks all of that.
Required fields: headline, datePublished, dateModified, author.name. The validator checks author.sameAs — a link to the author's LinkedIn, Google Scholar, or professional biography — which is the primary field that determines whether Google and AI citation systems treat your content as coming from a credible, named expert. Missing dateModified disqualifies pages from article carousels and Top Stories even when all other fields are present.
Required fields: name, applicationCategory, operatingSystem, offers.price, offers.priceCurrency. applicationCategory must be a valid Schema.org enumeration (e.g., "BusinessApplication", "DeveloperApplication"). offers.price is required for rich results in Google's app-related search features. The validator checks the complete required field set — not just whether the @type is present.
The most commonly broken schema type on SaaS and tool sites. The validator specifically checks for the deprecated {"@type": "EntryPoint"} pattern in the target property — a syntax that worked until 2022 and now silently fails. The correct syntax is a plain URL template string: "target": "https://example.com/search?q={search_term_string}". If your WebSite schema still uses the EntryPoint object, your sitelinks search box is broken and you may not know it.
Required fields: at minimum one mainEntity of type Question with an acceptedAnswer of type Answer. The validator checks answer text length — answers under 50 words have a significantly lower rate of triggering rich results in practice, even though Schema.org has no explicit minimum length requirement. It also checks that Q&A pairs are complete and that no question has an empty or missing acceptedAnswer.
Required fields: itemListElement array with ListItem entries each containing position, name, and item (URL). The validator checks URL consistency — the breadcrumb URLs must resolve to real pages and must match the canonical URLs on those pages. Breadcrumb schema that points to redirected or non-canonical URLs is ignored by Google's rich result renderer.
Required fields: name, url. The validator checks sameAs completeness — an empty or single-entry sameAs array significantly reduces the likelihood of Google associating your brand with a Knowledge Panel. Strong sameAs entries include Wikipedia, Wikidata, LinkedIn company page, Crunchbase, and major social profiles. Missing logo with explicit height and width also disqualifies the Organization from logo display in search results.
Required fields: name, address (with streetAddress, addressLocality, addressRegion, postalCode), telephone. The validator checks geo coordinates (latitude/longitude) and openingHoursSpecification — both of which are required for map pack eligibility and local rich results. Missing coordinates reduce the accuracy of Google Maps placement for businesses with non-unique addresses.
Required fields: name, offers (with price, priceCurrency, availability), brand. The validator checks availability against the valid Schema.org enumeration values (InStock, OutOfStock, PreOrder, etc.) — an invalid string here causes the entire Product schema to fail rich result eligibility silently. aggregateRating is optional but significantly increases click-through rate when present and valid.
Required fields: name, step array with HowToStep entries each containing name and text. The validator checks step completeness — a HowToStep with a name but no text is a common error that passes the Rich Results Test but fails at the rendering stage. It also checks image on individual steps, which increases eligibility for the visual HowTo rich result format.
Required fields: name, description, thumbnailUrl, uploadDate. The validator checks duration in ISO 8601 format (PT1M30S for 1 minute 30 seconds) — missing duration reduces eligibility for video rich results. It also checks that thumbnailUrl returns a 200 response and meets the minimum 160px width requirement for video thumbnails in search results.
Required fields: name. The validator checks jobTitle, worksFor, and sameAs — the three fields that establish credibility for author schema and E-E-A-T signals. A Person schema without sameAs links to authoritative profiles provides no additional E-E-A-T signal beyond the name itself. This is the most common E-E-A-T gap found in audits of content-focused sites.
Required fields: name, url. The validator checks potentialAction with a correctly formatted SearchAction (see SearchAction above — the EntryPoint deprecation applies here as well). A valid WebSite schema with potentialAction is required for sitelinks search box eligibility. It also checks that the WebSite schema appears on every page, not just the homepage, since Google requires it to be consistently present.
Google's Rich Results Test checks whether a specific schema block is eligible for a specific rich result type in Google Search. It answers one question: "Will this produce a rich result?"
seo.yatna.ai's schema validator answers three different questions:
Is it complete? — Required fields, recommended fields, and the fields that affect AI citation confidence (like author.sameAs and Organization.sameAs) are checked against the full Schema.org specification, not just Google's rich result eligibility requirements.
Is it using deprecated patterns? — The SearchAction EntryPoint deprecation is the most common example, but there are others. The validator checks your JSON-LD against current Schema.org syntax and flags any patterns that were valid in previous years but no longer work correctly.
Is it structured for AI readiness? — AI citation systems like ChatGPT Search and Perplexity look at schema fields to evaluate source credibility. author.sameAs, Organization.sameAs, Article.dateModified, and Person.jobTitle all contribute to whether an AI assistant cites your content or a competitor's. The Rich Results Test has no concept of AI readiness; our validator checks for it explicitly.
SoftwareApplication: missing offers.price field
Required for rich results. Google's app-related rich result formats require a price (or "0" for free apps). Without it, the entire SoftwareApplication schema is ineligible for enhanced display regardless of how complete the rest of the schema is.
Article: author.sameAs not set
The most common E-E-A-T gap in audits. Without author.sameAs, the author name in your schema is an unverifiable string. Google and AI citation systems cannot associate it with a known expert. Fix: add a sameAs array pointing to the author's LinkedIn profile, Google Scholar page, or authoritative biography URL.
SearchAction: using deprecated {"@type": "EntryPoint"} for target property
The EntryPoint object syntax was deprecated in 2022. The correct format is a plain URL template string. Sites still using EntryPoint pass the Rich Results Test but fail at the sitelinks search box rendering stage — meaning the search box never appears in Google results even though the validation tool shows no errors.
FAQPage: answer text under 50 words Technically valid by Schema.org specification, but short answers rarely trigger the FAQ accordion rich result in practice. Answers under 50 words are flagged as a medium-severity warning with a recommendation to expand to at least 50–100 words.
Organization: sameAs array empty
An Organization schema with an empty or missing sameAs array provides no entity disambiguation signal. Google uses sameAs to connect your website entity to your Knowledge Graph node. Without it, your brand is effectively anonymous in Google's entity graph — reducing Knowledge Panel eligibility and AI citation confidence.
How is this different from Google's Structured Data Testing Tool? Google's tools (both the Rich Results Test and the legacy Structured Data Testing Tool) check for rich result eligibility — whether your schema meets the minimum requirements for Google to display a specific rich result type. Our validator checks for completeness against the full Schema.org specification, deprecated syntax patterns that silently fail, and AI readiness signals that determine whether AI assistants cite your content. These are three distinct checks that Google's tools do not perform.
Can I paste raw JSON-LD to validate? Yes. Enter your live page URL to validate schema as Google sees it on your actual page, or paste raw JSON-LD directly into the validator input to check a schema block before deploying it. Both modes run the full 12-type validation check.
Does it validate all pages on my site? The free tier validates a single page — enter any URL and get a full schema validation report for that page. Starter tier and above run schema validation as part of the full site audit, checking every crawled page and surfacing the most critical schema errors across your entire domain.
What is the SearchAction EntryPoint deprecation?
The EntryPoint object was the original way to define a SearchAction target in Schema.org. It was deprecated in 2022 in favor of a simpler URL template string. Sites that haven't updated their schema still use the old syntax, which now fails silently — the sitelinks search box never appears even though the schema looks valid to casual inspection. See the full explanation in our SearchAction Schema guide.
Invalid schema costs you rich results, reduces E-E-A-T signals, and lowers AI citation confidence. The validator runs in under 60 seconds and tells you exactly which fields to fix.
Related reading:
7 AI agents. 7 audit categories. One score. Free for your first audit.
Run Free Audit →