Structured Data Validity Check
Verify JSON-LD syntax, semantic completeness, visible-content agreement, graph connectivity, and current search-feature relevance.
Check your websiteWhy this check matters
Machines need more than parseable JSON. Incomplete, disconnected, retired, or visibly unsupported markup can misrepresent the page and cannot be assumed to qualify for search features.
Passing evidence
{ "@context": "https://schema.org", "@type": "Organization", "name": "Example" }Common failing evidence
{ "@type": "Organization", "name": "Example", }Possible false positives
- FAQ rich-result eligibility is limited and should not be treated as universal search enhancement coverage.
- Google retired the sitelinks search-box SearchAction feature; keeping old markup does not earn current feature credit.
How to fix it safely
- Serialize JSON-LD with a real JSON encoder.
- Choose primary types that match the visible page purpose.
- Add the meaningful required properties for each primary type.
- Connect related nodes with stable @id values.
- Remove or correct claims users cannot verify on the page.
How to verify the fix
- Parse every rendered application/ld+json block.
- Compare names, URLs, offers, authors, dates, and claims with visible content.
- Run the canonical page through the relevant current structured-data validator.
Related SEO / AEO / GEO checks
Run the complete audit
Check this signal together with the related category evidence on the current public page.
Open the seo / aeo / geo audit tool
