Single Descriptive H1

What it does

Ensures each page has exactly one meaningful <h1> element and flags missing, duplicate, empty, or brand-only H1s. This rule explains why H1s matter for search engines, how to detect common problems in rendered DOM, and provides concrete fixes and examples for frameworks like Next.js/React.

When to use it

Use this skill when auditing page templates, running automated SEO checks, generating H1 suggestions for landing pages or blog posts, or reviewing CMS output that might produce empty or duplicated headings. Ideal for engineers, content editors, and SEO auditors.

What's included

• Scripts: none in this skill (has_scripts=false)
• References: includes a references/ directory with rule details and external link to frontendchecklist.io (has_references=true)
• Instructions: parse rendered DOM, count <h1> elements, assert exactly one non-empty H1, compare to <title>, and ensure H1 isn't a shared header/brand-only element. Provides remediation steps and example before/after markup.

Compatible agents

Best for agents that can inspect rendered HTML/DOM or run lightweight page audits (browser-capable agents, Puppeteer-enabled crawlers, or server-side render checks).