Why it matters
Multiple h1 elements blur the page topic for search engines and make heading navigation confusing for screen-reader users.
How to fix it
Keep exactly one per route (usually in the page) and use + for sections; logos in layouts shouldn't be h1.
Example
<h1>Pricing</h1>
<section><h2>Enterprise</h2></section>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.
dynamic-metadata-streamingRequest-time `generateMetadata` without `htmlLimitedBots`missing-langRoot `<html>` without `lang`jsonld-missingNo JSON-LD structured datasitemap-lastmod-nowSitemap uses `new Date()` for `lastModified`jsonld-deprecated-typeJSON-LD type that no longer produces rich resultsroute-js-budgetRoute first-load JS over budget (from `.next` build output)animate-undefined`animate-*` class with no matching `--animate-*` theme variable or `@keyframes`random-in-render`Math.random()` / `Date.now()` / `new Date()` evaluated in a component render body