Why it matters
Structured data (Organization, WebSite, Article, Product, BreadcrumbList) makes pages eligible for rich results and gives search and AI systems unambiguous facts about the entity behind the site.
How to fix it
Render one JSON-LD @graph with Organization + WebSite on the home page and type-specific data on articles/products, via an escaped
Example
<JsonLd data={{ '@context': 'https://schema.org', '@graph': [{ '@type': 'Organization', '@id': 'https://example.com/#org', name: 'Acme' }] }} />References
More lint rules
void lint reports 67 rules in this category. Static source checks with no browser: Tailwind v4 silent failures, Next.js 16 API traps, React render-body bugs, accessibility markup, SEO files and motion hygiene.
missing-iconNo favicon / app iconmissing-llms-txtNo `/llms.txt`dynamic-metadata-streamingRequest-time `generateMetadata` without `htmlLimitedBots`missing-langRoot `<html>` without `lang`sitemap-lastmod-nowSitemap uses `new Date()` for `lastModified`multiple-h1More than one `<h1>` in a route's page + layoutsjsonld-deprecated-typeJSON-LD type that no longer produces rich resultsroute-js-budgetRoute first-load JS over budget (from `.next` build output)